Closed zhangshenghang closed 3 months ago
The same problem will also occur in Doris monitoring
Because the indicator keys under doris_fe_query_latency_ms include:doris_fe_query_latency_ms 、doris_fe_query_latency_ms_count、doris_fe_query_latency_ms_sum
Doris monitoring information:
# HELP doris_fe_query_latency_ms
# TYPE doris_fe_query_latency_ms summary
doris_fe_query_latency_ms{quantile="0.75"} 0.0
doris_fe_query_latency_ms{quantile="0.95"} 0.0
doris_fe_query_latency_ms{quantile="0.98"} 0.0
doris_fe_query_latency_ms{quantile="0.99"} 0.0
doris_fe_query_latency_ms{quantile="0.999"} 0.0
doris_fe_query_latency_ms_sum {} 0.0
doris_fe_query_latency_ms_count {} 11
doris_fe_query_latency_ms{quantile="0.75",user="root"} 0.0
doris_fe_query_latency_ms{quantile="0.95",user="root"} 0.0
doris_fe_query_latency_ms{quantile="0.98",user="root"} 0.0
doris_fe_query_latency_ms{quantile="0.99",user="root"} 0.0
doris_fe_query_latency_ms{quantile="0.999",user="root"} 0.0
doris_fe_query_latency_ms_sum {user="root"} 0.0
doris_fe_query_latency_ms_count {user="root"} 11
# HELP doris_fe_txn_exec_latency_ms
# TYPE doris_fe_txn_exec_latency_ms summary
doris_fe_txn_exec_latency_ms{quantile="0.75"} 0.0
doris_fe_txn_exec_latency_ms{quantile="0.95"} 0.0
doris_fe_txn_exec_latency_ms{quantile="0.98"} 0.0
doris_fe_txn_exec_latency_ms{quantile="0.99"} 0.0
doris_fe_txn_exec_latency_ms{quantile="0.999"} 0.0
doris_fe_txn_exec_latency_ms_sum {} 0.0
doris_fe_txn_exec_latency_ms_count {} 0
# HELP doris_fe_txn_publish_latency_ms
# TYPE doris_fe_txn_publish_latency_ms summary
doris_fe_txn_publish_latency_ms{quantile="0.75"} 0.0
doris_fe_txn_publish_latency_ms{quantile="0.95"} 0.0
doris_fe_txn_publish_latency_ms{quantile="0.98"} 0.0
doris_fe_txn_publish_latency_ms{quantile="0.99"} 0.0
doris_fe_txn_publish_latency_ms{quantile="0.999"} 0.0
doris_fe_txn_publish_latency_ms_sum {} 0.0
doris_fe_txn_publish_latency_ms_count {} 0
hi, it seem now does not support add name column. Welcome to update this implement your idea. We currently have three ways of parsing prometheus, the first is automatically parsed via promethes task, the second is via promql, and the third is the way you describe. Personally, I feel that the third way is not very conveniently designed, if you have a better way of defining it in your side of the implementation, you are welcome to optimize it.
Description
Translation:
When I try to retrieve data via the HTTP protocol and parse it using Prometheus rules, I can't display the names of the metrics in the system.
Configuration:
Data obtained from the interface:
Actual display result:
Expected display result:
When the name is not displayed, it's impossible to understand the specific meaning of the monitoring metrics. Therefore, I hope to add a name column.
By examining the
HttpCollectImpl.parseResponseByPrometheusExporter
method, it seems that the expected result display may not be supported currently.Is there a need for the community to support my idea? If necessary, I can implement it.
Or is there any support method that I don’t know about yet, I hope you can give me some advice.
Task List
No response