Convert monitoring alert test in pytest tests (!8784) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Convert monitoring alert test in pytest tests.

Use prometheus-api-client lib instead of prompql CLI

Implement few tests:

Revisit the existing watchdog check to ensure prometheus was alive during the last 30m. Initially this test was looking if we have 30 watchdog alert during the last 30min. This was working fine as the test was started late in the CI pipeline but with our new framework the test is running just after the mgmt cluster deployment (so Thanos is not up since 30minutes), same issue when we run test manually on fresh platform. New version of the test is looking if we have gap over the last 30minutes, and if last sample are not older than 1minutes.
New smoke test that dump all alert over the time window. Dump everything in one file and also in sub files per severity to ease the debug
Existing critical alert firing
Existing Cluster_maxunavailable_* alert fired during the past TIME_WINDOW

Each test dump alert in multiple format (.json & .txt) For the .txt, series are reformatted to have a quick overview timeline

                                                 samples  09:17──────────────────────────────────────────────────13:17
  Thanos-Receive_No_Upload                            89  ·····································▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇

Test coverage

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited Aug 07, 2026 by Loic Nicolle

Convert monitoring alert test in pytest tests

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports