Include IPv4/6 status in API
Thomas Jensen
It would be useful if the check IPv4/6 offering was included in the API, that way I could integrate an external IPv6 check into my local Uptime Kuma instance.
Log In
Adrien Rey-Jarthon
I'm not sure what you mean exactly, are you talking about a new API endpoint to issue a single check that you could trigger from another monitoring service? Or about exposing the separate IPv4 and IPv6 status from your existing updown checks?
Thomas Jensen
Adrien Rey-Jarthon The latter, so adding it to this data set: https://updown.io/api#GET-/api/checks/:token, something simple to parse - like:
offers_ipv4: true
offers_ipv6: false
Adrien Rey-Jarthon
Thomas Jensen Ok I see, I'll have to think about this because this would add little value for most people and if I had to include every other information the dual stack monitoring under easy to parse attributes it would be way too long. If I were to add more details to the check endpoint covering this, I would probably add the same "results" attribute which exists in the /downtime endpoint (https://updown.io/api#GET-/api/checks/:token/downtimes) covering the last 5 requests for this check. This would include a lot of information (including dual stack) but probably in a less easy to parse fashion (you can see the format by hitting the /downtimes?results=true endpoint).
Could you clarify what you be your usecase with this attribute and Uptime Kuma ? I'm not sure I get the idea.
Thomas Jensen
Adrien Rey-Jarthon Hello, yeah, I get it. My usecase was to add an API check to Uptime Kuma, so I could get an internal alert if IPv6 connectivity went to false. But rethinking this; I can just add the IPv6 address as a check, and would accomplish the same.
Adrien Rey-Jarthon
Thomas Jensen Ah ok, but updown already send alerts if IPv6 connectivity is lost, you don't need a specific IPv6 address check.