Abstraction for cos integration tests

[rgildein]

Context

Since we'll be adding support for observability to all charms, we'll need to test that as well. These tests should be the same in each charm, and that's why an abstraction should be added to chisme. Such abstraction will require the following steps:

• Deploy, relate and assert the grafana-agent-k8s
  • it will be deployed in the test model along the charm
  • it will be related only to the tested charm, so there will be cos deployment
  • since cos relation will be missing, the grafana-agent-k8s will be in blocked state
• Check metrics-endpoint and grafana-dashboards-consumer relation endpoint data bags
  • We need to be able to verify that data bags contains all data needed. e.g. dashboards, scrape_jobs, alert_rules
  • get_alert_rules_from_charm - helper function to collect all alert rules in charm
  • get_grafana_dashboards_from_charm - helper function to collect all dashboard in charm
  • check_grafana_dashboard_relation_data
  • check_metrics_endpoint_relation_data
  • ...
• Check metrics endpoint is accessible
  • This function should check if <workload-k8s-service>:<metrics-port><metrics-path> returns code 200, i.e. that the endpoint is available.

What needs to get done

1. Add function to deploy, relate, ... grafana-agent-k8s to tested charm.
2. Add function to verify that metrics-endpoint data bags contains all data.
3. Add function to verify that grafana-dashboards-consumer data bags contains all data.
4. Add function to verify accessibility of metrics endpoint.

Definition of Done

1. All function above was implemented.
2. All function was tested.
3. The integration test was added, or we tested in with single charm.

[syncronize-issues-to-jira[bot]]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5731.

This message was autogenerated