monitoring-authoring

To create monitoring resources for a new component, author PrometheusRule, ServiceMonitor, and PodMonitor configurations, place them in config/monitoring, and register them in the appropriate kustomization for platform-wide observability.

Standardize monitoring resource placement by ensuring Prometheus resources follow labeling conventions, reside in the monitoring namespace via kustomize, and use standardized templates for PrometheusRule and ServiceMonitor configurations.

Update AlertmanagerConfig and PodMonitor resources when adding monitoring for a new component or adjusting existing monitoring to reflect changes in the system across clusters, namespaces, and subsystems.

Yes, kustomize works with Prometheus monitoring resources by registering them within kustomization files, ensuring they reside in the monitoring namespace and follow platform-wide labeling conventions.

Yes, you can use Canary configurations alongside ServiceMonitor by following standardized templates for Canary setups and registering them in kustomization for component monitoring visibility.

Prometheus alerts may not follow labeling conventions if the PrometheusRule resources are not properly standardized or registered in the appropriate kustomization within the monitoring namespace.