Hi team, I am currently doing a proof of concept o...
# support
a
Hi team, I am currently doing a proof of concept on Signoz but running into an issue. The architecture is roughly: A number of microservice based products have their own OTEL collectors running in a container app. This is configured to push to the Signoz cloud. It does this successfully I can see logs and traces and have default dashboards. So far so good. The container app (running the OTEL collector )none Signoz dstro) has its config.yaml configured to add resource/deployment_context attributes of (product.name, customer.id, deployment.environment etc.). So that I can isolate metrics over multiple deployments. I can see these have values in the container app logs. But the issue is I can't seem to use them in Signoz cloud clickhouse queries. I can't seem to find a good reference/example of these queries? Here is an example query that returns "API responded with 500 - Something went wrong status: error in clickhouse queries":
SELECT DISTINCT resource_string['product.name'] as product_name
FROM signoz_traces.distributed_signoz_index_v3
WHERE timestamp >= now() - INTERVAL 1 HOUR
AND ts_bucket_start >= toUInt64(toUnixTimestamp(now() - toIntervalHour(1))) - 3600 <https://signoz.io/docs/userguide/logs/>
I have noticed this in the logs and wondered if this was my issue (I am not using the Signoz distro)? thanks in advance! If you have N number of OpenTelemetry collectors running in different places then they should process and send data to SigNoz OTEL collector using OTLP for it to be able to store in ClickHouse.
I have swapped to the Signoz distro and confirmed that logs & metrics are exported to Signoz. but this simple clickhouse query: SHOW TABLES; returns "no data" and simple queries such as DESCRIBE signoz_logs; returns "API responded with 500 - Something went wrong status: error in clickhouse queries"