Status Pages Nerdpack

StatusPage Nerdpack

This StatusPage Nerdpack collects multiple Statuspage.io in one dashboard, so you can check the status of your key dependencies in one place. In the screenshot below you will see data coming from New Relic, Atlassian, Sumo Logic and others!

Nothing is required to get up and running but it is helpful if you have some status pages you’d like to monitor like:

Clone This Nerdpack

Clone this repository and run the following scripts:

git clone https://github.com/newrelic/nr1-statuspageio.git
cd nr1-statuspageio
nr1 nerdpack:uuid -gf
npm install
npm start

Visit https://one.newrelic.com/?nerdpacks=local, navigate to the Nerdpack, and :sparkles:


The full StatusPage Nerpack GitHub repository and README can be found here.

Happy Nerd-ing! :nerd_face:

5 Likes

Hi

I deployed the status pages nerdpack, added a couple of custom hostnames after clicking on “Configure status pages” (I added slack, azure and new relic)
All I see on the main page is a spinner.
In the console i can only see a warning that says : Accessing reflect is deprecated

Hi Brett,

Glad to hear you got it installed, sorry to hear you’re having some trouble with it working. For the issue at hand:

  • Did you get there via the Launcher on the main page of one.newrelic.com? Or by clicking into a Service entity and accessing it there?

It’s possible if you accessed an Entity that is not in the account the nerdpack is deployed for, it would just spin. We’re working on this though, better feedback for when unexpected loading events happen.

  • “Accessing reflect is deprecated” is just a warning, don’t worry about it, could you filter by errors and see if there are any red ones? The other option is looking at the network tab, and examining any XHR requests going out and see if maybe it’s having trouble talking to one of the status page service providers

Unrelated to your issue, but something that might solve it anyways, we’re working on a big visual update to this Nerdpack that might be released pretty soon (perhaps a few days)! I would expect it to include some better behavior than an endless spinner :wink:

Let me know what you find and if you didn’t know about them, we have Open Office Hours where we’ll answer questions over Slack, we’d be happy to help you there too!

Open Office Hours & How to Join Slack

1 Like

Another thought here - because I have seen a stuck spinner on the Status Pages Nerdpack before too ->

Usually in my case this is because I have yet to select an account. In between the refresh rate and edit status pages buttons, there is a dropdown that is not super obvious. Once I select one of those accounts - the spinner stops and I can add / edit my status pages. :slight_smile:

1 Like

Ahhh that looks like it was it! Thanks Ryan!
You are right, that dropdown is super hidden. I never would have seen that!

I can see the new relic status now, although azure and slack are giving me errors like :

Access to XMLHttpRequest at ‘https://status.azure.com/api/v2/summary.json’ from origin ‘https://20e4500e-5ead-49e0-ab4d-1257a241e214.g0.nr-ext.net’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

I wonder if its the source that I added that is wrong.

Hi Brett - I imagine the account drop down will be fixed or more visible in the updated UI that Michael mentioned for that Nerdpack.

The Errors you see sounds more like Slack and Azure have CORS policies in place that don’t allow us to pull that data in. Not necessarily that you have anything misconfigured.

Let me check on it to see if I can grab Slack/Azure Status… I’ll follow up in a moment.

Hey Brett - I’m getting the same CORS errors in the Azure and Slack status modules in the Status Page Nerdpack.

From what I can tell from their status pages, they are not backed by statuspage.io or Google Status pages.

Currently the StatusPage nerdpack only supports those two status providers, Statuspage.io and Google.

If Slack & Azure don’t use those, it may be the reason behind the errors.

The nerdpack will look take the URLs you provide, and the setting you choose (Google or Statuspage.io) & determine the endpoint to ping to get the latest status data.

The likelihood here is that we are getting CORS errors on the endpoint we’re pinging, which is likely the wrong endpoint.

I have NPM and Git installed, but when I try to run the first step nr1 nerdpack:clone -r https://github.com/newrelic/nr1-status-pages.git

I get Error: You need npm to run this command I can’t find NPM documentation that helps me solve this.

@reopelle.scott - that’s a known problem in Windows right now…

nerdpack:clone -r

This command will clone the repo and automatically regenerate the UUID for that Nerdpack.

You can workaround this by running a standard git clone https://github.com/newrelic/RepoName command.

Then you can change into the directory:

cd repoName

& manually regenerate the UUID:

nr1 nerdpack:uuid -gf

Hi,

Is it possible to check and display health of internal websites? Currently using synthetics with a private minion, but would like to use the statuspage nerdpack if supported.

Thanks!
Sandeep

Hey @sandeep.goli -

Does your internal site report it’s status to a statuspage.io site?

The statuspage.io nerdpack requires that you input a status URL, such as status.newrelic.com

If not, then a private minion is going to be the best way to monitor internal sites.

I am stuck in a cycle of dependencies that are required. right now I have “tsutils@3.17.1 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself. message”

Hi @david.heinz -

I just downloaded a fresh copy of the status pages nerdpack, after running npm install, I got the same message:

npm WARN tsutils@3.17.1 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.

Importantly, this is a warning message, rather than a blocking error

I was still able to run npm start following that message and the nerdpack worked as expected.

I’m going to tag in @dgolden - who has done a lot of development work on that nerdpack, so he may be able to dig into this more. But for now, you should be ok to still use the nerdpack regardless of that warning message.

Thank you. Shortly after I posted this I realized I was stuck on the fact they were warnings. It started fine, I have a bunch to learn in customization but it’s a good start.

1 Like

Great! Glad to know it’s working for you now :smiley:

Hi, I have installed the nerdpack, resolved all dependency issues and add the OOB cards for new relic and Github. They all work fine. However, when i attempt to add a NRQL card, i get a page that says oops something went wrong. Any advise?