Rafael4DC
commented
5 months ago Comparative Analysis Table
| Software | Advantages | Disadvantages | Implications for Heimdall |
|---|---|---|---|
| Zabbix | Extensive monitoring capabilities; robust and scalable. | Complex setup; functionality exceeds our requirements. | Ideal foundation for reliability; |
| ActivityWatch | Lightweight; specifically targets user activity; open-source. | Primarily designed for self-monitoring; limited network functionality. | Excellent model for local data collection. |
| osquery | Advanced structured data querying; comprehensive detail. | Focused on system state, not real-time monitoring; complex for our needs. | Cool for a deep dive into data, but probably too hefty for us. |
Strategic Recommendations
- Zabbix: Im going to take a bit of a deeper dive into zabbix when the time comes to make sure we follow a similar architecture, as it seems sound for what we want, since the main issue with zabbix is that its overly complex for what we desire
- ActivityWatch: ActivityWatch has some very readable code on how he collects local data with python. We can leverage this for whatever we are going to do for data collection
- osquery: Cool to know, but useless in practice
So pretty much we are going to: Create an active agent on the cliente side, which will fetch the local data of usage at relevant moments, and send them a (mongo) db, from where the server can collect and process that data. The agent should be a windows service, because altough i didnt find any good example of this softwares working as it, its abilities to relaunch itself and hide itself is important in the context of this aplication
The developer must be able to discuss various software solutions similar to what is intended for Heimdall, focusing on their approaches to data logging and communication. This task should be presented in a table that outlines the advantages and disadvantages of each software, and the chosen solution for Heimdall.