Resource Type: nimsoft_logmon_profile

Defined in:

lib/puppet/type/nimsoft_logmon_profile.rb

Providers:

nimsoft

Overview

The ‘nimsoft_logmon_profile` type describes a profile of the `logmon` probe. A profile can be used to monitor a specific logfile and watcher rules describe patterns that can be found in the specific logfile.

The ‘nimsoft_logmon_profile` type does only describe general profile attributes and watcher rules can then be described as a `nimsoft_logmon_watcher` resource.

Example:

nimsoft_logmon_profile { 'system log':
  ensure       => present,
  active       => yes,
  file         => '/var/log/messages',
  mode         => updates,
  qos          => no,  # do not generate Quality of Service messages
  alarm        => yes, # allow creation of alarm messages
  alarm_maxsev => critical,
}

Please note that the ‘logmon` probe is also able to monitor a url, the exit code of a command, or a nimbus queue. These alternate usecases cannot be handled by the `nimsoft_logmon_profile` resource (yet)

Properties

• active

  Set to ‘yes’ if the profile should be active and ‘no’ if the profile should be inactive

  Supported values:

  • yes
  • no
• alarm

  Describes wether or not alarm messages should be sent when a watcher rule matches

  Supported values:

  • yes
  • no
• alarm_maxserv

  The maximum alarm severity.

  Supported values:

  • info
  • warning
  • minor
  • major
  • critical
• ensure (defaults to: present)

  The basic property that the resource should be in.

  Supported values:

  • present
  • absent
• file

  The filename you want to monitor. You can also include time formatting primitives (see the probe manual)

• interval

  Specifies the interval between two checks. Can be expressed in minutes (e.g. ‘10 min`) or seconds (e.g. `30 sec`)

• mode

  The mode describes how the probe monitors the specific file. Valid options are ‘cat` (file is always scanned from top to bottom), `updates` (file is scanned from the last EOF mark), `full` (like `cat`, but file must change between two runs), and `full_time` (like `full`, but only access time has to change, not the content itself)

  Supported values:

  • cat
  • updates
  • full
  • full_time
• qos

  Describes wether or not variables and number of matches should be sent as Quality of Service messages

  Supported values:

  • yes
  • no

Parameters

• name (namevar)

  The name of the profile

• provider

  The specific backend to use for this ‘nimsoft_logmon_profile` resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.