I'm going with A. The Agent Collector sounds like the workhorse of the bunch, getting its hands dirty with the actual data collection. That's the kind of thing I'd expect to see in a CI tool.
I see your point. D) Check Definitions could also play a role in executing the commands. It might define what specific checks need to be performed on the agents.
You could be right. But I still think A) Agent Collector is the main player here. It's probably the one coordinating everything and collecting the attribute details.
I'm not sure about that. I think E) Policies could also be involved in executing the osquery commands on agents. It might set the rules for what data to gather.
I think B) Agent listener might also be a good choice. It sounds like it could be responsible for listening to the commands and executing them on the agents.
Hah, the Agent Listener? That's a good one! I bet that's the guy who just sits around and listens to the agents complain about their working conditions.
I'm not sure about that. Wouldn't the ACC for Discovery be the one handling the discovery and inventory of the assets? It seems more logical that the Agent Collector would be the one executing the osquery commands.
Option A seems like the right choice here. The Agent Collector would be responsible for executing the osquery commands and gathering the attribute details from the agents.
Eura
2 months agoLauran
2 days agoTiara
4 days agoShonda
13 days agoElfrieda
21 days agoLacey
2 months agoJani
28 days agoOlive
1 months agoElina
1 months agoKaran
3 months agoMarci
1 months agoClay
2 months agoElenor
2 months agoDarci
2 months agoMarica
3 months agoLeslee
2 months agoChun
2 months agoLoreen
3 months agoYuette
3 months agoNieves
3 months agoShonda
3 months ago