-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
docs: revise readme #455
docs: revise readme #455
Conversation
I stopped the review at the last comment, will continue after the updates. I think it should be in the tips and tricks section and maybe a mention in the CLI section. The idea is that the magic field can accept not just locations but also previous measurement IDs to select the exact same probes. This is useful for running comparisons of endpoints from the same probes for better data. Or to run continuous tests from the same probes |
RE. new feature #453 Updated the content with info about new feature -> still WIP as I need to add examples (added placeholders)
|
I reworked the section with the available information and added examples. |
@@ -193,124 +242,119 @@ Other acceptable location examples: | |||
- as396982, as16509 | |||
- comcast, google, ovh, orange, t-mobile |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets add:
- eyeball, datacenter
This is completely automated and managed by our platform. | ||
Here's when a probe is considered online and available through our API: | ||
- **It's up-to-date.** A probe running an older version will be forced to auto-update before it becomes available. | ||
- **It passes quality control tests.** Every probe must pass a test, ensuring it's connected to a reasonably stable network without packet loss. This test is done regularly; if a probe fails, it gets taken offline. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets add:
- It's not behind a VPN. We block probes that we detect as being hosted behind a VPN or any other proxying technique. Such probes would report incorrect latency and routing data making them unusable.
Thank you |
A summary of the changes: