Scheduler configuration¶
The scheduler is a service with is responsible for managing schedules for SNMP walks and GETs. Schedules definition are stored in Mongo DB.
Scheduler configuration file¶
Scheduler configuration is kept in values.yaml
file in section scheduler
.
values.yaml
is being used during the installation process for configuring Kubernetes values.
Example:
scheduler:
logLevel: "WARN"
profiles: |
test_profile:
frequency: 5
condition:
type: "field"
field: "SNMPv2-MIB.sysDescr"
patterns:
- "^.*"
varBinds:
# Syntax: [ "MIB-Component", "MIB object name"[Optional], "MIB index number"[Optional]]
- ["SNMPv2-MIB", "sysDescr",0]
Define log level¶
Log level for scheduler can be set by changing the value for key logLevel
. Allowed values are: DEBUG
, INFO
, WARNING
, ERROR
.
The default value is WARNING
Define resource requests and limits¶
scheduler:
#The following resource specification is appropriate for most deployments to scale the
#Larger inventories may require more memory but should not require additional cpu
resources:
limits:
cpu: 1
memory: 1Gi
requests:
cpu: 200m
memory: 128Mi
Define groups of hosts¶
To get the general idea when groups are useful see Configuring Groups.
Example group configuration:
scheduler:
groups: |
example_group_1:
- address: 123.0.0.1
port: 161
- address: 178.8.8.1
port: 999
- address: 12.22.23
port: 161
community: 'private'
example_group_2:
- address: 103.0.0.1
port: 1161
version: '3'
secret: 'my_secret'
- address: 178.80.8.1
port: 999
The one obligatory field for the host configuration is address
. If port
isn’t configured its default value is 161
.
Other fields that can be modified here are: community
, secret
, version
, security_engine
.
However, if they remain unspecified in the host configuration, they will be derived from the inventory record regarding this specific group.