Hi,
We want to rename some and remove some components from our Status Page view which are now obsolete and we don't need to track them any more.
Is there a way to disable those components or archive them so that we can keep the historical data for internal purposes, make them invisible to the outside world and also somehow show/highlight the status page managers that these are disabled/archived components. I noticed,
What is the best way to stop showing (disable) the obsolete components and keep their historical data?
Best regards
Akhil
Hi Akhil!
Thanks for reaching out to Atlassian Community with your questions about managing components on your StatusPage. I’m happy to clarify the options available for renaming, removing, and hiding components while preserving historical data.
Renaming: You can safely rename components directly from your StatusPage admin interface. This will update the component name everywhere, including historical incidents and metrics.
Removing: Deleting a component will remove it from your status page and also delete its historical data. If you want to retain historical data for internal purposes, deletion is not recommended.
Currently, StatusPage does not offer a built-in “archive” or “disable” feature for components. However, there are a few workarounds:
Setting "only_show_if_degraded": true via the https://developer.statuspage.io/ will hide the component from your public status page unless it is in a degraded state.
This is the most common method to make a component invisible to external viewers while keeping it available internally and retaining historical data.
Note: The component will still be visible to StatusPage admins and managers.
The "showcase": true parameter is used to enable component uptime on your status page, not to hide or archive it.
Setting "showcase": false will simply remove the component uptime from the section, but it will still be visible on the page if it’s otherwise active.
There isn’t a native way to visually mark components as “archived” or “disabled” within the admin UI.
As a workaround, you might consider renaming the component to include a prefix like “[ARCHIVED]” or “[DISABLED]” so it’s clear to your team which components are no longer active.
Regards,
Aditya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.