Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rule: Alerts will not be deleted after curl -X POST localhost:10902/-/reload. #1739

Closed
Kirchen99 opened this issue Nov 11, 2019 · 2 comments
Closed

Comments

@Kirchen99
Copy link

Thanos, Prometheus and Golang version used:

0.8.1

What happened:
I deleted alerts file and used curl to reload thanos. But the alerts are still in thanos-ruler.

What you expected to happen:
The alerts should be disappeared from thanos-ruler

How to reproduce it (as minimally and precisely as possible):
kubectl apply -f rules.yaml

apiVersion: v1
kind: ConfigMap
metadata:
  name: rule-test
  namespace: monitoring
data:
  test_rules_alerts.rules.yaml: |-
    groups:
    - name: test.alarm
      rules:
      - alert: TEST-ALARM
        expr: vector(1)

curl -X POST localhost:10902/-/reload.

Then the alert is in thanos-rule.
And now:

kubectl delete -f rules.yaml
curl -X POST localhost:10902/-/reload.

The alert is not disappeared.

Full logs to relevant components:

{"caller":"rule.go:441","level":"info","msg":"reload rule files","numFiles":1,"ts":"2019-11-11T14:45:15.926305365Z"}

{"caller":"rule.go:441","level":"info","msg":"reload rule files","numFiles":0,"ts":"2019-11-11T14:45:27.957372263Z"}
@GiedriusS
Copy link
Member

Probably related to this: #1439

@stale
Copy link

stale bot commented Jan 11, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 11, 2020
@stale stale bot closed this as completed Jan 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants