[Feature] Add host_info to api for nodes #838

Closed
opened 2025-12-29 02:24:41 +01:00 by adam · 4 comments
Owner

Originally created by @akelge on GitHub (Oct 23, 2024).

Use case

I am still developing a web UI for headscale and I would really love to add the OS, OS version and tailscale version to the node information.
This can be useful to debug issues and for statistical purposes.

Description

The nodes in the DB have a field called host_info that contains several interesting information, like OS, OS version, tailscale version, arch and even RTT to DERP nodes.
These info, though, are not returned by the REST API.
It would be useful to return them.

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

Add host_info to the field returned when calling /node or /node/<node_id>

Originally created by @akelge on GitHub (Oct 23, 2024). ### Use case I am still developing a web UI for headscale and I would really love to add the OS, OS version and tailscale version to the node information. This can be useful to debug issues and for statistical purposes. ### Description The nodes in the DB have a field called `host_info` that contains several interesting information, like OS, OS version, tailscale version, arch and even RTT to DERP nodes. These info, though, are not returned by the REST API. It would be useful to return them. ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? Add host_info to the field returned when calling `/node` or `/node/<node_id>`
adam added the enhancementstale labels 2025-12-29 02:24:41 +01:00
adam closed this issue 2025-12-29 02:24:41 +01:00
Author
Owner

@ArcticLampyrid commented on GitHub (Nov 19, 2024):

maybe #1205 #1938

@ArcticLampyrid commented on GitHub (Nov 19, 2024): maybe #1205 #1938
Author
Owner

@kradalby commented on GitHub (Nov 21, 2024):

Yes, as @ArcticLampyrid points out, there has been a couple of attempts, it has been blocked by the "strictness" of gRPC which has not allowed us to do this in an ergonomic way without requiring sending the JSON as a escaped string making a terrible API.

I think there are some details in the linked PR/Issues. Happy for someone to work on it, but unless we figure out how to make it "nice" we wont merge it.

@kradalby commented on GitHub (Nov 21, 2024): Yes, as @ArcticLampyrid points out, there has been a couple of attempts, it has been blocked by the "strictness" of gRPC which has not allowed us to do this in an ergonomic way without requiring sending the JSON as a escaped string making a terrible API. I think there are some details in the linked PR/Issues. Happy for someone to work on it, but unless we figure out how to make it "nice" we wont merge it.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 20, 2025):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Feb 20, 2025): This issue is stale because it has been open for 90 days with no activity.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 27, 2025):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Feb 27, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#838