<commit_before>.. _centengine_plugin_api:

Centreon Engine Plugin API
**************************

Other Resources
===============

If you're looking at writing your own plugins for Centreon Engine,
please make sure to visit these other resources:

  * The official `Nagios plugin project website
    <http://sourceforge.net/projects/nagiosplug/>`_

Plugin Overview
===============

Scripts and executables must do two things (at a minimum) in order to
function as Centreon Engine plugins:

  * Exit with one of several possible return values
  * Return at least one line of text output to STDOUT

The inner workings of your plugin are unimportant to Centreon
Engine. Your plugin could check the status of a TCP port, run a database
query, check disk free space, or do whatever else it needs to check
something. The details will depend on what needs to be checked - that's
up to you.

Return Code
===========

Centreon Engine determines the status of a host or service by evaluating
the return code from plugins. The following tables shows a list of valid
return codes, along with their corresponding service or host states.

================== ============= ======================
Plugin Return Code Service State Host State
================== ============= ======================
0                  OK            UP
1                  WARNING       UP
2                  CRITICAL      DOWN/UNREACHABLE
3                  UNKNOWN       DOWN/UNREACHABLE
================== ============= ======================

Plugin Output Spec
==================

At a minimum, plugins should return at least one of text
output. Beginning with Centreon Engine 3, plugins can optionally return
multiple lines of output. Plugins may also return optional performance
data that can be processed by external applications. The basic format
for plugin output is shown below::

  TEXT OUTPUT | OPTIONAL PERFDATA LONG TEXT LINE 1 LONG TEXT LINE 2 ... LONG TEXT LINE N | PERFDATA LINE 2 PERFDATA LINE 3 ... PERFDATA LINE N

The performance data (shown in orange) is optional. If a plugin returns
performance data in its output, it must separate the performance data
from the other text output using a pipe (|) symbol. Additional lines of
long text output (shown in blue) are also optional.

Plugin Output Examples
======================

Let's see some examples of possible plugin output...

  * Case 1: One line of output (text only)
    Assume we have a plugin that returns one line of output that looks like this::

      DISK OK - free space: / 3326 MB (56%);

    If this plugin was used to perform a service check, the entire line
    of output will be stored in the
    :ref:`SERVICEOUTPUT <user_configuration_macros_service>` macro.

  * Case 2: One line of output (text and perfdata)
    A plugin can return optional performance data for use by external
    applications. To do this, the performance data must be separated
    from the text output with a pipe | symbol like such::

      DISK OK - free space: / 3326 MB (56%);|/=2643MB;5948;5958;0;5968

    If this plugin was used to perform a service check, the first
    portion of output (left of the pipe separator) will be stored in the
    :ref:`SERVICEOUTPUT <user_configuration_macros_service>` macro and
    the second portion of output (right of the pipe separator) will be
    stored in the
    :ref:`SERVICEPERFDATA <user_configuration_macros_service>` macro.

  * Case 3: Multiple lines of output (text and perfdata)
    A plugin optionally return multiple lines of both text output and
    perfdata, like such::

      DISK OK - free space: / 3326 MB (56%);|/=2643MB;5948;5958;0;5968
      / 15272 MB (77%);
      /boot 68 MB (69%);
      /home 69357 MB (27%);
      /var/log 819 MB (84%);|/boot=68MB;88;93;0;98
      /home=69357MB;253404;253409;0;253414
      /var/log=818MB;970;975;0;980

    If this plugin was used to perform a service check, the red portion
    of first line of output (left of the pipe separator) will be stored
    in the :ref:`SERVICEOUTPUT <user_configuration_macros_service>`
    macro.

The orange portions of the first and subsequent lines are concatenated
(with spaces) are stored in the
:ref:`SERVICEPERFDATA <user_configuration_macros_service>` macro. The
blue portions of the 2nd - 5th lines of output will be concatenated
(with escaped newlines) and stored in
:ref:`LONGSERVICEOUTPUT <user_configuration_macros_service>` the macro.

The final contents of each macro are listed below:

=================== =================================================================================================================
Macro               Value
=================== =================================================================================================================
$SERVICEOUTPUT$     DISK OK - free space: / 3326 MB (56%);
$SERVICEPERFDATA$   /=2643MB;5948;5958;0;5968 /boot=68MB;88;93;0;98 /home=69357MB;253404;253409;0;253414 /var/log=818MB;970;975;0;980
$LONGSERVICEOUTPUT$ / 15272 MB (77%);\\  /boot 68 MB (69%);\\  /var/log 819 MB (84%);
=================== =================================================================================================================

With regards to multiple lines of output, you have the following options
for returning performance data:

  * You can choose to return no performance data whatsoever
  * You can return performance data on the first line only
  * You can return performance data only in subsequent lines (after the
    first)
  * You can return performance data in both the first line and
    subsequent lines (as shown above)

Plugin Output Length Restrictions
=================================

Centreon Engine will only read the first 4 KB of data that a plugin
returns. This is done in order to prevent runaway plugins from dumping
megs or gigs of data back to Centreon Engine. This 4 KB output limit is
fairly easy to change if you need. Simply edit the value of the
MAX_PLUGIN_OUTPUT_LENGTH definition in the ``include/centengine.h.in``
file of the source code distribution and recompile Centreon
Engine. There's nothing else you need to change!

Examples
========

If you're looking for some example plugins to study, I would recommend
that you download the official Centreon Engine plugins and look through
the code for various C, Perl, and shell script plugins. Information on
obtaining the official Centreon Engine plugins can be found
:ref:`here <exploit_plugins>`.<commit_msg>push new title<commit_after>.. _centengine_plugin_api:

Centreon Plugin API
*******************

Other Resources
===============

