-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
How to determine results of owned probe in output #128
Comments
If I understand correctly you would like your own probes to be somehow marked in the results of CLI? We will soon launch our user dashboard, you could then adopt your probes by proving ownership. Then if you authenticate the CLI with your API key the API would know which probes are yours and we could visually mark them in the CLI, as well as add tags in the raw JSON responses. Would that be helpful? |
Yes. Any functionality that would add a way to identify my probe in output of the CLI would help to compare results. |
It's an interesting idea, but the probe "ownership" is not public information at the moment. If we were to add this automatically for all measurements, I wonder if it wouldn't raise privacy concerns for some people. It could perhaps be a user setting? |
It would be added only if the user provides the API key. So no privacy problems |
Hi,
If I do a measurement, how do I determine the results of my probe in the output?
For instance if I do a ping measurement towards a certain IP using all 106 probes in The Netherlands, how do I compare the results of my probe to the other 105?
Currently my probe is the only one in the city Globalping assigned it so I can filter on city, but what if another probe is assigned to that city?
In the list of all active probes there is a "tags" field in the json output. How can I add a tag? The tags don't seem to be in the output of the CLI but is it possible to use tags for this purpose perhaps?
Regards,
Ernst
The text was updated successfully, but these errors were encountered: