sloctl user guide
Site reliability teams often deal with complex SLO tracking and management challenges.
Nobl9's command-line interface, sloctl, emerges as a streamlined solution,
offering a robust CLI tool
that transforms how you monitor and analyze service performance by complementing Nobl9's reliability monitoring toolset.
Use sloctl to connect data sources, set up alerting on SLI data, create, update, and manage multiple SLOs and objectives at once as part of CI/CD pipelines.
While the Nobl9 web interface provides an easy way to create and update SLOs, sloctl offers DevOps and SRE teams a systematic, code-driven approach to maintaining service reliability objectives with greater automation and precision.
Ready to start casting SLO spells with sloctl? 🪄
- Install sloctl.
- Configure sloctl.
- Dive deep into its capabilities.
- Learn more ways of leveraging the SLOs as code approach.
SLO automation with sloctl
- CI/CD integration:
sloctlintegrates seamlessly with CI/CD pipelines. - Version control: you can keep definitions of SLOs and other resources in your version control system.
- Bulk operations:
sloctlallows you to create or update multiple SLOs and other Nobl9 resources simultaneously. - Advanced configuration:
sloctlprovides access to advanced functionalities through YAML-based resource definitions, including (but not limited to):- Complex alert policies: with
sloctl, you can define alert policies with any number and combination of alert conditions, exceeding the limitations of the Nobl9 Web UI (one condition of a type). - Credential retrieval: you can run the
sloctl get agents --with-keyscommand to retrieve credentials for agents within your organization at any time.
- Complex alert policies: with
- Powerful filtering and transformation: use
--jqflag when fetching object definitions and unlock the processing power of JSON Query language (jq).
Command overview
This section summarizes the top-level sloctl commands.
For a full API visit Command reference.
Check your current context credentials if sloctl returns the access token error:
Error: error getting new access token from the customer identity provider: cannot access the token, customer identity provider replied with 401 {"errorCode":"invalid_client","errorSummary":"Invalid value for 'client_id' parameter.","errorLink":"invalid_client","errorId":"oaejFe6MwoIRo200IuIj7Hp1g","errorCauses":[]}
| Command | Description |
|---|---|
sloctl apply | Apply Nobl9 resource definitions |
sloctl aws-iam-ids | Get AWS IAM role identifiers |
sloctl budgetadjustments | Manage budget adjustment events |
sloctl completion | Generate shell completion scripts |
sloctl config | Manage sloctl configuration contexts |
sloctl convert | Convert external definitions to Nobl9 resources |
sloctl delete | Delete Nobl9 resources by name or definition file |
sloctl edit | Edit Nobl9 resources in the configured editor |
sloctl get | Get Nobl9 resources |
sloctl mcp | Start the Nobl9 MCP proxy over stdio |
sloctl move | Move SLOs between Projects or Services |
sloctl replay | Replay historical SLI data for existing SLOs |
sloctl review | Manage SLO review |
sloctl validate | Validate SLI queries |
sloctl version | Print build and runtime version information |