Agent properties

Section describes all available properties for Jagger agents

Back to GitHub Monitoring Capabilities documentation

Agent properties

You can set following properties for Jagger agents:

# begin: following section is used for docu generation - Jagger Agent properties

# Flag to enable JMX monitoring
jmx.enabled=true
# Host:port of JMX service
jmx.services=localhost:9875
# Timeout to collect information via JMX
jmx.monitoring.timeout=300
# Timeout to collect profiling information via JMX
jmx.profiler.timeout=300
# URL format for JMX service - the address of a JMX API connector server
jmx.url.format=service:jmx:rmi:
# Timeout for attempt to connect to JMX port, ms
jmx.connection.timeout=1000
# Period for jmx connection during initialization, ms
jmx.connection.retry.period=3000

# Comma separated list of network interfaces where Sigar will collect network traffic
monitoring.agent.network.interface.name.masks=eth.*

# Address of coordinator host
chassis.coordination.http.url=http://localhost:8089
# Endpoint to post data to coordinator
chassis.coordination.http.exchange=/exchange
# Endpoint to post registration information to coordinator
chassis.coordination.http.registration=/registration

# Number of threads to keep in the pool, even if they are idle
chassis.executor.pool.core=5
# MaximumPoolSize the maximum number of threads to allow in the pool
chassis.executor.pool.max=20

# Period in ms. How often agent will send information to coordinator
agent.exchange.polling.rate=2000

# Agent name
agent.name=#RANDOM

# Set true if you want to profile SUT via JMX. Profiling result will be available in PDF report
profiler.enabled=false


# end: following section is used for docu generation - Jagger Agent properties