postgrespro — the central component of the collector, which contains the main implementation (built-in plugins) for collecting data from a database instance.

file_log — an auxiliary receiver responsible for collecting information from database logs.

host_metrics — an auxiliary receiver that collects information from the operating system; may require root access.

journald — an auxiliary receiver that collects logs from the systemd journal.

otlp — a dedicated receiver for collecting data in the OTLP (OpenTelemetry Protocol) format. It is especially useful for working with Postgres ProGate.

sqlquery — an auxiliary receiver that collects metrics and/or logs from custom SQL queries.

attributes processes specific attributes of log records.

batch batches data and regulates the data transmission mechanism.

filter allows filtering metrics and logs based on specified conditions using OTTL (OpenTelemetry Transformation Language).

memory_limiter limits the pgpro-otel-collector memory consumption.

metrics_transform allows renaming metrics and managing labels, including scaling and aggregation.

resource adds extra log record attributes.

transform modifies the data using OTTL.

kafka sends metrics and logs to Apache Kafka — an open-source distributed event streaming platform.

otlp_http sends information over the OTLP protocol (the standard OpenTelemetry protocol used by many monitoring system vendors) with the help of the HTTP protocol.

prometheus exports metrics over the built-in HTTP server and publishes them on the /metrics page in the format of the Prometheus monitoring system. prometheus is used by default because it does not require additional configuration.

prometheus_remote_write sends metrics via the remote write protocol to Prometheus-compatible systems, including Cortex, Mimir, Thanos, VictoriaMetrics.

zabbix sends metrics to Zabbix — an open-source monitoring solution.