Integrating TimescaleDB Prometheus Data with SigNoz
TLDR Milan was unable to view TimescaleDB Prometheus data in SigNoz. With suggestions from Srikanth and Prashant, they identified and fixed a configuration error by removing the unnecessary evaluation_interval setting.
1
Jun 06, 2023 (6 months ago)
Milan
08:08 PMI have enabled Prometheus integration form TimeseriesDB, as stated here:
https://docs.timescale.com/mst/latest/integrations/prometheus-mst/
then I have edited file: deploy/docker/clickhouse-setup/otel-collector-metrics-config.yaml
and added this section:
# Timescale Dev
- job_name: timescale-dev-collector
scrape_interval: 10s
evaluation_interval: 10s
scheme: https
static_configs:
- targets: ['my-url:9273']
tls_config:
insecure_skip_verify: true
basic_auth:
username: milan
password: password
But I don’t see anything in SigNoz. I have tried to add new dashboard with system_filesystem_usage_total, system_cpu_time_total, as PromQL, but nothing is displayed.
How I can check Prometheus data from my TimeseriesDB on SigNoz instance?
Thanks
1
Jun 07, 2023 (6 months ago)
Srikanth
01:20 AMHow are these related to the Timescale Prometheus metric data?
Milan
06:57 AMOn SigNoz I have set up otel-collector-metrics-config.yaml, as stated above.
Now I am not sure how check are data flowing into SigNoz?
Milan
07:02 AMPrashant
08:22 AMmy-url:9273
is accessible from VM/Cluster where signoz is deployed?After that, you can use suggestions from Query Builder from dashboard page to verify if any timescale related metrics have been collected.
Prashant
08:23 AMPrashant
08:24 AMWe often have to cleanup properly for any changes to show up.
Milan
08:38 PM2. I did stop, removed containers clickhouse-setup-otel-collector-1 and clickhouse-setup-otel-collector-metrics-1 and re-run install script
3. however, in dashboard when I try to save panel with e.g system_filesystem_usage_total I get response: “No Data”
I am not sure anything is coming to my SigNoz instace from TimeseriesDB?
Jun 08, 2023 (6 months ago)
Srikanth
01:42 AMIs the endpoint
my-url:9273
expose this metric?Milan
07:51 AMlike
cpu_usage_guest, diskio_merged_reads,…
and when I try to use them in dashboard I get response: No Data
Srikanth
08:12 AMsystem_filesystem_usage_total
exists in response from my-url:9273/metricsMilan
08:13 AMSrikanth
08:15 AMMilan
08:16 AMMilan
08:16 AMSrikanth
08:16 AMMilan
09:01 AMMilan
09:02 AMMilan
09:02 AMMilan
09:02 AMSrikanth
09:03 AMMilan
09:04 AM# TYPE disk_used_percent gauge
Srikanth
09:05 AMJun 09, 2023 (6 months ago)
Milan
01:05 PMSrikanth
01:14 PMMilan
02:13 PMwhen I do this:
docker logs clickhouse-setup-otel-collector-metrics-1 | grep error
* error decoding 'receivers': error reading receivers configuration for "prometheus": prometheus receiver failed to unmarshal yaml to prometheus config: yaml: unmarshal errors:
line 17: field evaluation_interval not found in type config.ScrapeConfig
line 29: field evaluation_interval not found in type config.ScrapeConfig
2023/06/07 20:09:50 application run finished with error: failed to get config: cannot unmarshal the configuration: 1 error(s) decoding:
* error decoding 'receivers': error reading receivers configuration for "prometheus": prometheus receiver failed to unmarshal yaml to prometheus config: yaml: unmarshal errors:
line 17: field evaluation_interval not found in type config.ScrapeConfig
line 29: field evaluation_interval not found in type config.ScrapeConfig
Error: failed to get config: cannot unmarshal the configuration: 1 error(s) decoding:
* error decoding 'receivers': error reading receivers configuration for "prometheus": prometheus receiver failed to unmarshal yaml to prometheus config: yaml: unmarshal errors:
line 17: field evaluation_interval not found in type config.ScrapeConfig
line 29: field evaluation_interval not found in type config.ScrapeConfig
2023/06/07 20:09:50 application run finished with error: failed to get config: cannot unmarshal the configuration: 1 error(s) decoding:
and this
docker logs clickhouse-setup-otel-collector-metrics-1 | grep error
7->10.33.105.29:63788: read: connection reset by peer {"grpc_log": true}
2023-06-07T20:14:54.465Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 173.19.0.7:4317->10.33.105.29:63822: read: connection reset by peer {"grpc_log": true}
2023-06-07T20:14:55.280Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 173.19.0.7:4317->10.33.144.245:57520: read: connection reset by peer {"grpc_log": true}
2023-06-07T20:14:59.327Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 173.19.0.7:4317->10.33.144.245:57546: read: connection reset by peer {"grpc_log": true}
2023-06-07T20:15:06.169Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 173.19.0.7:4317->10.33.105.29:29906: read: connection reset by peer {"grpc_log": true}
2023-06-07T20:15:06.821Z warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp 173.19.0.7:4317->10.33.144.245:57492: read: connection reset by peer {"grpc_log": true}
Srikanth
02:14 PM>
field evaluation_interval not found in type config.ScrapeConfig
>
Jun 13, 2023 (6 months ago)
Milan
06:55 AMMilan
06:55 AMSigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Issues with SigNoz Setup and Data Persistence in AKS
Vaibhavi experienced issues setting up SigNoz in AKS, and faced data persistence issues after installation. Srikanth provided guidance on ClickHouse version compatibility and resource requirements, helping Vaibhavi troubleshoot and resolve the issue.
Unable to Monitor jdbc_connections_active Metrics in SigNoz
Ragulraj is unable to monitor jdbc_connections_active metrics with SigNoz despite modifying configurations and adding dependencies. Srikanth provided troubleshooting steps and info on alternatives, but the issue remains unresolved.
Monitoring JDBC and HIKARI Metrics in SigNoz
Ragulraj is unable to monitor JDBC and HIKARI metrics in their spring boot application using SigNoz. Srikanth suggests configuring `scrape_configs` in `otel-collector-metrics`.
Dashboard Load Issues and Possible Solutions
Al experiences dashboard loading issues since updating to `0.18.1`. Srikanth believes the issue is not version related and suggests examining queries, memory resources, and server distribution for improvements.
Configuring SigNoz with Istio Traces and Service Monitors
Zakaria asked about integrating SigNoz with istio traces and Prometheus service monitors. Srikanth suggested using OpenTelemetry operator and provided guidance for troubleshooting and solving configuration issues in the process.