Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Shared Dashboards Contest—Add Your Queries Here!

shared-dashboards

#108

This dashboard provide the website available & performance report to customer.

Query-1: [WWW][APP] Availability & Response Time

  • Rename monitoring name with a shorter text

  • Show weekly average availability, performance and satisfaction score

    SELECT percentage(count(*), WHERE result='SUCCESS') as 'Availability (%)', average(duration)/1000 as 'Response Time (s)', percentage(count(*), where (monitorName like '%OMM%' and duration/1000 < 150) or (monitorName not like '%OMM%' and duration/1000 < 90)) as 'Satisfied (%)' from SyntheticCheck FACET cases (where monitorName like '%OMM%' as 'HSP1-OMM', Where monitorName like '%SRT%' as 'HSP2-SRT', where monitorName like '%ESMT%' as 'HSP3-ESMT', where monitorName like '%ORCH%' as 'HSP4-Orchestra', where monitorName like '%DY%' as 'HSP7-DynWF') where monitorName like '%_A_%' and monitorName not like '%_UAT_%' since 7 day ago

Query-2: [WWW][HSP] Slowness Count (>10s)

  • This widget could easily identify whether the slowness is coming from location network issue

    SELECT count(*) as 'Slowness count' from SyntheticCheck FACET monitorName, locationLabel WHERE monitorName like '%WWW_S_%' and monitorName like '%_S_%' and duration/1000 > 10 SINCE 7 days ago LIMIT 100

Query-3: Availability (%) WSE-W vs. WSE-X

  • This widget given a overall vision to customer about availability

    SELECT percentage(count(*), WHERE result='SUCCESS') as Availability FROM SyntheticCheck FACET cases(where monitorName like 'WSE-W%' as 'WSE-W', where monitorName like 'WSE-X%' as 'WSE-X') Where monitorName LIKE 'WSE%' and monitorName not like '%A_UAT%' SINCE 7 DAY AGO LIMIT 100


Vote for this Dashboard!

  • :star: :star: :star:
  • :star: :star:
  • :star:

0 voters


#109

We use NR APMs and Synthetics to monitor our Fuse ESB infrastructure (middleware). We have a customer facing portal plus internal Billing and CRM systems that utilise external credit agencies, data warehouses etc. So, there’s always people asking if the issue is with ‘us’ or ‘them’. The dashboard is fairly simple using NRQL queries and some charts from the NGINX plugin. Plus we also use an NTP plugin (not shown) as time sync is crucial in our business. NR Alerts are sent as webhooks to Zapier and then sent to either statuspage, slack or jira. Never a dull moment in operational support.

SELECT count(*) FROM Transaction WHERE appName in (‘credit production’,‘Consumption Production’,‘Customer Production’,‘address production’,‘billing production’,‘consumer production’,‘contact production’,‘credit production’) FACET httpResponseCode SINCE 60 MINUTES AGO TIMESERIES

SELECT count(*) as ‘ESB Errors’ from TransactionError where appName NOT LIKE ‘%SSP%’ SINCE 1 day ago FACET appName

SELECT count(*) as ‘Errors’ FROM TransactionError facet error.message WHERE error.message NOT LIKE ‘%Test%’ SINCE 1 day ago LIMIT 10

SELECT histogram(duration,10,18) from PageView SINCE 1 day ago FACET appName limit 20


Vote for this Dashboard!

  • :star: :star: :star:
  • :star: :star:
  • :star:

0 voters


#110

This dashboard provides the website availability monitoring as a daily task.


#111

Sub-Account Integration Summary

Challenge When you have 170+ sub-accounts that are tied to the operational metadata for the things that you are monitoring AND you use that metadata to filter the Cloud Integrations, well that’s a lot of data to keep track across our accounts. Because we work on a DevOps/SRE model with New Relic (we “own” the platform, provide consulting services to teams and help establish best practices, etc, but they own the day-to-day stuff), we wanted to give them a way to quickly ensure that their data was reflective of what they thought they should be collecting.

