This message was deleted.

That won't be possible even going forward

First of all, in Kibana I can decide which columns are displayed. And it's displayed in table and not json or any other type

@Łukasz Herman you should be able to extract out fields for better visibility. You need to set parsing rules at otel-collector and add them to

selected

fields from

interesting

fields. If you can share your log line and what you want to extract from it, we can help with regex rules at otel-collector. cc @nitya-signoz

Sure @Ankit Nayan

I can’t think of how you would surface SigNoz data in Kibana, but there is a Clickhouse data source for Grafana which could probably be used to visualize SigNoz data. I’m actually planning on giving that a shot soon myself.

We are also thinking of using Grafana on top of SigNoz data since we want all alerts in one place (Grafana)

btw I got some time to try this out and querying/aggregating SigNoz trace data from Grafana via the ClickHouse data source works brilliantly 👍 here’s a quick example query that I put behind a timeseries panel:

SELECT
  $__timeInterval(timestamp) as time
  ,sum(toInt32(tagMap['client.validSamples'])) as Written
  ,sum(toInt32(tagMap['client.initialSamples'])) as Attempted
FROM signoz_traces.signoz_index_v2
WHERE $__timeFilter(timestamp)
  AND (serviceName = '$app')
  AND has(tagMap, 'client.validSamples')
GROUP BY time
ORDER BY time ASC

nice, i didn’t try yet and was wondering if it worked at all haha

I was a little worried about time-binning but the Grafana time macros

$__timeInterval

and

$__timeFilter

work as advertised 🎉 also aggregating fields from the

tagMap

column works great. I was expecting performance to be a bit rocky, but ClickHouse continues to impress.

yeah its laser fast

now to figure out how to populate a Grafana Heatmap panel with SigNoz trace duration data 😅

lol, see you in 2 weeks

😭 really missing Elasticsearch’s date_histogram aggregation right now