You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have many separate systems that together make up a customer's overall SLA uptime. We would like to be able to record an SLA impacting event in multiple monitors via some type of shared dependency.
For example:
"North America Monitor" feeds into "Region Monitor" which feeds into "Tenant Monitor"
Essentially, status timeline changes in the "North America Monitor" would flow left to right, appearing in the "Region Monitor." "Region monitor" status timeline changes would flow into the "Tenant Monitor."
We could probably accomplish this by associating labels to all of these monitors and reporting against labels, but this currently only works when manually reporting incidents, which also has the issue of not allowing us to fix the start time to reflect the actual start of the event or fix the end time.
This lack of control makes it very difficult to justify paying a fee for manual monitors and we are reconsidering whether we can fully migrate to OneUptime from our current status page solution, which does offer control over status timeline start and end times when reporting issues and when closing them.
Allowing status timeline changes by monitor label where we can control the start and end times would also work for our needs.
The text was updated successfully, but these errors were encountered:
We have many separate systems that together make up a customer's overall SLA uptime. We would like to be able to record an SLA impacting event in multiple monitors via some type of shared dependency.
For example:
"North America Monitor" feeds into "Region Monitor" which feeds into "Tenant Monitor"
Essentially, status timeline changes in the "North America Monitor" would flow left to right, appearing in the "Region Monitor." "Region monitor" status timeline changes would flow into the "Tenant Monitor."
We could probably accomplish this by associating labels to all of these monitors and reporting against labels, but this currently only works when manually reporting incidents, which also has the issue of not allowing us to fix the start time to reflect the actual start of the event or fix the end time.
This lack of control makes it very difficult to justify paying a fee for manual monitors and we are reconsidering whether we can fully migrate to OneUptime from our current status page solution, which does offer control over status timeline start and end times when reporting issues and when closing them.
Allowing status timeline changes by monitor label where we can control the start and end times would also work for our needs.
The text was updated successfully, but these errors were encountered: