Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
I can see the IEventReplication was moved to EPiServer.Framework.AspNet.dll, trying the following now:
<tracerFactory name="NewRelic.Agent.Core.Tracer.Factories.IgnoreTransactionTracerFactory">
<match assemblyName="EPiServer.Framework.AspNet" className="EPiServer.Events.Remote.EventReplication">
<exactMethodMatcher methodName="RaiseEvent" />
</match>
</tracerFactory>
That didn't work :thinking:
Hello all.
Trying to ignore a NewRelic hit on /EPiServer.Events.ServiceModel.IEventReplication.RaiseEvent (approx 5k rpm) as it's skewing our view in NR a fair bit. 4 servers, lots of chatter/publishes etc - first off is this an expected amount of hits? I'm kinda dubious it's working harder than what is reasonable. I'm not fully sure what this api is doing/if this is the norm (we don't have NR on other clients - does anyone have a similar story?).
Attempting to block the instrumentation for this transaction using a custom instrumentation file https://docs.newrelic.com/docs/agents/net-agent/custom-instrumentation/add-detail-transactions-xml-net#blocking-instrumentation but struggling to configure it correctly. Does anyone have experience with this? (quite bespoke I know...)
Cheers!