Agent Configuration for Monitor

The Sysdig configuration library lists all the major configurations required to enable Sysdig Monitor features.
Configurationdragent.yamlHelmDescriptionDefault and Example
StatsDstatsd

Controls StatsD metric collection.

enabled
statsd:
	blacklisted_ports

See StatsD for more information.

statsd:
	tcp_port

See StatsD for more information.

statsd:
  udp_port

See StatsD for more information.

statsd:
  ip_address: 0.0.0.0

The value indicates that the statsd server will accept incoming traffic from any IP, local or remote. Use this configuration to add the ability to send statsd messages to a host running the agent from a remote host, and for the agent to process the message as if they have originated on the host on which the agent is running.

By default, the agent includes a statsd server that listens on the loopback interface (127.0.0.1) for incoming statsd messages, which does not allow accepting messages originating from remote hosts. Use the ip_address: 0.0.0.0 configuration to change this default behavior.

Events
events:
  docker

Controls Event Collection metric collection.

events:
  kubernetes
Log
log:
  event_priority

Allows you to configure log levels metric collection.

log:
  console_priority

log:
  file_priority
Prometheus
prometheus:
  enabled

Controls Prometheus Native Service Discovery.

JMX
jmx:
  enabled

Controls JMX metrics collection.

App Checks
app_checks:
  enabled

Controls monitoring capabilities using App Checks.

KSM
k8s_extra_resources:
  - include
  ...

Enable and disable Kube State Metrics collection.

enabled
Go Eventsgo_k8s_user_events

Streamline Sysdig agent processing times and reduce CPU load.

true
Agent Console
command_line:
  enabled

Enable Agent Console to interact with the Sysdig agent to troubleshoot and investigate agent configuration problems quickly.

enabled

Learn More