Gergely Kalapos
Gergely Kalapos
From https://github.com/elastic/apm-agent-dotnet/pull/1275#pullrequestreview-646527790. Currently we have 2 dependencies that we ship with the agent and pull in as source code (Newtonsoft.Json and Ben.Demystifier). We should have some automation for updating these...
Currently the agent tries to send each event once, and if it fails, it just logs. We should implement a retry logic and listen to responses from the server and...
- When `Microsoft.Extensions.Configuration.IConfiguration` is passed (e.g. ASP.NET Core) we read `builder.ApplicationServices.GetEnvironmentName()` - On ASP.NET classic we actually pass `null` - The `EnvironmentConfigurationReader` (which is the default one if you don't...
Sets the minimum duration of spans. Spans that execute faster than this threshold are attempted to be discarded. Some spans ignore this setting (details in the Java doc). Java PR:...
The version check [here](https://github.com/elastic/apm-agent-dotnet/blob/master/src/Elastic.Apm/Metrics/MetricsProvider/ProcessTotalCpuTimeProvider.cs#L69) does not seem to be correct. It's based on the version of the assembly of the `Process` type, but the version of that assembly does not...
So far, no agent had distributed tracing and span link support for Azure Service Bus. .NET implemented it recently and it uses the `diagnostic-id` application property - as suggested in...
### Problem statement In the [W3C TraceContext](https://www.w3.org/TR/trace-context/) specification it's possible that a system is monitored by multiple tracing tools. Example: **A** -> **B** -> **C** (Service A calls Service B...
Some agents have a configuration to set a proxy to the http client which reports to APM Server. Current status: - [Ruby](https://www.elastic.co/guide/en/apm/agent/ruby/current/configuration.html#config-proxy-address) - 5 different configs: `ELASTIC_APM_` +`proxy_address`, `proxy_headers`, `proxy_password...
Follow up from: https://github.com/elastic/apm-agent-dotnet/pull/1826 https://github.com/elastic/apm-agent-dotnet/pull/1826 removed the `integration tests` from the pipeline - that means after that PR there is no test in the .NET APM Agent pipeline to test...