-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Two questions #257
Comments
For example here is the relevent disk config https://github.com/jsdelivr/globalping-hwprobe/blob/master/meta-jsdelivr/recipes-jsdelivr/jsdelivr-scripts/files/jsdelivr-startWorld.sh |
Ok. Thanks!
|
Had a look at the API docs at https://globalping.io/docs/api.globalping.io#overview No mention of env_vars? |
Sorry I meant an internal API. Meaning we have this information but I wasn't sure where you wanted to see it or how to use it. So that we could potentially add it |
Ah. I wanted to see how many of the shipped HW probes are currently installed since only 27 new probes appeared since October 5th. |
We only have that information for adopted probes, and there are 31 HW adopted probes in NL at the moment. I suspect most of them are related to the recent shipment. |
If I am not missing something, every probe returns hw status to the API. There are 140 NL probes currently, 35 of them are hardware. |
Still the internal API is meant I guess? |
yes( |
Any plans to add the distinction to externally visible data? |
Ah, we're returning the property only if it's true, slightly confusing 😄 |
Generally speaking, the goal is to include data that has a clear use case and value to most users. I don't really see that here. |
We could make the probe type public as part of this page jsdelivr/www.jsdelivr.com#689 |
Hi,
Two questions:
Is there a way to make a distinction between hardware and software probes?
Is logging on a hardware probe in RAM? If not, the SD card will have low life expectancy.
Regards,
Ernst
The text was updated successfully, but these errors were encountered: