Recursively search for alert rule files

[arnisoph]

I tried to specify a directory in the main config, which obviously isn't supported. I don't know the actual list of directories that contain these files but I know the structure (see tree below).

The following doesn't work because prometheus expects file paths only:

rule_files:
  - /etc/prometheus-alerts/

The following doesn't work because golang's file globs doesn't support that:

rule_files:
  - /etc/prometheus-alerts/*/*/*.yaml

Example file tree:

$ tree prometheus-alerts
/etc/prometheus-alerts
|-- team1/
|   `-- configmap1/
|       |-- alert1.yaml
|       `-- alert2.yaml
`-- team2/
    |-- configmap1/
    |   |-- alert1.yaml
    |   |-- alert2.yaml
    |   `-- alert3.yaml
    `-- configmap2/

[brian-brazil]

rule_files is a lost of files, not directories. You can use a glob in the filename though (but not the directories).

[arnisoph]

@brian-brazil in this case I expect to be able to to specific something like:

rule_files:
  - /etc/prometheus-alerts/*/*/*.yaml

But golang's file globs doesn't support that. That's my issue, I don't know the actual list of directories that contain these files.

[brian-brazil]

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

[arnisoph]

I've started thread https://groups.google.com/forum/#!topic/prometheus-users/ExJbj-pX-es .

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.