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

Make the osquery instance status available in the knapsack #1938

Open
Tracked by #1827
RebeccaMahany opened this issue Nov 5, 2024 · 0 comments
Open
Tracked by #1827

Make the osquery instance status available in the knapsack #1938

RebeccaMahany opened this issue Nov 5, 2024 · 0 comments

Comments

@RebeccaMahany
Copy link
Contributor

RebeccaMahany commented Nov 5, 2024

The osquery runner should be able to report on the status of each of the instances it manages. Status should probably be one of unstarted|launching|healthy|unhealthy or similar. Since we are moving toward running multiple instances, status must be stored per-instance -- use the registration ID to store. (Currently we only have one "default" registration ID.)

We should add the instances' statuses to the status blob returned by localserver.

@RebeccaMahany RebeccaMahany changed the title Make the osquery instance status available in the knapsack. We will probably want to add it to the status blob returned by localserver. Make the osquery instance status available in the knapsack Nov 5, 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

1 participant