Investigate feasibility of serving as a data collector API #311
Description
There are some appealing features that would be made possible if chefbrowser hosted an endpoint for data collection (https://docs.chef.io/automate/data_collection/). However, doing this also makes an otherwise very simple read-only application much more complex.
I don't have any desire to recreate the functionality of Chef Automate in this project, but I'm not against the idea of collecting the same data and using it to display statistics about the last chef client run on each node page.
I don't have any desire to recreate the functionality of Chef Automate in this project, but I'm not against the idea of displaying statistics about the last chef run on each node page.
Some napkin considerations:
- Must be configurable and disabled by default
- Storage solution should be scalable but if feasible something like sqlite should be considered for small environments
- Periodic clean ups will be necessary. Either with a configurable TTL or by pruning records for nodes that are no longer returned by the chef server API.
- Should be possible to run as a separate service to fail gracefully without taking down the chefbrowser application