...
| Code Block |
|---|
define service {
use generic-service
host_name localhost
service_description JobSchedulerAgents
is_volatile 0
check_period 24x7
max_check_attempts 1
normal_check_interval 1
retry_check_interval 1
contact_groups admins
notification_options w,u,c,r
notification_interval 960
notification_period 24x7
check_command check_jobscheduler_agent_with_joc!http://localhost:4446!myJobSchedulerId!test:test!5!
active_checks_enabled 1
passive_checks_enabled 0
} |
Parameterization
Parameter |
| Default | Description |
|---|---|---|---|
| -j | --joc-url | — | Url of JOC Cockpit (http or https are supported) |
| -i | --id | — | Id of a JobScheduler Cluster |
| -a | --account | — | Account for HTTP authentication to JOC Cockpit (=<user:password>) |
-A | --agent | — | Url of an Agent, optional, can be specified several times |
-t | --timeout | 30s | Timeout for establishing the connection to JOC Cockpit |
| -d | --detailed | — | If set and the Cluster has more than one Master and not all Masters are running then the message contains host:port of each Master |
Example:
| Code Block |
|---|
#JobScheduler running with the id 'test' and JOC Cockpit has the url http://localhost:4446 where the account (user and password 'test') has access
<path_to_plugins>/check_jobscheduler_agent_with_joc.pl -j http://localhost:4446 -i test -a test:test |
See also
Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-684 Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1480 Jira server SOS JIRA serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1715
...