Nobl9 application (1.190.0)
- Webhook HTTP signatures
- Treat zero values as no data
- Splunk Observability generally available
- Disruption timeline updates
Release details
new Webhook HTTP signatures
Nobl9 now signs all webhook notifications with HTTP Message Signatures.
Use the signature to verify that a webhook notification came from Nobl9
and that the signed request fields and body were not changed in transit.
Signed requests carry the Content-Digest, Signature-Input, and Signature headers.
Existing webhook endpoints continue to receive notifications without changes. Signature verification is optional, and you can adopt it when your endpoint is ready.
new Treat zero values as no data
No data anomaly detection can now
treat a value of 0 as no data, for data sources that return 0 as a placeholder instead of omitting the data point.
Enable the setting per SLO to have zero values trigger no-data alerts. Existing SLOs keep the previous behavior until you enable it.
new Splunk Observability generally available
The Splunk Observability integration is now self-service for all organizations.
new Disruption timeline updates
Disruptions & impact in Organization status now uses a new update flow for posting changes to a disruption timeline.
A single update can add a timeline comment, change the severity, and amend the scope of impacted components.