NR1 Account Maturity is a quick view to understand if you're using key features of your New Relic account across multiple accounts and multiple applications.
Apache License 2.0
4
stars
12
forks
source link
DT reporting doesn't reflect how Spans are reported with auto application naming enabled #17
When auto application naming is enabled in a Java agent, the root application name (configured appName) will always be the attribute name for Span Events. However, the DT page for a service whose name was auto generated, will show Spans on its DT APM/NR One pages.
This results in the Account Maturity App showing that the auto-generated application does not have DT enabled, yet it indeed is by proxy of the root application.
Steps to Reproduce
Create an environment to run multiple servlets in containers.
Enable DT in the configuration for the Java Agent.
Generate traffic to the auto generated application end point.
Observe DT. Compare Span Events and Transaction table in Insights/
You'll see traceId for Spans, but the attribute for appName[s] will be for the appserver.
Expected Behaviour
Account for the auto application named service running in the container that has DT enabled.
Relevant Logs / Console output
I can provide an internal NR ticket for this if needed.
Description
When auto application naming is enabled in a Java agent, the root application name (configured appName) will always be the attribute name for Span Events. However, the DT page for a service whose name was auto generated, will show Spans on its DT APM/NR One pages.
This results in the Account Maturity App showing that the auto-generated application does not have DT enabled, yet it indeed is by proxy of the root application.
Steps to Reproduce
Create an environment to run multiple servlets in containers. Enable DT in the configuration for the Java Agent. Generate traffic to the auto generated application end point. Observe DT. Compare Span Events and Transaction table in Insights/ You'll see traceId for Spans, but the attribute for appName[s] will be for the appserver.
Expected Behaviour
Account for the auto application named service running in the container that has DT enabled.
Relevant Logs / Console output
I can provide an internal NR ticket for this if needed.
Your Environment
Additional context