docs(SaaS): Add Cluster Metrics endpoint documentation for Camunda 8 SaaS monitoring

[zaycodes]

Description

This PR introduces a new Monitoring section under Camunda 8 SaaS and adds documentation for the Cluster Metrics endpoint.

Epic - https://github.com/camunda/product-hub/issues/2229

The documentation covers:

• An overview of monitoring in Camunda 8 SaaS
• How to set up and manage the Cluster Metrics endpoint in Camunda Console
• How to configure monitoring systems to scrape metrics from the endpoint

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
• This is already available but undocumented and should be released within a week. (add available & undocumented label)
• This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
• This is part of a scheduled alpha or minor. (add alpha or minor label)
• There is no urgency with this change (add low prio label)

PR Checklist

• The commit history of this PR is cleaned up, using {type}(scope): {description} commit message(s)

• My changes are for an upcoming minor release and are in the /docs directory (version 8.9).

• My changes are for an already released minor and are in a /versioned_docs directory.

• I included my new page in the sidebar file(s).

• I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • Engineering team review
  • Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[github-actions]

👋 🤖 🤔 Hello, @zaycodes! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.8/.

• docs/reference/announcements-release-notes/890/890-release-notes.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[sourcehawk]

@ColRad Can you confirm this?

[ColRad]

No there is no limit on credentials. The user can create as many as they like

[sourcehawk]

@zaycodes There will be a 20 credential limit now, please confirm @ColRad

[mesellings]

@zaycodes nice work on this PR - I've committed a few changes, but otherwise looks good to go! 🚀

[zaycodes]

@mesellings help re-approve after back-porting the changes. Thanks!

[mesellings]

Re-approved @zaycodes - great work 🚀

[Sijoma]

🌱 Have we thought about adding a very simple curl command or so to the docs? This then allows to verify that everything works before setting up the specific monitoring configuration.

cc @sourcehawk, @zaycodes

[sourcehawk]

🌱 Have we thought about adding a very simple curl command or so to the docs? This then allows to verify that everything works before setting up the specific monitoring configuration.

cc @sourcehawk, @zaycodes

The curl command would be:

curl -v -u '<username>:<password>' "https://<target>/<path>"

[afgambin]

@zaycodes @sourcehawk confirmed we can backport this to the alpha 3 release notes. Do you prefer to include it in this PR, or should I open a separate one? Let me know, thanks!

[zaycodes]

@zaycodes @sourcehawk confirmed we can backport this to the alpha 3 release notes. Do you prefer to include it in this PR, or should I open a separate one? Let me know, thanks!

I've added it to this PR, thanks!

[afgambin]

lgtm! Thanks for adding it to the RN :)

[sourcehawk]

Beautiful! 🎉