Welcome to the latest Online Technical Community’s
Post of the Week
The Community members featured in this edition of our Post of the Week give such amazing tips, are transparent to the max, and generally are
superstar New Relic users. Thanks for being awesome!
First, a shoutout to
@eric_stein_de for sharing his tip on a successful Twisted/Python app:
@dustin.lacewell - it is in fact possible. I am doing it for my background batch jobs.
Here is a snippet of my code that I did. Granted, this is not async code and it is not twisted code. If you want to make transactions for web requests in an asynchronous python thing, you would have to patch the code in the python NR agent that influences how the instrumentation parts detect the current transaction. I'm not going to go into that here. It is likely fraught with issues, and I don't really rec…
@bill.anderson has not one, but two incredible Synthetics posts:
I noticed this on one of our ping monitors. The monitor was still running from a location after the schedule change. Try disabling and then enabling the monitor. That solved the issue for me
Thanks, One option might be to have a schedule that allows you to select alternate locations. That way if a location is overloaded or down there is a backup location the monitor still runs just not at the suggested location. In general, it's more important to make sure to verify the site is up than check from a specific location. There are exceptions to this where we need to check from a specific location to a specific site
Check out the details that
@jimm threw down regarding our Java Agent:
Hi gwilson - my solution was not very good because each piece of background work showed up in the New Relic UI as a distinct transaction. We ended up not using it because it threw our metrics way off. For example if we used 10 transformations of a Scala Future to fully process the request, we ended up with 10 transactions for every request, and each transaction appeared to be extremely fast because it didn't account for any of the wait non-blocking waits.
But let's say you want to go down th…
BIG thank you to our Forum Hero, @stefan_garnham for always being there with detailed answers and a helping attitude. You Rock!
if(navigator.userAgent != [your agent])
// load NR browser script
@prachetos.sadhukhan: You could use a custom attribute on the transaction which you could then FACET on in Insights.
The benefit of doing this is that you then remove the url filtering so the dashboard will still work if you change the domain name.
Another great week! I am always amazed by the content I review every week! Thanks not only to the Community members being heroes that I listed above, but a huge thumbs up to
every one of you that help out all the time! See you all back in the Online Technical Community soon!