#support

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.

Powered by Struct AI

1

29
6mo
Solved
Join the chat
Jun 06, 2023 (6 months ago)
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
08:08 PM
Hi all, I need some help

I 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
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
01:20 AM
> 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 are these related to the Timescale Prometheus metric data?
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
06:57 AM
On Timescale TB I have Enabled Prometheus service integration
On 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?
07:02
Milan
07:02 AM
I want to see Timescale Prometheus data in SigNoz. Can someone help please?
Prashant
Photo of md5-1899629483c7ab1dccfbee6cc2f637b9
Prashant
08:22 AM
Milan can you verify that the my-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.
08:23
Prashant
08:23 AM
Also, did you stop->remove->re-create otel-collector-metrics container?
08:24
Prashant
08:24 AM
since, we use volume mounting for the configuration in Docker.
We often have to cleanup properly for any changes to show up.
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
08:38 PM
1. I am able to see my-url:9273 from my signoz instance
2. 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
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
01:42 AM
>however, in dashboard when I try to save panel with e.g system_filesystem_usage_total I get response: “No Data”

Is the endpoint my-url:9273 expose this metric?
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
07:51 AM
when I use GET my-url:9273/metrics, I am able to see huge response
like
cpu_usage_guest, diskio_merged_reads,…
and when I try to use them in dashboard I get response: No Data
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
08:12 AM
Are you sure the system_filesystem_usage_total exists in response from my-url:9273/metrics
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
08:13 AM
you are right, that does not exist. but I can’t display any of metrics that do exists
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
08:15 AM
Did you mean you can’t display or you can display?
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
08:16 AM
can’t
08:16
Milan
08:16 AM
sorry
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
08:16 AM
Can you open the network tab and share the response when you try to run query?
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
09:01 AM
Image 1 for
09:02
Milan
09:02 AM
another metrics
09:02
Milan
09:02 AM
Image 1 for
09:02
Milan
09:02 AM
I get 200 OK
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
09:03 AM
What is the metric type and temporality for them?
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
09:04 AM
# HELP disk_used_percent Telegraf collected metric
# TYPE disk_used_percent gauge
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
09:05 AM
Can you confirm if it was really scraped by otel-collector-metrics? Do logs show any errors? Make sure it is reachable.
Jun 09, 2023 (6 months ago)
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
01:05 PM
That is the problem, I did prepare it, as stated above, but not sure how to see on Signoz side :-(\
Srikanth
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
01:14 PM
> Do logs show any errors?
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
02:13 PM
Here is output

when 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
Photo of md5-ce04a9988e2fd758a659dc55be6f2543
Srikanth
02:14 PM
It says config is invalid.
>
field evaluation_interval not found in type config.ScrapeConfig

>
Jun 13, 2023 (6 months ago)
Milan
Photo of md5-2f1595079fdf2f9da7cf336b4e3395d3
Milan
06:55 AM
I managed to set all up. Issue was that env variable evaluation_interval: 10s was not needed.
06:55
Milan
06:55 AM
Thank for your support!

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community