Advanced config

Change log level

/etc/srv-idp/integrations/log.yaml

log:
  level: INFO
  network: tcp
  address: 127.0.0.1:514

Can be set to "EMERGENCY", "ALERT", "CRITICAL", "ERROR", "WARNING", "NOTICE", "INFO" or "DEBUG".

Note that it should not be set to DEBUG in a production environment.

Service logs can be stored locally or remotely. The above snippet will work if there is a log-compatible client set to work on the provided address.

If you just want to change the log level we should set "network" to local. For example:

log:
  level: ERROR
  network: local
  address: 127.0.0.1:514

Stats for system performance

/etc/srv-idp/integrations/stats.yaml

The program uses StatsD to collect usage metrics which can then be used with a StatsD-compatible client such as Graphite to visually render key system performance information such as session starts, logins, communicating with the authentication server, spikes in 404 statuses etc.

An example config would be:

stats:
  prefix: srv-idp
  network: udp
  address: :8125

Note that prefix defines the prefix that is given to each bucket of stats. Address can be in the format of 'url:port' or just 'port'.

The above example would be suitable for a Graphite installation, as Graphite https://github.com/etsy/statsd/blob/master/docs/graphite.md listens on port 8125 by default. A useful Docker image for Graphite can be found at https://github.com/hopsoft/docker-graphite-statsd

REDIS settings

/etc/srv-idp/integrations/log.yaml

The system uses Redis to collect data for logged in sessions. Below is the default config. Redis can be used locally or installed on a separate machine. In a production environment, AWS Elasticache may be used.

redis:
  network: tcp
  address: :6379
  password: ""

Top