Solution A Sub-Account Summary is a quick snapshot of what data is being collected through agents, Cloud Provider integrations, and the freshness of that data. As an added feature, we also track the failures to collect data due to throttling. While this isn’t a problem for smaller shops, when you have hundreds of sub-accounts and thousands of users hitting APIs, etc. it because a real concern.

Working clockwise, starting with the top-left table, these are the queries. They make use of the IntegrationDataFreshnessReport data – which is my favorite data set after NrDailyUsage :heart:

SELECT max(timestamp) FROM IntegrationDataFreshnessReport FACET providerAccountName, dataType, awsRegion SINCE 15 minutes ago

SELECT uniquecount(ec2InstanceId) FROM ComputeSample SINCE 15 minutes AGO
Note that this query is specific for EC2 instances. If you have GCP instances, it will be slightly different.

SELECT SUM(requestCount), sum(retryCount), sum(throttleException) FROM IntegrationProviderReport FACET providerAccountName, awsRegion, awsServiceName SINCE 1 day ago

SELECT uniquecount(hostname) FROM ComputeSample FACET operatingSystem SINCE 15 minutes ago


Vote for this Dashboard!

  • :star: :star: :star:
  • :star: :star:
  • :star:

0 voters


#112

Screenshot

This dashboard provides the response time of some our applications


Vote for this Dashboard!

  • :star: :star: :star:
  • :star: :star:
  • :star:

0 voters


#113

Continuing the discussion from Shared Dashboards Contest—Add Your Queries Here!:

SLA checks results in last 30 minutes

Dashboard represents SUCCESSFUL / FAILED results for our SLA related checks in last 30 minutes

SELECT count(*) AS ‘’ FROM SyntheticCheck SINCE 30 minutes ago FACET result WHERE monitorName = ‘pr_nameofthecheck’


Vote for this Dashboard!

  • :star: :star: :star:
  • :star: :star:
  • :star:

0 voters


#114

Response time for each of services


#115

Dashboard - Error stats Dashboard

This dashboard shows us all the stats which we use on daily basis for error logging, detection and resolving. Some of the critical charts include:

  1. Which of the server instance is throwing how many internal errors.
  2. Which OS is giving which type of JS error.
  3. Response code appdex
  4. Some critical microservice appdex scores

Dashboard Details

Required Products: APM, Browser
Level of Effort: Low

Settings:
Event Types: Transaction, JavaScript Error
Enabled Attributes: response.status, host, userAgentOS

Chart Details

App to response code response time:

SELECT count(error) FROM Transaction FACET appName, response.status SINCE 1 day ago TIMESERIES

JS Errors by OS

SELECT count(*) FROM JavaScriptError FACET userAgentOS,errorMessage

JS Errors

SELECT count(*) FROM JavaScriptError SINCE 3 days ago COMPARE WITH 3 days ago TIMESERIES


Vote for this Dashboard!

  • :star: :star: :star:
  • :star: :star:
  • :star:

0 voters


#116

Dashboard

