Log Decoration Support for Semantic Logger #2341
Labels
5
Story Point Estimate
community
To tag external issues and PRs submitted by the community
feature request
To tag feature request after Hero Triage for PM to disposition
jan-mar qtr
Possible FY Q4 candidate
Milestone
Comments
chris-judd
added
the
feature request
github-actions
bot
added
the
community
|
Blocked by #2358 ? Not sure we can tackle this one for the current |
kford-newrelic
added
5
|
The problem is a duplicate of an existing issue. |
github-project-automation
bot
moved this from To do
to Code Complete/Done
in Ruby Engineering Board
github-project-automation
bot
moved this from Code Complete/Done
to Triage
in Ruby Engineering Board
|
Inadvertently closed. Re-opening and putting on backlog for future consideration. |
kford-newrelic
added
the
apr-jun qtr
kford-newrelic
added this to the Ruby Agent - FY25Q1 Instrumentation Improvements milestone
kford-newrelic
added
jul-sep qtr
kford-newrelic
added
oct-dec qtr
kford-newrelic
removed this from the Ruby Agent - FY25Q2 Non-Core Instrumentation Improvements milestone
elucus
added
jan-mar qtr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently, logs coming from the SemanticLogger are not decorated for traceId. This breaks the Logs In Context feature for Ruby APM Services when browsing the Distributed Tracing curated views.
Feature Description
Update NR Ruby Agent to support SymantecLogger's implementation of log forwarding so that log decoration is successful.
Describe Alternatives
None
Additional context
SemanticLogger added support for forwarding logs using the New Relic ruby agent, but this was not implemented by NR. It appears that the way they did this is to record their logs directly to the agents aggregator, which would bypass the part of the agent that would be decorating any logs.
Priority
Must Have
The text was updated successfully, but these errors were encountered: