Glossary
Definitions of the terms used across the agent documentation.
Collector. The OpenTelemetry (OTel) Collector built into the agent. It runs the receivers, processors, and exporters that collect and send telemetry.
Coverage. One set of data the agent can collect for a database engine, such as standard metrics, query performance, locks, or query logs. You pick the coverages you want, and the agent sets up the receiver to collect them. See Engines and coverages.
Database Activity Monitoring (DAM). The eBPF view of the database queries your applications run, captured automatically with no credentials. See eBPF observability.
eBPF (extended Berkeley Packet Filter). A Linux kernel technology the agent uses to observe applications, network, and databases without code changes. See eBPF observability.
ETW (Event Tracing for Windows). The Windows equivalent of eBPF monitoring. The agent uses ETW to produce request spans and RED metrics for IIS traffic. See Windows platform notes.
Fleet manager. On Kubernetes, the pod that applies the generated configuration to the cluster and reports each collector’s status back. See Kubernetes platform notes.
Managed mode. The mode where KloudMate builds the collector configuration from the features you turn on, and the YAML editor is a read-only preview. Contrast manual mode. See the configuration model.
Manual mode. The mode where you edit the raw collector YAML yourself and the feature toggles are turned off. For advanced, hand-tuned setups. See the configuration model.
Pipeline. A path through the collector for one signal (metrics, traces, or logs), made of receivers, processors, and exporters.
Profile. A template that provides one coverage for one database engine. When you select a profile, the agent turns it into the right receiver configuration. See Database monitoring overview.
Profiler (CLR profiler). The Common Language Runtime profiler used to instrument .NET applications on Windows without code changes. See Windows and .NET application APM.
Receiver. A collector component that collects telemetry from a source, such as hostmetrics, filelog, or a database receiver like postgresql.
RED metrics. Rate, Errors, and Duration: the key metrics eBPF monitoring produces for each service, with no instrumentation.
Server address. The single routable address the agent stamps on database telemetry so metrics and traces for the same database join. See Telemetry identity.
Service identity. A stable ID the agent gives a discovered service, so the instrumentation you choose keeps applying after the service restarts. See Discovery.