Section "Monitoring"

The settings in this section control the monitoring capabilities of kenaflow.

For details please read article Monitoring

usePerformanceCounter

    <entry key="usePerformanceCounter" type="System.Boolean" default="false"></entry>

kenaflow offers a basic set of performance counters that integrate into Windows OS and can be used locally on the kenaflow server using perfmon or with any third party monitoring that can leverage Windows performance counter.

With this setting the use of performance counters can be enabled or disabled (default).

WorkReportHookAddress

    <entry key="WorkReportHookAddress" type="System.String" default=""></entry>

kenaflow is able to report its work to a webhook for monitoring purpose.

With this setting you can specify a webhook that is able to receive kenflow work reports.

ClientStartReportHookAddress

    <entry key="ClientStartReportHookAddress" type="System.String" default=""></entry>

kenaflow uses sub processes for workflow execution and several other tasks.

Sub processes are started and/or restarted regulary.

This web hook can be used for monitoring purpose to inform a monitoring system about the start of sub processes.

PingICMP

    <entry key="PingICMP" type="System.String" comment="[ip/host]|[time-between]|[max-ok-latency-msec]|[stop-after-failed-count]|return-to-normal-after-count]~..."></entry>

kenaflow is able to monitor other network related devices to check its connectivity.

Here you can specify zero, one or more devices that have to be available over ICMP ping to infornm kenaflow about network connectivity.

One entry consists of this settings, separated by | (pipe character):

  • IP address or host name
  • time between two ICMP pings (in milliseconds)
  • maximum latency (in milliseconds)
  • mark this entry (device) as "failed" (= not reachable / disconnected) after this number of failures
  • mark this entry (device) as "normal" (= reachable / connected) after this number of successful ping AFTER it's in "failed" state

Sample for two entries: 172.16.1.1|5000|1|5|5~domaincontroller2.company.local|5000|1|5|5

PingWebHook

    <entry key="PingWebHook" type="System.String" comment="[url]|[time-between]|[expected-http-status-code]|[stop-after-failed-count]|return-to-normal-after-count]~..."></entry>

kenaflow is able to monitor other network related devices to check its connectivity.

Here you can specify zero, one or more devices that have to be available over HTTP web request to infornm kenaflow about network connectivity.

One entry consists of this settings, separated by | (pipe character):

  • URL to web resource
  • time between two HTTP request (in milliseconds)
  • desired HTTP response status code
  • mark this entry (device) as "failed" (= not reachable / disconnected) after this number of failures
  • mark this entry (device) as "normal" (= reachable / connected) after this number of successful ping AFTER it's in "failed" state

Sample for two entries: http://ping1.company.local|5000|200|5|5https://172.16.1.1|5000|200|5|5

StopCountFailedPings

    <entry key="StopCountFailedPings" type="System.Int32" comment="how much ping conditions must fail from setting above before pausing the engine?" default="1"></entry>

The settings determine the number of ping tests that must fail before kenaflow stops work.

It must be >= 1.

It is not used if there is no setting for PingICMP and/or PingWebHook.

Full Section Default

  <section name="monitoring">
    <entry key="usePerformanceCounter" type="System.Boolean" default="false"></entry>
    <entry key="WorkReportHookAddress" type="System.String" default=""></entry>
    <entry key="ClientStartReportHookAddress" type="System.String" default=""></entry>
    <entry key="PingICMP" type="System.String" comment="[ip/host]|[time-between]|[max-ok-latency-msec]|[stop-after-failed-count]|return-to-normal-after-count]~..."></entry>
    <entry key="PingWebHook" type="System.String" comment="[url]|[time-between]|[expected-http-status-code]|[stop-after-failed-count]|return-to-normal-after-count]~..."></entry>
    <entry key="StopCountFailedPings" type="System.Int32" comment="how much ping conditions must fail from setting above before pausing the engine?" default="1"></entry>
  </section>

Discussion