Migrate Statuspage to use Atlassian accounts
Learn everything you need to know to migrate you and your team to Atlassian accounts.
System metrics are a great way to build trust and transparency around your organization.
Submitting data for a custom metric is as easy as sending a POST request with the timestamp and value of the data point. You can also manage system metrics in the management interface under Your page > System metrics.
Take note that there are a couple of constraints and considerations when submitting data:
At a minimum, one data point must be submitted every 5 minutes. If there is a lag in data, the gap will be reflected on the charts for the “Day” view.
Each data point is cast to its nearest 30s interval, giving us a maximum of 10 data points per 5 minute period. Submitting multiple data points near each other will result in the last data point being the only one stored.
The timestamp value returned in the body of the response will be the casted timestamp used to store your data.
Data can, and should, be backfilled up to 28 days in the past.
Statuspage believes strongly that transparency should be a virtue that all companies embrace. The benefits are numerous, and include things like increasing customer trust, winning prospective customers, and deflecting possible inbound support requests if customers can self-diagnose issues.
Example custom metrics that we feel embody good transparency and give a lot of value to the user include:
API response time
Web server uptime
Average time an outbound request sits on a queue
Max time an incoming piece of data sits on a queue before ingested
Average time before first reply on customer support requests
Current exception rate of all requests
Here's a video detailing how to use a metrics provider to add a metric to your page.
You can now send add metrics to your page by sending us data via the API. See our developer documentation for sending and getting metrics data: Metrics API documentation
If you're using an audience-specific page, you can choose what visibility users and groups have into metrics. This is similar to how you choose the visibility of components for different users and groups.
If a subscriber hasn't set up their subscription preferences they'll automatically be subscribed to any new components/system metrics.
If a subscriber has already changed their subscription preferences, they will not automatically be added to new components/system metrics. You will need to edit the audience-specific group or user under Audience to give them access to the new component/system metric.
Was this helpful?