If you're looking at writing your own plugins for Centreon Engine,
please make sure to visit these other resources:

  * The official `Nagios plugin project website
    <http://sourceforge.net/projects/nagiosplug/>`_

Plugin Overview
===============

Scripts and executables must do two things (at a minimum) in order to
function as Centreon Engine plugins:

  * Exit with one of several possible return values
  * Return at least one line of text output to STDOUT

The inner workings of your plugin are unimportant to Centreon
Engine. Your plugin could check the status of a TCP port, run a database
query, check disk free space, or do whatever else it needs to check
something. The details will depend on what needs to be checked - that's
up to you.

Return Code
===========

Centreon Engine determines the status of a host or service by evaluating
the return code from plugins. The following tables shows a list of valid
return codes, along with their corresponding service or host states.

================== ============= ======================
Plugin Return Code Service State Host State
================== ============= ======================
0                  OK            UP
1                  WARNING       UP
2                  CRITICAL      DOWN/UNREACHABLE
3                  UNKNOWN       DOWN/UNREACHABLE
================== ============= ======================

Plugin Output Spec
==================

At a minimum, plugins should return at least one of text
output. Beginning with Centreon Engine 3, plugins can optionally return
multiple lines of output. Plugins may also return optional performance
data that can be processed by external applications. The basic format
for plugin output is shown below::

  TEXT OUTPUT | OPTIONAL PERFDATA LONG TEXT LINE 1 LONG TEXT LINE 2 ... LONG TEXT LINE N | PERFDATA LINE 2 PERFDATA LINE 3 ... PERFDATA LINE N

The performance data (shown in orange) is optional. If a plugin returns
performance data in its output, it must separate the performance data
from the other text output using a pipe (|) symbol. Additional lines of
long text output (shown in blue) are also optional.

Plugin Output Examples
======================

Let's see some examples of possible plugin output...

  * Case 1: One line of output (text only)
    Assume we have a plugin that returns one line of output that looks like this::

      DISK OK - free space: / 3326 MB (56%);

    If this plugin was used to perform a service check, the entire line
    of output will be stored in the
    :ref:`SERVICEOUTPUT <user_configuration_macros_service>` macro.

  * Case 2: One line of output (text and perfdata)
    A plugin can return optional performance data for use by external
    applications. To do this, the performance data must be separated
    from the text output with a pipe | symbol like such::

      DISK OK - free space: / 3326 MB (56%);|/=2643MB;5948;5958;0;5968

    If this plugin was used to perform a service check, the first
    portion of output (left of the pipe separator) will be stored in the
    :ref:`SERVICEOUTPUT <user_configuration_macros_service>` macro and
    the second portion of output (right of the pipe separator) will be
    stored in the
    :ref:`SERVICEPERFDATA <user_configuration_macros_service>` macro.

  * Case 3: Multiple lines of output (text and perfdata)
    A plugin optionally return multiple lines of both text output and
    perfdata, like such::

      DISK OK - free space: / 3326 MB (56%);|/=2643MB;5948;5958;0;5968
      / 15272 MB (77%);
      /boot 68 MB (69%);
      /home 69357 MB (27%);
      /var/log 819 MB (84%);|/boot=68MB;88;93;0;98
      /home=69357MB;253404;253409;0;253414
      /var/log=818MB;970;975;0;980

    If this plugin was used to perform a service check, the red portion
    of first line of output (left of the pipe separator) will be stored
    in the :ref:`SERVICEOUTPUT <user_configuration_macros_service>`
    macro.

The orange portions of the first and subsequent lines are concatenated
(with spaces) are stored in the
:ref:`SERVICEPERFDATA <user_configuration_macros_service>` macro. The
blue portions of the 2nd - 5th lines of output will be concatenated
(with escaped newlines) and stored in
:ref:`LONGSERVICEOUTPUT <user_configuration_macros_service>` the macro.

The final contents of each macro are listed below:

=================== =================================================================================================================
Macro               Value
=================== =================================================================================================================
$SERVICEOUTPUT$     DISK OK - free space: / 3326 MB (56%);
$SERVICEPERFDATA$   /=2643MB;5948;5958;0;5968 /boot=68MB;88;93;0;98 /home=69357MB;253404;253409;0;253414 /var/log=818MB;970;975;0;980
$LONGSERVICEOUTPUT$ / 15272 MB (77%);\\  /boot 68 MB (69%);\\  /var/log 819 MB (84%);
=================== =================================================================================================================

With regards to multiple lines of output, you have the following options
for returning performance data:

  * You can choose to return no performance data whatsoever
  * You can return performance data on the first line only
  * You can return performance data only in subsequent lines (after the
    first)
  * You can return performance data in both the first line and
    subsequent lines (as shown above)

Plugin Output Length Restrictions
=================================

Centreon Engine will only read the first 4 KB of data that a plugin
returns. This is done in order to prevent runaway plugins from dumping
megs or gigs of data back to Centreon Engine. This 4 KB output limit is
fairly easy to change if you need. Simply edit the value of the
MAX_PLUGIN_OUTPUT_LENGTH definition in the ``include/centengine.h.in``
file of the source code distribution and recompile Centreon
Engine. There's nothing else you need to change!

Examples
========

If you're looking for some example plugins to study, I would recommend
that you download the official Centreon Engine plugins and look through
the code for various C, Perl, and shell script plugins. Information on
obtaining the official Centreon Engine plugins can be found
:ref:`here <exploit_plugins>`.

{'fraction_non_alphanumeric': 0.1576863354037267, 'fraction_numerical': 0.034472049689440995, 'mean_word_length': 4.142115768463074, 'pattern_counts': {'":': 0, '<': 19, '<?xml version=': 0, '>': 19, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2956994', 'n_tokens_mistral': 3600, 'n_tokens_neox': 3134, 'n_words': 1610}