.NET Core on Linux on AWS/ECS Fargate

[Carl.Brahms]

Has anyone managed to get a .NET Core for Linux agent to work on AWS Fargate?  We've had a number of attempts across multiple teams working on it with no luck.   

The controller receives the request to create a node just fine, but it doesn't seem to be able to pull in any of the normal metrics, or even collect basic agent metrics, like Agent|Availability.   No BTs are discovered, even when creating a standard ASP_DOTNET or POCO discovery rule to supersede the standard OOTB discovery rules.

Just wondering if there are any users that were able to get something to work on Fargate.

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/AWS_Fargate.html 

[Allan.Schiebold]

Hi. Which version of the agent are you trying to use? Thanks. 

[Carl.Brahms]

Hi Allan, thanks for the response. We have tried with version 4.5.13.0 and 4.5.18.1. Controller is 4.5.17.

Once v20.3 is released this month we will give that a try for our .NET Core 3.1 environments, so we could try that here.

[Allan.Schiebold]

Sounds good. The 20.3 release will work great with core 3.1 but 4.5.19.0 that's out now is technically capable of working with 3.1 if you're in the mood to try it out. Let us know! 

[Carl.Brahms]

We are using .NET Core 2.1 or 2.2, so we were expecting it would work fine for us on Fargate.

I’m more wondering if folks have successfully used serverless/Fargate so we can make sure we are barking up the correct tree in our troubleshooting.

Thanks!
Carl

[Allan.Schiebold]

Ah ok. Serverless .net monitoring is currently in the works. 

[Carl.Brahms]

Hi Allan, I think you’re thinking of something like Lambda. ECS on Fargate works more like a regular kubernetes environment but the management of the cluster and the nodes are abstracted so it’s also referred to as serverless.

It should be working, we just don’t see errors or problems with debug enabled. We will just keep trying.

[Allan.Schiebold]

Ah ok, yes, k8s / containers are supported. In case you haven't seen this I wanted to double check:

The agent supports the following features:

• ASP.NET MVC transactions  See Name MVC Transactions by Area, Controller, and Action

• ASP.NET WebAPI transactions
• ASP.NET Razor Pages transactions
• HttpClient backend calls
• ADO.NET backend calls such as SqlClient, MySql, SQLite, and PostgreSQL
• EntityFramework
• Upstream and downstream correlation using HTTP
• Snapshot waterfall view with async support
• Redis exit calls
• Detects and monitors calls to an Oracle database

Are you using anything outside of that list?

[Carl.Brahms · Accepted solution]

Hi Allan,

We will have to manually define POCO transactions.   DEBUG logs aren't showing the classes/methods to define for some reason, so we're going to enable TRACE logs and work with AppD support to continue troubleshooting.

Have a good weekend,

Carl