SLO annotations
Create, update, retrieve, and delete annotations added to SLOs in your organization.
Authenticate API requests using an access token.
Include it in the Authorization header as: Bearer TOKEN.
User and system annotations
SLO annotations can be created by users (user annotations) and Nobl9 (system annotations). System annotations relate to alert, budget adjustment, and no data anomaly events.
Nobl9 automatically creates system annotations for each alert, budget adjustment, and no data anomaly event.
Learn more about SLO annotations in Nobl9.
Annotations quota and rate limits
A quota limits the number of user annotations to 100 000 annotations per organization.
For rate limits, refer to the Rate limits section.
RBAC
The following permissions apply to annotations:
- Organization level
- All organization roles can view user and system annotations
- Organization admins and responders can view, create, edit, and delete user annotations
- Organization admins can delete system annotations
- Project level
- All project roles can view user and system annotations
- Project owners, editors, and responders can view, create, and edit annotations. They can edit and delete annotations they created.
- Project owners and editors can delete system annotations
Authentication
- HTTP: Bearer Auth
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |