nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to indicate affected components when backfilling an incident

Jeremy Goldsmith

I have to backfill an incident and have filled in the description, but I see no way to indicate which components were affected. As we have an Access Control package, allowing clients in each shard only to view their own components, anything I add without indicating a component will be invisible to everyone.

Is this accurate, or is there a way for me to do this so that it shows up for the one affected shard? Currently I suspect that I cannot effectively backfill anything as nothing will show up for our clients in the affected shard.

If that is accurate, is there any way to make a feature suggestion that we are able to set the affected components?

Accepted answers

Nick Cruickshank

As far as I am aware, you would need to go to each affect component and on the uptime graph, select the day and update if there was a partial or major outage and the length of time.

I hope this helps.

Regards,

Nick

All comments

Nick Cruickshank

As far as I am aware, you would need to go to each affect component and on the uptime graph, select the day and update if there was a partial or major outage and the length of time.

I hope this helps.

Regards,

Nick

Jeremy Goldsmith

Top moves, Nick; thank you very much!

vishal.shah_8fd75b

but this doesn't help completely. Since on the status page when you hover over the affected day, it shows the downtime but says no associated incident tied to it. how to you link the historical manually entered incident to the manually edited component down time

Jeremy Goldsmith

Agreed. I think this is not possible and is a missing part of the functionality. I have been unable to find anything to suggest that this can be done and even the suggested answer above goes less than half way to achieving the obvious desired outcome.

From my perspective, it's even worse than you described as the historically entered incident is invisible to our clients on the affected shard, since they can only see things related to their shard and it can't be tied to any when adding historically. The result is an orphaned description which only my team can see (utterly useless) and recorded degradation time with no corresponding incident as far as our clients can see.

Corbin Johnson

I've found that by creating an incident for now (and not selecting the "backfill" checkbox) you can, after the incident is created, modify the start and end time. That way you can pick which components are affected.

It's not intuitive but it does work.

Jeremy Goldsmith

A great suggestion, Corbin. Thanks for taking the time to write it up for us.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

statuspage