This query is offset by 1,000 milliseconds (or 1 second), which is required by Splunk in Grafana to create a valid query.
Much like the trace to logs feature for Loki, if trace to logs for Splunk is enabled in your data source (see Get started below), we will automatically generate a query link that, when clicked from the trace view, opens a Splunk tab in Grafana. This was a heavily requested feature from our customers whose data is deeply embedded with Splunk and now those users can add to their all-in-one approach to working in Grafana.įor more information about the Splunk Enterprise plugin, which is available for customers with a Grafana Cloud account or with a Grafana Enterprise license, check out the Splunk solutions page or contact our team. Grafana handles the task of sifting through your immense log data simply and powerfully by allowing you to filter logs by trace ID and/or by span ID, in addition to filtering by any other tags and metadata that may be contained in your logs. So, in combination, traces to logs is really powerful. But what if you were also empowered to connect the dots even further to understand why it happened as well? This feature helps you do just that, telling you why and when an incident happened. Traces tell you that something happened, or more specifically, what part of your request path caused the error.
But with the introduction of this new feature, the deep insights offered by Splunk logs are now one click away.
Previously, the Grafana trace to logs enablement included only Loki logs. It’s a big leap that now allows you to draw a straight line between your traces - whether they are coming from Tempo, Zipkin, or Jaeger - to even more third-party logging data, all from the comfort of your traces view. The recent release of Grafana 8.5 marks the start of enabling the jump from traces directly to Splunk logs.
0 kommentar(er)
