Welcome to the October docs digest! Sensu 6.1 is here, with important performance and stability gains, improved search syntax and suggestions in the web UI, support for custom secrets engine paths in Vault secrets, and much more. If you’re using Prometheus client libraries to instrument your applications, as of 6.1.0, the Sensu Go agent can scrape and enrich those metrics. We’ve also released 6.1.1 and 6.1.2, with fixes for sensuctl prune and sensuctl dump as well as form validation for subscription names in the web UI.
New features in October
- The Guides section homepage is now the Guides Index, which lists and links to all of the how-to guides throughout the Sensu Go documentation — Read Discourse post
New and updated content in October
- State attribute and Flap detection algorithm docs.sensu.io/sensu-go/latest/observability-pipeline/observe-events/events/#state-attribute
- Back up and recover resources with sensuctl (updated with commands for exporting resources from all namespaces) docs.sensu.io/sensu-go/latest/sensuctl/back-up-recover/
- Update resources with PATCH (example at docs.sensu.io/sensu-go/latest/api/apikeys/#update-an-api-key-with-patch) — the PATCH method is now documented for API keys, assets, checks, cluster role bindings, cluster roles, entities, filters, handlers, hooks, mutators, role bindings, and roles
- Etag response headers docs.sensu.io/sensu-go/latest/api/#etag-response-headers
Most popular docs in October
- Sensu Go | Installation guide docs.sensu.io/sensu-go/latest/operations/deploy-sensu/install-sensu/
- Sensu Go | Sensuctl CLI docs.sensu.io/sensu-go/latest/sensuctl/
- Sensu Go | Checks reference docs.sensu.io/sensu-go/latest/observability-pipeline/observe-schedule/checks/
October releases
- Sensu Go 6.1.2 | docs.sensu.io/sensu-go/latest/release-notes/#612-release-notes
- Sensu Go 6.1.1 | docs.sensu.io/sensu-go/latest/release-notes/#611-release-notes
- Sensu Go 6.1.0 | docs.sensu.io/sensu-go/latest/release-notes/#610-release-notes
We’d love to hear your feedback and suggestions — leave a comment here on Discourse, post in the community Slack, or open a docs issue!