feat: Globalping support

[Zetanova]

📑 I have found these related issues/pull requests

• Traceroute probe like smokeping / mtr #2911
• Allowing ping/dns/http calls via distributed network (globalpings,ripe Atlas) #4031

🏷️ Feature Request Type

New monitor

🔖 Feature description

monitor support for globalping for alternative http, ping, dns tests
and maybe a new monitor for MTR and traceroute

✔️ Solution

test endpoints from different regions and/or providers for latency and routing issues.

❓ Alternatives

External script that publishes the result to a push-monitor

📝 Additional Context

No response

[jimaek]

Hey, I'm from Globalping. I just found this issue and wanted to let you know we'd be happy to help with the integration in any way we can!

[SchneiderSam]

That feat would be soooo cool. 🥰

[CommanderStorm]

@jimaek How is this different from RIPE Atlas? Seems like the same initative..

See

• Allowing ping/dns/http calls via distributed network (globalpings,ripe Atlas) #4031

[jimaek]

@CommanderStorm Hey, they're similar but RIPE Atlas is more focused on academic and professional use-cases while Globalping aims to be a more accessible and modern alternative. Easier to use API, plenty of tools with good UX, fair limits per IP and even more for registered users. Additionally to get Atlas credits you are required to either host a probe, to ask for someone to transfer you or to pay at least $5k/month. Globalping does not have such limitations.

[grvwy]

I'd like to help out in building this as well!

[CommanderStorm]

I would love the help. ❤

A few pointers:

• before jumping into coding, I would suggest to make a plan how the frontend should look (be it in paint, gimp or on a napkin). Sharing this plan can be very helpful and avoid an back-forth over code.
• We have a two ways of checking things. Primitive checks and those currently only used for the dns monitor (at least since v2.0-beta.2) - depending on what we can push down to globalping, either or could make sense.
• how to add monitoring types is documented here

[jimaek]

Hey all, I was wondering if anything changed. We're ready to contribute an integration but the discussion at #4031 made things unclear if a PR would be accepted.

[CommanderStorm]

Sure, if the implementation is good, i don't see a reason why not. Please keep in mind to keep the pr as tight in terms of functionality as possible as otherwise this feature could require lots of code quite quickly as far as I see things (maybe I am wrong).

The concern about mixing the pings and traceroute/mtr in one pr is mostly that we don't have anything comparable so it would be a very large diff (maybe I am wrong).
Pings should relatively stateless so fine.

The feature would be nice, but not at every cost (maintainability, security, buggy, bad UX ..). But that's what the pr is for to iterate them this sort of thing for it gets merged.

I'm not entirely sure how this would feature would/should work 100% but you are the expert on that so I'm going to defer to you.

Above given some pointers/advice how this should be double. They are still accurate.

[jimaek]

Hey we prepared a draft to check out #6163 (comment)

Let me know what you think and we can expand it to add all measurement types, docs and more