You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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 theregistration ID
to store. (Currently we only have one "default" registration ID.)We should add the instances' statuses to the status blob returned by localserver.
The text was updated successfully, but these errors were encountered: