# Configure Sysdig Monitor Using Agent Modes

Agent modes provide the ability to control metric collection to fit your scale and specific requirement. You can choose one of the following modes to do so:

• Monitor

• Monitor Light

• Troubleshooting

Using a stripped-down mode limits collection of unneeded metrics, which in turn prevents the consumption of excess resources and helps reduce expenses.

## Monitor

The Monitor mode offers an extensive collection of metrics. We recommend this mode to monitor enterprise environments.

monitor is the default mode. To switch back to the Monitor mode from a different mode, do one of the following:

• Add the following to the dragent.yaml file and restart the agent:

feature:
mode: monitor
• Remove the parameter related to the existing mode from the dragent.yaml file and restart the agent. For example, to switch from troubleshooting mode to monitor, delete the following lines:

feature:
mode:troubleshooting

## Monitor Light

Monitor Light caters to the users that run agents in a resource-restrictive environment, or to those who are interested only in a limited set of metrics.

### Metrics Available in Monitor Light

The following metrics will be reported in Monitor Light.

Metrics

Description

cpu.cores.used

See System.

cpu.cores.used.percent

cpu.idle.percent

cpu.iowait.percent

cpu.nice.percent

cpu.stolen.percent

cpu.system.percent

cpu.used.percent

cpu.user.percent

load.average.percpu.1m

load.average.percpu.5m

load.average.percpu.15m

memory.bytes.available

memory.bytes.total

memory.bytes.used

memory.bytes.used

memory.bytes.virtual

memory.pageFault.major

memory.pageFault.minor

memory.swap.bytes.available

memory.swap.bytes.total

memory.swap.bytes.used

memory.swap.used.percent

memory.used.percent

file.bytes.in

file.bytes.out

file.bytes.total

file.iops.in

file.iops.out

file.iops.total

file.open.count

file.time.in

file.time.out

file.time.total

fs.bytes.free

fs.bytes.total

fs.bytes.used

fs.free.percent

fs.inodes.total.count

fs.inodes.used.count

fs.inodes.used.percent

fs.largest.used.percent

fs.root.used.percent

fs.used.percent

net.bytes.in

net.bytes.out

net.bytes.total

proc.count

thread.count

container.count

system.uptime

uptime

### Enable Monitor Light

To switch to the Monitor Light mode, edit the dragent.yaml file:

1. Open the dragent.yaml file.

2. Add the following configuration parameter:

feature:
mode: monitor_light
3. Restart the agent.

## Troubleshooting

Troubleshooting mode offers sophisticated metrics with detailed diagnostic capabilities. Some of these metrics are heuristic in nature.

### Additional Metrics Values Available in Troubleshooting

In addition to the extensive set of metrics available in the Monitor mode, the following metric segments will also be reported in the Troubleshooting mode.

Metrics

Additional Metrics Values Available When Segmented by

file.error.total.count

file.name and file.mount labels

file.bytes.total

file.bytes.in

file.bytes.out

file.open.count

file.time.total

host.count

host.error.count

proc.count

proc.start.count

net.mongodb.collection

all

net.mongodb.error.count

net.mongodb.operation

net.mongodb.request.count

net.mongodb.request.time

net.sql.query

all

net.sql.error.count

net.sql.query.type

net.sql.request.count

net.sql.request.time

net.sql.table

### Enable Troubleshooting Mode

To switch to the Troubleshooting mode, edit the dragent.yaml file:

1. Open the dragent.yaml file.

2. Add the following configuration parameter:

feature:
mode: troubleshooting
3. Restart the agent.