Skip to content
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

Closed
Ernst2020 opened this issue Oct 28, 2024 · 13 comments
Closed

Two questions #257

Ernst2020 opened this issue Oct 28, 2024 · 13 comments

Comments

@Ernst2020
Copy link

Hi,

Two questions:

  1. Is there a way to make a distinction between hardware and software probes?

  2. Is logging on a hardware probe in RAM? If not, the SD card will have low life expectancy.

Regards,

Ernst

@jimaek
Copy link
Member

jimaek commented Oct 28, 2024

  1. Where exactly? We do have a way to differentiate them on the API level thanks to env vars that hw probes set
  2. Everything is in RAM, the sd card is read-only and is barely touched (Note that in certain cases we do write to some card partitions, but its something we thought out :) ). We work with an experienced IoT developer and of course we thought of such issues. And the OS itself https://www.yoctoproject.org is also designed for such use-cases, which we compile specifically for our hardware and software. It's part of what makes the probe secure, not only we don't open any ports, we don't even include most of the unrelated software that could potentially be abused.

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

@Ernst2020
Copy link
Author

Ok. Thanks!

  1. Will need to explore the API more.
  2. Excellent. Some users were worried about this.

@Ernst2020
Copy link
Author

Had a look at the API docs at https://globalping.io/docs/api.globalping.io#overview

No mention of env_vars?

@jimaek
Copy link
Member

jimaek commented Oct 28, 2024

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

@Ernst2020
Copy link
Author

Ah. I wanted to see how many of the shipped HW probes are currently installed since only 27 new probes appeared since October 5th.
Can you easily generate an overview of which of the probes in NL are hardware based? And email me?

@MartinKolarik
Copy link
Member

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.

@alexey-yarmosh
Copy link
Member

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.

@Ernst2020
Copy link
Author

Still the internal API is meant I guess?

@alexey-yarmosh
Copy link
Member

yes(

@Ernst2020
Copy link
Author

Any plans to add the distinction to externally visible data?

@MartinKolarik
Copy link
Member

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.

Ah, we're returning the property only if it's true, slightly confusing 😄

@MartinKolarik
Copy link
Member

Any plans to add the distinction to externally visible data?

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.

@jimaek
Copy link
Member

jimaek commented Oct 31, 2024

We could make the probe type public as part of this page jsdelivr/www.jsdelivr.com#689
I'll make a note

@jimaek jimaek closed this as completed Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants