How to Use StatusCast and New Relic to Inform Customers About Site Performance
Join the DZone community and get the full member experience.Join For Free
guest author alex bloom is founder and ceo of statuscast , formerly uptime.ly.
devops wants to focus on solving problems, not on communicating about them (especially not while those problems are still causing headaches). marketing wants every interaction with the customer to cultivate a positive impression. but what do you do when customers can’t access your web-based application? or when they experience a disruption in performance?
it’s counterproductive to distract your it staff by demanding they craft status updates—especially when you have an application performance monitoring (apm) tool like new relic that can automatically report on system status in real time. statuscast is a new tool built for new relic customers and others who understand that application downtime is a marketing issue as much as it is an it issue.
given the dual impact on marketing and it, you not only need to resolve downtime issues quickly, but you need to provide updates about the scope of the issue, the progress you’re making, and when full functionality will be restored. and you need to do it in a manner convenient for your customers, using simple, clear terminology that makes sense to them without sounding condescending.
statuscast is designed to equip your devops and marketing teams to translate the technical information provided by new relic apm into user-friendly status updates that go out to customers. in a matter of minutes, you can set up an application status page where end users can get status updates—and they can subscribe to receive updates via their preferred communication method (email, text, etc.). your statuscast page and update communication tools can also be valuable internally, informing executive staff, customer support, and whomever else needs to be apprised of your uptime/downtime status.
the combination of new relic and statuscast is designed to free your devops team to focus on what they do best, while still giving your customers the timely, professional communication they demand. integrating the two services is simple. if you do not yet have both a new relic and a statuscast account, you can sign up here: newrelic.com/statuscast
for existing statuscast and new relic customers: 3 immediate steps to implement your integration
1. set up your api key
before you get started, find your new relic api key by logging in to your account and selecting account settings > integrations > data sharing.
copy your api key, navigate to the integrations section of your statuscast admin portal ([yourapp].statuscast.com/admin), and select the install button under new relic.
enter your api key here and click the install button. now new relic can communicate with your statuscast application.
2. automate incident posting
navigate to the monitors section. select the new monitor button to start the configuration.
choose new relic from the choose provider drop down.
next, select the alert name from the list (this will correspond to a specific application in your new relic account). enter a name for authored by, which defines who is the author of each incident. just like normal incidents, a post can have only a single author:
the other incident settings, including type, affected components, subject, and message, reflect the same general options you have when creating an incident. for more information on this process, please refer to statuscast’s article how do i post a new incident or status?
at this point you can set up a workflow for the incident:
once you set all the configurations, click submit to save the configuration.
3. add new relic metrics to your statuscast page
to configure the metric, navigate to the layout section. drag the metric widget into your pages layout, select the pencil edit icon, and select new metric.
from here you can configure the metric you’d like to display:
enter a friendly name to identify this metric within statuscast.
choose provider: select new relic as your provider.
choose application: select the application from your new relic account from which you want metric data made available to statuscast.
metric: select the type of metric you wish to make available, e.g., response time .
select save to add the new relic metric to your layout, and to finalize these changes, select the save & publish option on the right.
now that your metric has been added to your statuscast page, navigate to the page to see it in action!
software-as-a-service providers earn their customers’ trust by treating application downtime as a marketing issue just as much as a devops issue. integrating apm reporting and customer communication systems helps accomplish this without distracting devops from resolving the issue. combining new relic and statuscast lets you enjoy the benefit of the integrations webhooks make possible: get started here!
Published at DZone with permission of Fredric Paul, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Effective Java Collection Framework: Best Practices and Tips
RAML vs. OAS: Which Is the Best API Specification for Your Project?
DevOps Midwest: A Community Event Full of DevSecOps Best Practices
How To Manage Vulnerabilities in Modern Cloud-Native Applications