Files

Alexander Akhmetov c7c68322b1 Alerting: Allow specifying a folder for Prometheus rule import (#101406 )

What is this feature?

Allows the creation of alert rules with mimirtool in a specified folder.

Why do we need this feature?

Currently, the APIs for mimirtool create namespaces and rule groups in the root folder without the ability to set a custom folder. For example, it could be a special "Imported" folder, etc.

This PR makes it possible with a special header: mimirtool ... --extra-headers="X-Grafana-Alerting-Folder-UID=123". If it's not present, the root folder is used, otherwise, the specified one is used.

mimirtool does not support nested folder structures, while Grafana allows folder nesting. To keep compatibility, we return only direct child folders of the working folder (as namespaces) with rule groups and rules that are directly in these child folders as if there are no nested folders.

For example, given this folder structure in Grafana:

```
	grafana/
	├── production/
	│   ├── service1/
	│   │   └── alerts/
	│   └── service2/
	└── testing/
	    └── service3/
```

If the working folder is "grafana":

    Only namespaces "production" and "testing" are returned
    Only rule groups directly within these folders are included

If the working folder is "production":
   -  Only namespaces "service1" and "service2" are returned
    Only rule groups directly within these folders are included

2025-03-03 17:59:01 +01:00

alertmanager

Alerting: Stop running AM integration tests on CI (#100702 )

2025-02-14 16:55:20 +01:00

api

Alerting: Allow specifying a folder for Prometheus rule import (#101406 )

2025-03-03 17:59:01 +01:00

apis

Provisioning: Define large parts of our infrastructure (#101029 )

2025-02-24 09:08:58 +01:00

testinfra

fix (unified-storage): stop registering unified storage metrics in global state (#101322 )