Nobl9 application (1.187.0)
· 2 min read
We've just released Nobl9 1.187.0! Release highlights:
new
keep up to date!
Keep tracking the latest changes in Nobl9 and subscribe to our Application RNs RSS Feed Release details
new Multi-component Status Page disruptions
You can now register a single Status Page disruption on multiple origin components at once, including components from different parts of the component tree.
The disruption propagates to the ancestors of every origin, and a single clear, update, or severity change then applies to all of them.
new Manage Status Page disruptions over HTTP API
Machine-to-machine integrations can now manage Status Page disruptions using HTTP Basic authentication with an access key (clientId:clientSecret), the same method already used for external issue reporting.
External monitoring and automation systems can register a disruption, change its severity, and clear it without a browser session.
The register-disruption endpoint now returns the disruption
id so Basic-auth clients have a handle for follow-up change-severity and clear calls. See the Organization status API reference.