A dashboards an information management tool that visually tracks, analyzes and displays [key performance indicators metrics and key data points to monitor the health of a business, department or specific process. They are customization to meet the specific needs of a department and company

A dashboard keeps every member of a business on the same page. Users can share dashboards in real-time and periodically. Dashboards bring a business’s data to the cloud, making key metrics and accessible to your entire time on desktop, mobile and tablet. There are a number of ways to share data dashboards: on wallboard tv’s, email reports, printable reports or direct access. Users can create a public link to their dashboard which gives anyone access, or through private link that allows only those with the link to access your data. It has become increasingly popular to display dashboards on wallboard tv’s in offices as a way to keep everyone on the same page about performance and objectives. Data dashboards are becoming increasingly common because they allow for virtual work environments and make it easier for teams to collaborate


Vote for this Dashboard!

  • :star: :star: :star:
  • :star: :star:
  • :star:

0 voters


#117

Dashboard: Mobile Applications - iOS & Android

This dashboard contains important business metrics and application health metrics.
It allows our application team to always have a good understanding of

  • users regularly logging into the mobile application
  • level of user satisfaction
  • most used areas of the application
  • trends in errors
  • frequency of mobile crashes
  • server-side performance


Dashboard Details

Required Products: API, Mobile, Synthetics
Level of Effort: Moderate
This dashboard uses custom events (Tap Events)
Settings
Use the gear button to edit your dashboard and configure the following settings:

  • Dashboard Filter: Enabled

Chart Details

% Crash Free Sessions

Gauge

SELECT (1-filter(uniqueCount(uuid), WHERE category='Crash') / uniqueCount(uuid)) * 100 as% Crash FreeFROM MobileSession, MobileCrash WHERE crashFingerprint NOT IN () where appName like 'PROD%' SINCE 1 week AGO LIMIT 1000
The percent of unique crash free mobile sessions.

Digital Gateway API - Performance

Pie Chart

select count(*) from Transaction where appName = 'mobile-api' facet cases(where apdexPerfZone = 'S' as 'Satisfied', where apdexPerfZone = 'T' as 'Tolerating', where apdexPerfZone = 'F' as 'Frustrated') since 1 week ago
Breaks down the server calls into its apdex categories of ‘Satisfied’, ‘Tolerating’, and ‘Frustrated’.

Feedback -> Satisfied -> Write Review

Funnel

SELECT funnel(sessionId, WHERE target like '%Feedback: Did Prompt' as 'Prompted for Feedback', WHERE target like '%Feedback: Satisfied Yes' as 'Tapped Satisfied', WHERE target like '%Feedback: Write Review Yes' as 'Tapped Write Review') FROM TapEvent SINCE 1 week ago
The number of sessions in which a user was prompted for feedback inside the application, said they were satisfied, and subsequently agreed to write a review.


Vote for this Dashboard!

  • :star: :star: :star:
  • :star: :star:
  • :star:

0 voters


#118

A last minute submission :slight_smile: !

Quick introduction

Our web application provides an easy and safe way for our healthcare partners to redirect patients of lower priority in order to reduce wait time, risk and costs in emergency rooms. Our process involves following a proven algorithm, where at each step you “leave” the process if the criteria aren’t matched.

We are in production since only a few weeks, so this is our quick first try of an overview dashboard :D. Data bellow has been anonymized with generic names and values, but enough to give you an idea!

Overview dashboard

As you can see, we can find the following informations (based on last 7 days data):

  • Total requests received

  • Amount of appointments taken

  • Availability (Synthetics healthcheck success rate)

  • Custom version of a funnel for our algorithm

  • Call duration for specific schedule loads

  • SLA and Request satisfaction

Details on some queries

1. Availability

We use our Synthetics healthcheck call’s success rate to display a gauge here.

NRQL:

SELECT percentage(count(*), WHERE result = 'SUCCESS') FROM SyntheticCheck 
WHERE monitorName = 'Healthcheck - Prod' SINCE 7 days ago

Useful to bring the value into a dashboard without having to check it elsewhere!

2. Algorithm funnel

This result is similar to a “conversion rate” in usual store sites, but applied to our reality. Since we do not use the Browser or Mobile features, we made our own homemade version of a funnel graph based on server requests at each steps.

NRQL:

SELECT count(*) FROM Transaction facet
cases(
  WHERE(name = 'WebTransaction/***/***Step1/**') as 'Step 1 - ***',
  WHERE(name = 'WebTransaction/***/***Step2/**:someId' AND `request.headers.referer` LIKE '%/***Step1/**') as 'Step 2 - ***',
  WHERE(name = 'WebTransaction/***/***Step3/**:someId' AND `request.headers.referer` LIKE '%/***/***Step2/%') as 'Step 3 - ***',
  WHERE(name = 'WebTransaction/***/***Step4/**:someId' AND `request.headers.referer` LIKE '%/***/***Step3/%') as 'Step 4 - Appointment confirmation'
)

SINCE 7 days ago

As you can see, we make sure that at each step, the call count only consider ones made (referred) from previous step.

-> Same principle (with same WHERE statement) is applied in the widget bellow to represent the % of users remaining after each step, similar to this:

NRQL:

SELECT
filter(count(*), WHERE(name = 'WebTransaction/***/***Step2/**:someId' AND `request.headers.referer` LIKE '%/***Step1/**'))
/ filter(count(*), WHERE(name = 'WebTransaction/***/***Step1/**')) * 100 as '% Step 2',

3. Important transactions duration percentiles

In order to monitor closely each schedule type’s load times (a heavy and important call in our API), we display the duration with this query:

NRQL:

SELECT percentile(duration, 50, 90) FROM Transaction WHERE `request.uri` LIKE '/scheduleTypeA/%' SINCE 7 days ago FACET `request.uri`

We can then view each variants and its matching values. The table filter function then allows us to see worst ones first. We actually caught a bug for a specific schedule load last week, as we could see high duration spikes for one of them!

TIP: As used in the previous request, the LIKE operator with a % at the end of URIs ensure it will match any query string parameters. A cool trick!

4. SLA and Apdex preview

As we display only this particular dashboard on a TV near our work area, we wanted to bring back the SLA and request satisfaction based on our Apdex value in our overview.

This query was highly inspired by a few posts in the Explorers hub! I don’t have the sources at hand, but we built it based on our findings here, so Kudos to you guys!

NRQL:

SELECT
count(*) / 1000 AS 'Requests thousands',
average(duration) * 1000 AS 'Resp. time ms',
apdex(duration, 0.5),
percentage(count(*), WHERE duration &lt;= 0.5) AS '% Satisfied',
percentage(count(*), WHERE duration &gt; 0.5 AND duration &lt;= 2) AS '% Tolerating',
percentage(count(*), WHERE duration &gt; 2) AS '% Frustrated'
FROM Transaction
WHERE appName = 'OurAppName-prod' SINCE 7 days ago

As you can see, our Apdex value is still the default one (500ms), which is hardcoded in this query. If someone figures out how to pull it from our actual apdex value instead, let us know :)!

