Reference · built on requestConnectorIdentity, IT & observability

Prometheus

Instant and range queries, active alerts, recording rules, and scrape targets from Prometheus servers via the HTTP API under /api/v1.

Request accessPricing ↗

About

Prometheus is an open source systems monitoring and alerting toolkit hosted by the Cloud Native Computing Foundation. It collects and stores metrics as time series data identified by metric names and key-value label pairs. The Prometheus HTTP API provides PromQL expression evaluation for instant and range queries, scrape target health discovery, alert rule inspection, and time-series metadata lookup.

Through Fibric, an operator runs scheduled PromQL queries to monitor metric drift, proposing alert silences or scrape target updates for team approval.

This is a reference listing. It documents what Fibric would read from Prometheus and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Instant PromQL query evaluation at a single point in time via GET /api/v1/query
  • Range PromQL query evaluation across time intervals with step resolution from GET /api/v1/query_range
  • Active firing and pending alert states through GET /api/v1/alerts
  • Configured recording and alerting rule evaluations from GET /api/v1/rules
  • Scrape targets, job names, endpoint health, and scrape latency via GET /api/v1/targets
  • Time-series metadata, metric names, and label values from GET /api/v1/labels and /api/v1/series

Proposed actions

  • Target capability: propose creating an alert silence in Alertmanager for firing rules
  • Target capability: propose triggering a server configuration reload via POST /-/reload
  • Target capability: propose updating scrape target labels or recording rule definitions

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Monitor container error budget burn rates

    Execute PromQL range queries on HTTP error rates and latency percentiles, proposing notifications when burning through quarterly error budgets.

    With Error Budget, Uptime Response

  • Alert on failing scrape targets

    Query target discovery endpoints to find exporter endpoints marked down, proposing remediation tickets before monitoring coverage lapses.

    With Integration Health, On-call Handoff

  • Identify idle infrastructure resources

    Evaluate CPU and memory utilization metrics over 30-day windows to spot over-provisioned nodes and propose resource scaling plans.

    With Idle Resources, Cost Anomaly

Requirements

  • An accessible Prometheus server endpoint exposing the /api/v1 HTTP interface
  • PromQL query access enabled on the endpoint without restrictive query size proxies
  • The --web.enable-lifecycle flag enabled on Prometheus to support configuration reload requests
Authentication
HTTP Basic authentication, Bearer tokens, or mutual TLS configured on the Prometheus ingress or reverse proxy.

Limits

  • Broad time-range queries with small step intervals can trigger memory consumption limits
  • Prometheus query timeouts terminate expensive queries exceeding configured server limits
  • Prometheus does not provide native role-based access control without an external reverse proxy

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Prometheus ↗

Questions and answers

What query language is supported?
The connector supports standard PromQL expressions executed through Prometheus HTTP query endpoints. Queries can compute rate calculations, histogram percentiles, label aggregations, and mathematical transformations across time series.
Can Prometheus receive remote write data from Fibric?
This connector focuses on querying telemetry data and managing alerts via the HTTP API. Ingesting custom metrics into Prometheus can be configured through Prometheus Pushgateway or standard Prometheus exporters.
How does Fibric handle query rate limits?
Prometheus queries are executed with bounded time ranges and reasonable step resolutions to prevent overloading the Prometheus time-series database. Fibric respects query timeouts configured on the server.
Ask about Prometheus

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Prometheus through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy