Prometheus gets and stores the metrics. Grafana prints out nice looking graphs from metrics provided by prometheus. More on reddit.com

So...this is an example of an xy problem https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem The thing you tried is to get is "a pdf of a dashboard". But that's not what you wanted, since the alternative you described doesn't do that. What you actually wa t to do is record the cpu metric define some rules around that metric notify you when those rules are breached This problem set is fully covered in open-source grafana. It sounds like you already have something pushing the cpu metrics to prometheus (if not, check out the k8s-monitoring helm chart from grafana). In that case, open up your Grafana instance, under "alerts"- create a contact point with your email create an alerting rule, with a promql query. set it to notify your contact point when breached. Like you said, awk on a cron with email would work- but it's such a basic requirement that you can do the same with any observability platform. You'll learn going forward that cpu is usually not a good metric to alert on, and start to think about metrics that do a better job of describing your customers experience...but for now implement the basic thing you described. More on reddit.com

No, and you are comparing apples with oranges. Grafana is the visualization plugin for Prometheus. And works for a lot of more data sources than just Prometheus, so it makes no sense for Prometheus to have all the Grafana features. But there are more programs that let you visualize in different ways the time series database that Prometheus have. More on reddit.com

If you're in Kubernetes, have you had a look at Prometheus Operator yet ? Gets all your AlertManager & Prometheus configs in kubernetes ressources which you manage the same as everything else in your clusters. Declarative, GitOps, good ol' reliable yaml. Personally I wouldn't use anything else . More on reddit.com