-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend tests for Observability stack #401
Comments
@jsmolar I wonder if it would be sufficient as an initial test of dashboards to deploy them with kustomize (mounted via configmap volumes), then use the dashboard api to verify they exist in grafana after it is ready? A similar approach could be used for the example alert rules with the prometheus http api. That, at the very least, should verify they are valid and are imported ok. |
This was referenced May 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Observability automation should include tracing, metrics, dashboards, and alerts, for both Authorino/Limitador standalone and Kuadrant.
Currently, the test suite implements Authorino tracing (supports the usage of Jaeger and Tempo as tracing backends) and metrics.
Documentation
Observability docs: https://docs.kuadrant.io/kuadrant-operator/doc/observability/examples/
Test coverage
Authorino standalone
Kuadrant
Authorino
Limitador
The text was updated successfully, but these errors were encountered: