Loki is written by the same people as Grafana and integrates tightly. You can use the "explore" section to view logs, you can create your own panels, and you can use LogQL <https://grafana.com/docs/loki/latest/logql/> queries. But this is off-topic for a prometheus list.
On Saturday, 18 September 2021 at 02:39:14 UTC+1 kazakaze wrote: > thank you for your reply. > > My other question is, do I still want to show with grafana? *Can the data > of the log solution be displayed in grafana*? I haven't seen it. What > kind of graphics might it be? > 在2021年9月17日星期五 UTC+8 下午7:49:08<Brian Candler> 写道： > >> Prometheus only records metrics, which are numeric values - counters and >> gauges. >> >> You can apply labels to timeseries, but these are not suitable for >> storing arbitrary strings like URL paths, because every new URL path you >> see will create a new timeseries. It can lead to cardinality explosion, >> especially if your system is open where attackers can generate arbitrary >> URL paths. >> >> I suggest you look at a logging solution, like Loki or Elasticsearch. >> Loki allows you to apply PromQL-style queries to your logs; Elasticsearch >> has its own query language and API. >> >> On Friday, 17 September 2021 at 11:28:13 UTC+1 kazakaze wrote: >> >>> I have a proxy server, simply, I want to record which URLs are accessed >>> through the proxy server. And hope to use prometheus as monitoring. >>> However, when I was brainstorming, I wonder if >>> *prometheus+request-url-path* is a good idea. >> >> -- 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/02457d47-78bf-459b-9ac7-745215b1cda7n%40googlegroups.com.
