如何直接访问Prometheus数据库？REST API功能存在局限性

Great question! Let’s start by clarifying a core design choice of Prometheus: it’s built around a pull-based model (scraping metrics from targets) rather than accepting direct writes. That’s why the REST API doesn’t support inserting data natively. But there are ways to work with its storage more directly, and alternative approaches to get data into Prometheus. Here’s what you need to know:

Direct Database Access Options #

• Avoid direct manipulation of TSDB files: Prometheus uses its own built-in Time Series Database (TSDB), with data stored in block files under the data/ directory. While technically you could interact with these files, there’s no official tooling for direct reads/writes, the format is complex and version-dependent, and messing with them risks corrupting your entire dataset. This is strongly discouraged for production environments.
• Use promtool for block management: The official promtool utility has a command to generate TSDB blocks from OpenMetrics-formatted data:

  promtool tsdb create-blocks-from openmetrics --start=1600000000 --end=1600003600 input.txt output-dir
  

  You can then move the generated block directory into Prometheus’s data/ directory and restart the service. This lets you retroactively add historical data, but it’s a batch process, not real-time insertion.

Inserting Data into Prometheus (Workarounds) #

Since direct writes aren’t supported, these are the official/recommended ways to get data into Prometheus:

• Pushgateway: For short-lived jobs or services that can’t be scraped (like batch tasks), you can push metrics to the Pushgateway. Prometheus then scrapes the Pushgateway just like any other target. Note that metrics stored here won’t expire automatically—you’ll need to manage deletion manually.
• Remote Write to a compatible storage backend: If you need persistent, real-time write capabilities, you can use Prometheus’s Remote Write feature to send metrics to an external storage system (like Thanos, Cortex, or VictoriaMetrics) that supports write APIs. You can then configure Prometheus to read from this backend via Remote Read if needed.

Key Takeaway #

Prometheus doesn’t offer a direct, supported way to write data into its native TSDB via an API or tooling, due to its pull-oriented design. For most use cases, Pushgateway or Remote Write are the safer, supported paths. Directly touching the TSDB files should only be done as a last resort, and always with backups.

内容的提问来源于stack exchange，提问作者roie