Great ideas, thank you! I have found under the related videos another useful one: youtu.be/qeVhFyqDbJs?t=354 The main idea is that monitoring items can be separeted into 3*3 different categories (area - infrastructure, application, business; concern - health, performance, capacity; and interaction - passive, proactive, reactiv) - and any combination of these categories is viable (e.g. "how much CPU do I have left?" -> infrastructure, capacity, passive)

The system consits of several microservices

Yes (in my case), reporting could be separeted from monitoring data; the reason, for not doing this, is that our system is not that complex, and adding an additional reporting application, would result in a much more complex infrastructure to manage. However, I like the idea to monitor the cost of the system, thank you (updated my question with this information).

Thank you; yes, this data if vital - but I do not feel it is enough/complete (it covers the hardware data layer I mentioned in the question)