Resources in Nobl9
For further work with Nobl9, create resources—projects, services, data sources, SLOs, alert policies, alert methods, and, in some cases, role bindings.
Projects are the basic logical grouping of resources in Nobl9.
They contain all other resources—services, data sources, alert policies, and alert methods. Services, in turn, encompass SLOs, and SLOs hold objectives.
The core hierarchy in Nobl9 is Project > Service > SLO. SLOs can only exist within services; no single SLO can belong to more than one service.
Data sources refer to monitoring solutions with which Nobl9 is integrated. They provide data for your SLOs.
Alert policies are the conditions you configure to get notifications when SLO reports undesired data. You attach alert methods to them—the ways you wish to be notified should this happen.
SLOs can be created based on any data source you have in the project. Alert policies can be attached to any SLO within this project.
Project-agnostic labels streamline work with your Nobl9 resources.
Change history Enterprise
The Change history feature is available to all users with resource access in Nobl9 Enterprise Edition.
A comprehensive changelog is available under the Change history tab on SLO, project, and service details. It tracks:
- Total number of changes
- Change details
- Timestamp
- User who made the change
- Tool used to implement the change
Tools
The list of tools used to implement every modification is as follows (not all tools are applicable to SLOs):
| Tool used | Description |
|---|---|
| Agent | N/A  |
| sloctl | Changes applied using sloctl |
| Browser | Changes made through the Nobl9 Web interface |
| Terraform | Changes applied using the Nobl9 Terraform Provider |
| System | Changes performed by internal system processes |
| SCIM | N/A |
| SDK | Changes made using the Nobl9 SDK for Go |