We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
monika_probe_result
Describe the bug The monika_probe_result metric is stuck on 1 / success
To Reproduce Steps to reproduce the behavior:
probes: - id: 'mock-1' name: 'local-test-test' requests: - url: http://0.0.0.0:7001/v1/hello alerts: - assertion: response.status < 200 or response.status > 308 message: HTTP Status is not 200 - id: 'http-1' name: 'status-200-test' requests: - url: https://httpbin.org/status/200 method: GET alerts: - assertion: response.status < 200 or response.status > 308 message: HTTP Status is not 200 - assertion: response.time > 2000 message: Too slow
npm start -- --prometheus 3001 -c config.yaml
localhost:3001/metric
Expected behavior The metric monika_probe_result should show 0 for a failed probe and 1 for success
Screenshots both probes running and when mock probe is disabled:
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the bug
The
monika_probe_result
metric is stuck on 1 / successTo Reproduce
Steps to reproduce the behavior:
npm start -- --prometheus 3001 -c config.yaml
localhost:3001/metric
on your browserExpected behavior
The metric
monika_probe_result
should show 0 for a failed probe and 1 for successScreenshots
both probes running and when mock probe is disabled:
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: