#support

Configuring Signoz to Consume Metrics From App's Endpoint

TLDR Sindhu wanted to configure Signoz to consume metrics from their app's endpoint. Ankit provided guidance on enabling a Prometheus receiver and suggested changing the host path for Docker.

6mo

Join the chat

Mar 23, 2023 (6 months ago)

Photo of md5-7c814df44ffd6834720c7d714f915ec6

Sindhu

04:20 PM

Hi, I have an app that's pushing metrics in prometheus format on localhost:3334/metrics. I do not want to run a prometheus instance to consume these. What configuration should I add to signoz to consume the metrics from my app's endpoint?

Also I do not see a "Metrics" menu item in the Signoz dashboard. Does this need some sort of config to enable?

Photo of md5-dbe7088320fe1d922707613e02f3420d

Ankit

04:36 PM

https://signoz.io/docs/userguide/send-metrics/#enable-a-prometheus-receiver

Sindhu

04:49 PM

Thanks, I added this:

        - job_name: "consoled"
          scrape_interval: 30s
          static_configs:
            - targets:
              - localhost:3334

into : /code/signoz/deploy/docker/clickhouse-setup/otel-collector-metrics-config.yaml
and restarted signoz, still wasn't able to see Metrics in the side pane of Signoz UI.

i have my application running at 3334 and its exposing /metrics

05:17

Sindhu

05:17 PM

I queried signoz clickhouse, it doesn't look like my consoled metrics are getting stored in signoz.

clickhouse :) select DISTINCT(JSONExtractString(time_series_v2.labels,'__name__')) as metrics from signoz_metrics.time_series_v2;

SELECT DISTINCT JSONExtractString(time_series_v2.labels, '__name__') AS metrics
FROM signoz_metrics.time_series_v2

Query id: 08686b3d-ae7f-4520-9b07-29fe5c69f00f

┌─metrics────────────────────────────────────┐
│ otelcol_exporter_db_write_latency_bucket   │
│ otelcol_exporter_db_write_latency_count    │
│ otelcol_exporter_db_write_latency_sum      │
│ otelcol_exporter_send_failed_metric_points │
│ otelcol_exporter_sent_metric_points        │
│ otelcol_receiver_accepted_metric_points    │
│ otelcol_receiver_refused_metric_points     │
│ otelcol_signoz_metric_points_bytes         │
│ otelcol_signoz_metric_points_count         │
└────────────────────────────────────────────┘
┌─metrics────────────────────────────────────────┐
│ otelcol_exporter_enqueue_failed_log_records    │
│ otelcol_exporter_enqueue_failed_metric_points  │
│ otelcol_exporter_enqueue_failed_spans          │
│ otelcol_exporter_queue_capacity                │
│ otelcol_exporter_queue_size                    │
│ otelcol_process_cpu_seconds                    │
│ otelcol_process_memory_rss                     │
│ otelcol_process_runtime_heap_alloc_bytes       │
│ otelcol_process_runtime_total_alloc_bytes      │
│ otelcol_process_runtime_total_sys_memory_bytes │
│ otelcol_process_uptime                         │
│ otelcol_processor_batch_batch_send_size_bucket │
│ otelcol_processor_batch_batch_send_size_count  │
│ otelcol_processor_batch_batch_send_size_sum    │
│ otelcol_processor_batch_timeout_trigger_send   │
└────────────────────────────────────────────────┘
┌─metrics───────────────┐
│ signoz_calls_total    │
│ signoz_latency_bucket │
│ signoz_latency_count  │
│ signoz_latency_sum    │
└───────────────────────┘
┌─metrics──────────────────────────────────┐
│ otelcol_exporter_send_failed_log_records │
│ otelcol_exporter_send_failed_requests    │
│ otelcol_exporter_send_failed_spans       │
│ otelcol_exporter_sent_log_records        │
│ otelcol_exporter_sent_spans              │
│ otelcol_receiver_accepted_log_records    │
│ otelcol_receiver_accepted_spans          │
│ otelcol_receiver_refused_log_records     │
│ otelcol_receiver_refused_spans           │
│ otelcol_scraper_errored_metric_points    │
│ otelcol_scraper_scraped_metric_points    │
│ otelcol_signoz_logs_bytes                │
│ otelcol_signoz_logs_count                │
│ otelcol_signoz_spans_bytes               │
│ otelcol_signoz_spans_count               │
│ scrape_duration_seconds                  │
│ scrape_samples_post_metric_relabeling    │
│ scrape_samples_scraped                   │
│ scrape_series_added                      │
│ signoz_external_call_latency_count       │
│ signoz_external_call_latency_sum         │
│ system_cpu_load_average_15m              │
│ system_cpu_load_average_1m               │
│ system_cpu_load_average_5m               │
│ system_cpu_time                          │
│ system_disk_io                           │
│ system_disk_io_time                      │
│ system_disk_merged                       │
│ system_disk_operation_time               │
│ system_disk_operations                   │
│ system_disk_pending_operations           │
│ system_disk_weighted_io_time             │
│ system_filesystem_inodes_usage           │
│ system_filesystem_usage                  │
│ system_memory_usage                      │
│ system_network_connections               │
│ system_network_dropped                   │
│ system_network_errors                    │
│ system_network_io                        │
│ system_network_packets                   │
│ up                                       │
└──────────────────────────────────────────┘

69 rows in set. Elapsed: 0.010 sec. Processed 4.00 thousand rows, 1.26 MB (386.68 thousand rows/s., 121.95 MB/s.)

Ankit

05:36 PM

running using docker-compose or helm? docker container can't use localhost:3334 to access host path

Sindhu

05:57 PM

Thank you! that fixed it 🙂

Ankit

06:38 PM

what did you use as host? there are more than 1 ways to do that IMO

Mar 24, 2023 (6 months ago)

Sindhu

02:50 AM

I realised after fumbling around for a bit and checking logs on otel-collector-metrics-1 and your reply was just on time, so thank you! Ankit

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 825 threads (61% resolved)

Join Our Community Manage subscription

Similar Threads

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`.

4mo

Monitoring JVM Metrics with Signoz in Kubernetes Cluster

Ragul had trouble monitoring JVM metrics in their Kubernetes cluster with Signoz using Helm. Srikanth advised modifying the scrape config in values.yaml and checking the `host:port/path`.

3mo

Integrating TimescaleDB Prometheus Data with SigNoz

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.

3mo

Difficulty Configuring SigNoz on AzureK8s with Prometheus

saptarshi seeks guidance on configuring SigNoz with Prometheus in AzureK8s, and Srikanth provides a link to documentation. saptarshi still faces issues and suggests adding data sources in the UI.

6mo

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.

5mo