elixir_agent
elixir_agent copied to clipboard
newrelic
New Relic's Open Source Elixir Agent
Add telemetry based instrumentation, following the patterns used for other libraries, in special `NewRelic.Telemetry.Plug`. Transaction names present a bit of challenge, as jobs don't necessary have "stable" names: names can...
**Is your feature request related to a problem? Please describe.** Current Agent export database queries, but they are only available as part of the Transaction traces. For other agents, like...
Extend the `accept_distributed_trace_headers` and `distributed_trace_headers` functions to enable passing the Distributed Tracing payload beyond the HTTP context, for cases like `grpc` or message queues. Right now these are internal functions,...
Right now a "Transaction" is tracked across spawned processes, so work done in the child process is included in the Transaction. It would be useful if we could _safely_ track...
Other agents have an HTTP connect timeout as high as 2 minutes when they connect to the new relic collector. We should increase the timeout the agent uses for contacting...
Calculate "Total Sum of Squares" value for Metrics. This uses Welford's online algorithm. It is relatively accurate when using 64-bit floating point values, only losing accuracy on float rounding. Here,...
**Describe the bug** Seem to be having an error on startup in our service where `parse_error_info(nil)` is being called. If we trace this up the stack we get to some...
Before this PR, all LiveView metrics are named for the plug and action, i.e. `WebTransaction/Phoenix/Phoenix.LiveView.Plug/index`. This PR names those metrics after the module and action, i.e. `WebTransaction/Phoenix/PhxExampleWeb.HomeLive/index`. This provides more...
Phoenix LiveView is becoming more popular. Currently the agent reports the live view metrics with the name `Phoenix.LiveView.Plug/#{action}`. It would be more helpful if the metric had the name of...