Conclusion

We only just started exploring Insights. It’s a pretty cool module! We proved to our stakeholders that we could quickly mix performance, “technical” metrics with real business observations, which is great! Thank you NewRelic!

We will enhance our dashboards in the future.

PS: Hopefully there will be clear and affordable pricing options soon, in order to explore with a bit more than ~8 days data retention!


Vote for this Dashboard!

  • :star: :star: :star:
  • :star: :star:
  • :star:

0 voters


#119

[Effort LOW] - Infrastructure Performance

This simple dashboard shows me the cpu,memory and load details.

Screenshot

![04%20PM|690x325]

Dashboard Details

Required Products: Infrastructure
Level of Effort: Low
This dashboard will work on the standard New Relic data models and does not require any custom attributes or events.

Settings
Use the gear button to edit your dashboard and configure the following settings (below is an example):

  • Dashboard Filter: Enabled
  • Enabled Event Types: SystemSample
  • Enabled Attributes: entityId

Chart Details

Chart Title

Bar Chart

SELECT average(cpuPercent) AS '' FROM SystemSample FACET entityId SINCE 1 hour ago
Shows high cpu usage systems for past 1 hour. we can use hostname instead of entity id

Chart Title

Bar Chart

SELECT average(memoryUsedBytes/memoryTotalBytes*100) AS '' FROM SystemSample FACET entityId SINCE 1 hour ago
Shows high memory usage systems for past 1 hour. we can use hostname instead of entity id

Chart Title

Bar Chart

SELECT average(loadAverageFiveMinute) AS ' ' FROM SystemSample FACET entityId SINCE 1 hour ago
Shows systems with high load average for past 1 hour. we can use hostname instead of entity id


Vote for this Dashboard!

  • :star: :star: :star:
  • :star: :star:
  • :star:

0 voters


#120

I love it when we NRQL while we WRQL!


#121

Ha! Three stars for that silly and delightful response, @mark_ardito!

Thanks to all of you in this thread who participated in our contest! This was wildly successful and we can’t wait to continue sharing dashboards in the Explorers Hub.

Stay tuned for winner and prize announcements! :blush:


#122