The KloudMate agent has been rebuilt to reduce the manual setup previously required to start collecting database, log, and APM telemetry, replacing hand-written collector configuration with wizards and per-service toggles.
Automatic from install, no config needed: service/runtime/database discovery, host metrics and logs, and eBPF monitoring (RED metrics, network service map, Database Activity Monitoring, trace-context propagation), all with no code changes.
Opt-in, now wizard- or toggle-driven instead of hand-configured:
- APM:toggle Instrument per service. Java/Node.js/Python/.NET use standard OTel attach mechanisms and need a restart, which the agent asks for explicit consent on and applies one service at a time; PHP uses a graceful reload instead of a restart; Go isn't injected at all; it's covered by eBPF across HTTP, gRPC, Kafka, Redis, SQL, and MongoDB, with validated trace-context handoff to instrumented neighbors. On Kubernetes, the same toggle works through the OpenTelemetry Operator, or you can annotate a deployment manually. If a restart fails or crash-loops, the agent rolls back automatically; one bad service can't affect the others.
- Database monitoring:a wizard walks engine selection, coverage choice (metrics, query performance, locks, logs), and credentials, with exact grants shown inline. Credentials are stored as an environment reference by default, so rotating a password is just an env var or Secret update, no agent config change needed.
- Log monitoring:point at a folder and file pattern, pick a parse format (plain text, JSON, or regex, with presets for syslog/nginx/Apache), and preview real sample lines before saving.
- Web server monitoring:nginx and Apache auto-discovered via their status modules; the agent only probes, never edits your server config.
For automated rollouts, an advanced autonomous mode instruments every eligible service and auto-wires reachable web servers with no per-service toggles.
Check out the KloudMate Agent documentation for full details.