Revamping argoCD observability documentation (operator manual)

[jsolana]

Summary

The goal of this issue is to improve the Argo CD observability documentation by gathering real-world monitoring practices. This will allow us to refine the Operator Manual with best practices for logs, alerts, and dashboards, ensuring clearer and more actionable guidance for users.

Motivation

While the current documentation covers basic observability aspects such as metrics, it lacks comprehensive examples and best practices for:

• Prometheus dashboards – Essential PromQL queries and panel definitions.
• Logs – Key log events that are crucial for monitoring.
• Alerts – PromQL queries and alert rules that help maintain stability.

A well-documented observability strategy is essential for efficient troubleshooting and performance optimization. By structuring this information properly, we can make ArgoCD easier to monitor, debug, and scale.

Proposal

The proposal is to update the existing observability documentation by filling in missing aspects.

To ensure the most comprehensive and objective improvements, we aim to gather community feedback on how users monitor and operate Argo CD in real-world scenarios. Their insights will help refine the documentation with practical best practices, making it a more valuable resource for all users.

Also related, an as @crenshaw-dev suggested here, we should better-maintain the Grafana dashboard. I think the demo instance is broken. Fixing that would be a great first step.

[jsolana]

Hi! I can work on this issue if it is ok 😄