You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 2, 2021. It is now read-only.
What's the expectation here, should I be breaking up the scope of the generated element in the generated file and adding small scoped items like above ?
The text was updated successfully, but these errors were encountered:
I'm afraid I've no idea what the expected result is! I've previously used a single scope with low hundreds of instrumentation targets listed without issue, but my needs when I wrote NRConfig were pretty basic - for example, specifying a metric name was never useful to me.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Apologies, I'm fairly new to custom instrumentation, this looks like a great tool though.
I've create a file using the all method just to play and I see that there is one tag
<tracerFactory>
which is scoped to all the output.When I look at an NewRelic example it looks like :
<tracerFactory name="NewRelic.Agent.Core.Tracer.Factories.BackgroundThreadTracerFactory" metricName="Background/CustomTransaction">
What's the expectation here, should I be breaking up the scope of the generated element in the generated file and adding small scoped items like above ?
The text was updated successfully, but these errors were encountered: