#support

Using Prometheus Storage with Query-Service

TLDR Sergei inquires about using existing Prometheus storage with query-service, but Srikanth says remote_read is not supported at this time.

5mo

Join the chat

Jun 20, 2023 (5 months ago)

Photo of md5-2b5e5f101a8f637bb89fe73070782487

Sergei

11:57 AM

Greetings! Is there any way to use existing prometheus storage (or VictoriaMetrics) to gather mertircs via query-service?

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

11:59 AM

No, what’s the usecase? You can configure the collector to scrape targets though.

Sergei

12:04 PM

Saw this one - https://signoz.io/docs/faqs/product/#is-prometheus-included-in-signoz and thought that the service supports remote_read from existing prom stack. Is it possible? This will be useful to not duplicate data (metrics) in both CH and Prometheus.

Srikanth

12:08 PM

I don’t think we support remote_read now.

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

Similar Threads

Issues with Azure Prometheus Metrics Scraping

Alex is encountering problems scraping metrics from Azure Prometheus and shared their config details. Srikanth suggested a possible issue with the target's accessibility, although Alex affirmed its accessibility despite the lack of a /metrics endpoint in Azure. The issue remains unresolved.

Connecting TimescaleDB to Signoz

Milan needed help connecting TimescaleDB to Signoz for monitoring parameters. Ankit advised using Prometheus integration with modifications to the prometheus.yml file.

7mo

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.

6mo