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.
Just set up bloomtext.statuspage.io and added some incidents for a "bloomtext.com" component. These all show as expected on the public page in the "Past Incidents" section. But the "Uptime over the past 90 days" chart is wrong:
For example, despite downtime from Feb 1, 18:30-19:00 PST, and a partial outage 18:30-19:00 PST, the chart shows "No downtime recorded on this day" for Feb 1. Meanwhile, Feb 2 has both a "Major outage" and a "Partial Outage", but just 1 minute each...
Any idea what's going wrong here?
Hello Eric,
in your statuspage main page the data shown is correct, so I suppose the wrong one you mention is in the uptime section.
I'm not sure but I think that the data in the main page represents the date you put into the incident, while the one in uptime represents the component state per day.
So you created an incident for component A on February the 2nd (this will create an incident that day, and put the component outage status for that day), and then you edit the date to February the 1st (the incident's day changes while the component's outage one doesn't). So the component's outage is marked as February the 2nd and not the incidents day.
Indeed you can create an incident without changing the component's status so it shouldn't even appear on the historical uptime
Hope this helps you
I did in fact create the incident after the fact, and then set all the times and dates. If the uptime stats ignore edits, that explains the 1 minute downtimes on the wrong date... Can someone from Atlassian confirm that this is a known issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.