cortex-tools

cortex-tools copied to clipboard

Confusing parse error messages when using loki backend

4

Given `bug.yaml`: ``` namespace: bug groups: - name: bug rules: - alert: AlwaysFire expr: vector(1) ``` `cortextool rules lint --backend=loki bug.yaml` gives: ``` ERRO[0000] unable parse rules file error="could not...

ekpdt

Reorder return values for SummarizeChanges in sync

1

Swap "created" and "updated" to set values correctly. Fixes #267.

coderalex

What is the difference between the `load` and `sync` commands?

2

At the moment, it is unclear what is the _exact_ difference between both commands. From a quick peek at the code it seems like load is more of a "only...

gotjosh

Currently, `rules sync` is reporting the number of groups created as the number of groups updated and vice versa. To fix, we need to have `created, updated, deleted` instead of...

coderalex

Update Grafana Mimirtool in plain text, and

2

perform minimal minor edits.

osg-grafana

cortextool is the only frontend for now that also support uploading loki rules (not supported by mimirtool yet). However it is not longer compatible with any go version that is...

Mic92

Add function to analyse used labels, and not just used metrics.

1

This is a WIP PR which analyses the usage of labels, and not just metric names. The idea is eventually we'll be able to identify labels we can drop /...

tomwilkie

fix(analyse_prometheus): store errors instead of exit

7

Fixes #236 Make sure you have `metrics-in-grafana.json` file in the directory. ```golang $ go run ./cmd/cortextool analyse prometheus --address --log.level="debug" --read-timeout=5m ```  Signed-off-by:...

Dentrax

I'm trying to tell Grafana which datasource to use for an alerting query, but I can't find any documentation for this in the rules YAML syntax. I see in the...

justinTM

Hello! I think the README is missing documentation on how to construct an alert; the YAML syntax of the tool; how to manage groups of rules and notifications. A simple...

justinTM