Nexus OCSP Responder can work in an environment that includes a built-in system monitor – a supervisor. This article describes how to specify a Nexus OCSP Responder agent that sends signals to and receives signals from the supervisor. This is done in the "System management" section of the Nexus OCSP Responder configuration file.

Specify agent

• In the OCSP configuration file, specify the agent as follows:

  agent.supervisor.host=<host> agent.supervisor.port=<port> agent.supervisor.connect=[true|false

  Description of constants and values:

Specify agent logging items

Locally, the agent listens to all log messages. You can separate different logging items into different output units.

• In the OCSP configuration file, specify a type for each logging item as follows:

  agent.log.<#>.type=[file|stderr|syslog]

  Description of constants and values:

• For each agent log with ...type=file, specify the following:

  agent.log.<#>.prefix=<directory>/<filename> agent.log.<#>.period=<time expr>

  Description of constants and values:

Example:

This creates a file: <installdir>/log/oper-YYMMDD-HHMMSS.log. A new file is created each week.

• For each agent log with ...type=syslog, specify the following:

  Description of constants and values:

Apply filters to logging items

You can apply filters to the logging items to further fine tune the output.

1. To set up a filter for any log type, specify as follows in the OCSP configuration file:

   See this table for description of constants and values:

Examples

To filter all requests that are for non-issued certificates, create a filter like this:

This will filter out all warnings generated for the oper class of messages. Then any log scraper with search capabilities will be able to parse the logs for the message NON-ISSUED CERTIFICATE DETECTED and alert accordingly.

Split audit logs into different log files

The Nexus OCSP responder supports three different audit logs, see Log messages and log filters. To filter out and split different audit logs into different log files, specify as follows in the OCSP configuration file:

Configure fields to be displayed in a logger agent

You can configure which fields that should be displayed in a logger agent. In the OCSP configuration file, specify as follows:

See this table for description of constants and values:

You can also manipulate how a field will behave when used by the logger agent, for example, offset and length. To do this:

1. Specify integers on defined positions separated by a comma after a colon inside the curly brackets, such as {field:width,offset,length:novalue}, where:
   field - [string] the field name, for example, date
width - [integer] minimum width, default 1 or specified length
   offset - [integer] offset from start or offset from end if negative, default 0
   length - [integer] maximum length, default unlimited (0)
   novalue - [string] replacement string if no value exists for the provided field (default is ' - ')

2. To insert a line break after a field, use the keyword %s.

Example:

Define default global configurations for all agent loggers

Set the loggerdef parameter to define default global configurations for all agent loggers configured in your system. This can be useful if you want to specify filters or a field format that should be applied globally across all agents. If a logger agent specify the same parameter but with an another setting, the global setting will be overridden for that agent.

Example:

Related information

• Configure Nexus OCSP Responder

• Log messages and log filters

• Nexus OCSP Responder

• ISO 8601 Representation of dates and times