You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have recently changed our SLA metrics and wish to update the historical view of statuspage to report on uptime according to our new metrics.
How can we manipulate the statuspage database to account for any historical changes we want to do?
Tks
Hello Rémi,
Welcome to the community and thanks for the question about manipulating the database to try and change your uptime.
Statuspage does not have any direct database manipulations. The closest thing we would have would be to utilize the API but even there, we don't have an automated way to manipulate the uptime data for components.
Statuspage is a good tool to show when components are down and for incident communication but it might not be the right tool for calculating uptime. For example, we consider partial outages as 30% as bad as a major outage so if you mark something as a partial outage, it could not reflect your downtime as you intended. If you haven't already, please take a look at the following article that goes over how uptime is calculated:
https://support.atlassian.com/statuspage/docs/display-historical-uptime-of-components/
I am curious about your use case on how you want to change your uptime on components. If you had any insight to offer, I would love to understand.
Regards,
Jesse
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.