Only "1" appears in localhost:3001/metrics > monika_probe_result.

[Sanitater941]

Creating an API monitoring system using monika.

The API failed intentionally, but on http://localhost:3001/metrics,
The "monika_probe_result" data is not updated, and the past successful history of "1" continues to be exposed.

If it fails, what can I do to get "0" exposed?

---

here is my monika.yml:
(this http request was Failed)

probes:
   - id: '4'
     name: name
     interval: 60 # in seconds
     requests:
      - method: PATCH
        url: {url}
        timeout: 7000 # in milliseconds
        saveBody: true
        headers:
           Authorization: {Authorization}
           Content-Type: application/json
        body: 
           name : name
        followRedirects: 1
     incidentThreshold: 3
     alerts: 
      - assertions: response.status != 204
        message: Status not 204 

[Sanitater941]

hi @sapiderman
is there any update?

[sapiderman]

hi @Sanitater941

I have a question, how many iterations have you let the probe run in your example above? What is the result if you let it run 10 times? Have you tried the --verbose switch to see the logs internally in more detail?

Let me know how it goes.

[Sanitater941]

hi @sapiderman

Yes, based on "id4", If it fails more than 10 times, it is exposed to alert_counter.
but not to monika_probe_result and monika_request_status_code_info.

[sapiderman]

@Sanitater941 thanks for the additional info. Looking into it now.

[sapiderman]

@Sanitater941

I've finally got round to trying it out, so far everything checks out. What is the http response or status code from your PATCH to your url/API? Does the PATCH request fail immediately? a 401 or 404? Did you get the "status not 204" alert?

I'm using this setup (similar to yours).

probes:
  - id: 'http-1'
    name: 'status-401-test'
    requests:
      - url: https://httpbin.org/status/401
        method: PATCH
    alerts:
      - assertion: response.status < 200 or response.status > 308
        message: HTTP Status is not 200
      - assertion: response.ime > 2000
        message: Too sloow

Here's my localhost:3001/metrics

Are you able to get the same result the above config yaml?

[sapiderman]

@Sanitater941

Hi. After a deeper dive and trying a few more scenarios I think I finally understand your initial issue.
monika_probe_result stays 1 and not 0 when the probe fails. This might be a bug, depending on the failure. For instance: if it returns a 4xx, the probe DOES work just returning a bad status. If the probe is unreachable, then it might be right to set it as a fail.

In any case the documentation is lacking for this metric, Will hash it out with the team for proper behavior and will update you! Thanks for all the feedback!

[Sanitater941]

@sapiderman

Thank you.

If there is any revision of the contents(monika), please reply.

[Sanitater941]

@sapiderman

Hi, May I know the progress?

[dennypradipta]

Hi @Sanitater941 ,

I've seen this discussion and decided to change some metrics up. It's still in PR though #1338

I've made a simple dashboard too using the code from the branch. Maybe you could take a look:
https://github.com/dennypradipta/monika-dashboard

Bear in mind this is not yet released, so you might need to build the source from my branch.

[Sanitater941]

@dennypradipta Thank you

A few new metrics have been added!
When it merge, please reply