Kubernetes Classic Monitoring VS Kubernetes experience Monitoring

[Ecataldo88]

Hi All;

Please help me to understand exact difference between Kubernetes Classic and Cloud Kubernetes experience Monitoring (advantages and limitations).

Regards,

[AntonPineiro · Accepted solution]

Hi,

I hope this table is useful:

Best regards

[PierreGutierrez · Accepted solution]

Hi @Ecataldo88 

The painting that AntonPineiro shares is extraordinary.
(From left to right) The first 4 represent Classic Monitoring and the last 2 represent Experience Monitoring.

I share with you my opinion on what I consider advantages of using Experience Monitoring:

- From moment 0, all metrics, events and logs are fed into Grail, so exploiting information with DQL in notebooks, dashboards and workflows is optimal.

- The interface that presents the information has better summaries, groupings and it is easier to access various information from the same point. (Which makes analysis easier)

- The license consumption model (DPS) is much more precise, but also entails greater responsibility in managing its use. (similar to pay as you go)

- The centralization of monitoring, of multi-cloud environments, has greater relevance in this new interface

I hope it's helpful 💪