vastworks.blogg.se - Proxie tester

#Proxie tester pro

The round robin check cycles through the available agents, resulting in each agent executing the check every 180 seconds. In the diagram above, the standard check is executed by agents A, B, and C every 60 seconds.

Sensu also supports deduplicated check execution when configured with the round_robin check attribute.įor checks with round_robin set to true, Sensu executes the check once per interval, cycling through the available agents alphabetically according to agent name.įor example, for three agents configured with the system subscription (agents A, B, and C), a check configured with the system subscription and round_robin set to true results in one observability event per interval, with the agent creating the event following the pattern A -> B -> C -> A -> B -> C for the first six intervals.

Round robin checksīy default, Sensu schedules checks once per interval for each agent with a matching subscription: one check execution per agent per interval. Sensu requires that checks include either an interval attribute (interval scheduling) or a cron attribute (cron scheduling). You can schedule checks using the interval, cron, and publish attributes. Sensu entities become subscribers to these topics (called subscriptions) via their individual subscriptions attribute. The Sensu backend schedules checks and publishes check execution requests to entities via a publish/subscribe model.Ĭhecks have a defined set of subscriptions: transport topics to which the Sensu backend publishes check requests.

#Proxie tester pro

PRO TIP: If you’re familiar with the Nagios monitoring system, you may recognize this specification - it is the same one that Nagios plugins use.Īs a result, you can use Nagios plugins with Sensu without any modification.Īt every execution of a check command, regardless of success or failure, the Sensu agent publishes the check’s result for eventual handling by the event processor (the Sensu backend).

Exit status codes other than 0, 1, and 2 indicate an UNKNOWN or custom status.

For metric checks, this output contains the measurements gathered by the.

For service checks, this output is typically a human-readable message.

Result data is output to stdout or stderr.

Check result specificationĪlthough Sensu agents attempt to execute any command defined for a check, successful check result processing requires adherence to a simple specification. Check command executionĪll check commands are executed by Sensu agents as the sensu user.Ĭommands must be executable files that are discoverable on the Sensu agent system (for example, installed in a system $PATH directory). The Sensu user is not permitted to kill timed-out processes invoked by the root user, which could result in zombie processes. NOTE: Sensu advises against requiring root privileges to execute check commands or scripts.