Hi all! And thanks for joining us for today’s:
Post of the Week!
Thank you to
all who helped make the Online Technical Community excellent this week! Keep reading to learn about workarounds, NRQL queries and exciting changes!
Our Community Heroes were especially on fire this week.
to @pault for providing us with this Synthetics workaround:
Not natively but easy to implement in the code.
Just check time of day when firing. Assert success if between 2 and 3am, otherwise run the tests.
Note, you’ll still be charged credits for each of these dummy probes but you’ll not get false alerts.
Another side effect to be aware of is that your timing graphs will suddenly show a near-zero response time for the given monitor. Depending on how you consume synthetic data, this may or not be a problem.
Given a synthetic can only pass or fail, …
@stefan_garnham and @LAMBERT include more additions to the NRQL Query Library:
As requested by
@hross Here is some nrql to create an uptime report for the past 12 months broken down by month. Useful when presenting to management
SELECT percentage(count(*), WHERE result =‘SUCCESS’) FROM SyntheticCheck WHERE type =‘SIMPLE’ since 12 months ago FACET monthOf(timestamp)
Obviously you would alter the "type = " to suit your own needs. This just queries our Synthetic ping results. For your scripted synthetics you might use “type = SCRIPT_BROWSER” and also perhaps modify the “sin…
Be sure to visit us in Feature Ideas! Or newest category will hopefully help make requests in the community a lot better.
Click the link below to learn the details:
We feel really lucky here at New Relic because we get to work with some of the smartest and most creative technical people on the planet: you!
Every day you use the community to ask tough questions and support one another. Best of all for us, you give us great ideas for the future direction of New Relic products.
Today, we’re rolling out a new way to discuss those great product ideas you have: the Feature Ideas category. What’s it all about?
How it works
Sometimes you bring ideas to t…
We are getting ready to launch our new Twitter handle! You all voted and
! Thanks for participating: @Learn_NR won
The Online Technical Community is getting its own Twitter handle - one that will help integrate content from the Community, Datanauts,
NRU, docs, and more. We’ll be framing the account as a place for knowledge acquisition and learning about New Relic products and software best practices in general.
Here’s the important part: We need your help naming the new handle! Tell us which one you prefer (these specific formats are available, others may not be):
Thanks for sharing your tw…
and be sure to visit us here:
It is going to be a great week! We want to hear from you! Solved any particularly interesting New Relic problems lately? Need your questions answered? Please contribute as often as you can—we love seeing you all in here pitching in. Thanks again for your participation and come again soon!