On 09/12/2020 08:34, Allenzh li wrote:
The key problem is that ordinary users need to learn PromQL, even if
grafana is provided, the cost of promql learning cannot be reduced.
It is not easy for everyone to learn PromQL.
If users need to create/update dashboards or alerts then yes they need
to understand PromQL. They also need to understand the metrics and their
meanings.
I would say this is the case for any database type system, for example
needing to know SQL for MariaDB or KQL for Kibana & Elasticsearch.
For both of those examples tools to allow very simple queries to be
constructed graphically do exist, but you very quickly outgrow them -
all these systems are only fully useful if you are able to use the power
of their different query languages.
The sort of query which can be easily represented on a web page is so
basic that it generally isn't that useful, and trying to represent more
complex queries would quickly become more confusing than seeing the
underlying PromQL. For example how would you visually represent queries
which use sums of rates or join metrics together?
I would suggest as far as query languages go, PromQL isn't that complex.
The basics should be relatively straightforward to learn, with more
complex ideas being things you can add over time to your understanding.
One thing that can be useful for less experienced users are example
queries or cookbooks - often you might find a set of alerts/queries for
dashboards have similarities.
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/c0239984-8aa1-6fcc-345c-858b2a6a2d1e%40Jahingo.com.
