We have some per-VM usage analytics that are ingressed into postgres. Users may not need/care for this and the data might just be noise for them. It would be valuable if we had some sort of Hyper.Vm.Analytics.Behaviour that was implemented by a Hyper.Vm.Analytics.Pg, Hyper.Vm.Analytics.Prom and a Hyper.Vm.Analytics.Nop, so that users can configure how they want their analytics to work.
For the sake of this issue, we should probably implement Analytics.Pg and Analytics.Nop and leave prometheus for later.
We have some per-VM usage analytics that are ingressed into postgres. Users may not need/care for this and the data might just be noise for them. It would be valuable if we had some sort of
Hyper.Vm.Analytics.Behaviourthat was implemented by aHyper.Vm.Analytics.Pg,Hyper.Vm.Analytics.Promand aHyper.Vm.Analytics.Nop, so that users can configure how they want their analytics to work.For the sake of this issue, we should probably implement
Analytics.PgandAnalytics.Nopand leave prometheus for later.