Gergely Kalapos

Hi @sluebbert, a new agent version (version `1.4.0`) just went out and it contains the fix for this issue. With that you could remove the `ELASTIC_APM_DISABLE_METRICS` setting, and with the...

I believe this is addressed in https://github.com/elastic/apm-agent-dotnet/pull/750 and it's a fairly old issue. I'm closing this now. If this happens again, please make sure you are on a fairly up-to-date...

Hi @m-hafi, it seems the [CLA is not yet signed](https://github.com/elastic/apm-agent-dotnet/pull/1629#issuecomment-1043016214) - we'd need that before we proceed. More importantly, we'll need tests which cover this feature and the new config...

I quickly looked at the library - no `DiagnosticSource` unfortunately :(

Thanks for reporting! We'll look at this - clearly something we'll need to fix.

To be clear, this whole thing was [in a try-catch block](https://github.com/elastic/apm-agent-dotnet/blob/main/src/Elastic.Apm/ServerInfo/ApmServerInfoProvider.cs#L63). I agree we can have a better parsing logic - that's what @z1c0 fixes in https://github.com/elastic/apm-agent-dotnet/pull/1787. But by looking...

Hi @Chompetto yes, it's definitely on our radar. We are aware that the .NET Agent is behind the other agents in terms of lambda support, and we definitely want to...

I agree with the recommendation from @vhatsura - the whole idea of passing an `IConfiguration` was that you can use any config source through that and the agent will read...

@matheus-inacio thanks for reporting. As an immediate workaround: I see it's caused by the MondoDb driver - have you considered referencing the `Elastic.Apm` package and other packages you need manually,...

Short summary: In the agent we always target the lowest possible version of a given library, but that does not mean that specific version must be loaded at runtime. Typically,...