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

implement 'pause' for hosts via agent #15

Closed
NickTitle opened this issue Jun 8, 2017 · 2 comments
Closed

implement 'pause' for hosts via agent #15

NickTitle opened this issue Jun 8, 2017 · 2 comments

Comments

@NickTitle
Copy link
Contributor

NickTitle commented Jun 8, 2017

From the kolide/cloud ui, a user would be able to 'pause' a host from reporting up to cloud.

concept

'pause' is the core concept because:

  • the host would NOT stop checking in, so that if a user decides to 'unpause' the host, they'd pull this info down in a subsequent configuration
  • this host would be temporarily removed from live/scheduled querying and workspaces, but data about the host would be kept

questions

  • what do we do about data that osqd generated while the host was paused? does that fill up rocksdb or do we discard it?
  • do we count hosts against host quotas while paused?
@NickTitle NickTitle changed the title implement implement 'pause' for hosts via agent Jun 8, 2017
@marpaia
Copy link
Contributor

marpaia commented Jun 15, 2017

I think that if a host is paused, we should kill osqueryd and just maintain lightweight comms just to see if the agent becomes unpaused. I think paused hosts should count against your limit, you shouldn't be so tight on it where that really matters. I'm open to discussion on that though, I don't feel very strongly about it.

@marpaia
Copy link
Contributor

marpaia commented Jul 19, 2017

Closing this for now as we have no current plans to implement this feature in the product.

@marpaia marpaia closed this as completed Jul 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants