puppet on monitor1.cz2.id.lan

State: OK

Not in scheduled or unscheduled maintenance.

Schedule Maintenance

Output: CheckPuppet OK: Puppet ran successfully

Address:172.27.213.7 Tags:teamoperations,organizationidnet,local-common

Last state change: about 4 hours ago 2025-03-13 04:02:44 +0000  
Last update: 5 minutes ago 2025-03-13 08:22:45 +0000  
Last critical notification: 9 months ago 2024-05-27 14:51:37 +0000
Last warning notification: about 5 hours ago 2025-03-13 03:52:44 +0000
Last unknown notification: over 3 years ago 2022-02-01 05:52:20 +0000
Last recovery notification: about 4 hours ago 2025-03-13 04:02:44 +0000 CheckPuppet OK: Puppet ran successfully
Last acknowledgement notification: never    

Recent state changes

Timestamp State Summary
2025-03-13 04:02:44 +0000 ok CheckPuppet OK: Puppet ran successfully
2025-03-13 03:32:44 +0000 warning CheckPuppet WARNING: Puppet ran with errors: events/failure=1; resources/failed=1;
2025-03-12 04:02:43 +0000 ok CheckPuppet OK: Puppet ran successfully
2025-03-12 03:32:43 +0000 warning CheckPuppet WARNING: Puppet ran with errors: events/failure=1; resources/failed=1;

Failure Delays

Initial failure delay: 30 secs
Repeat failure delay: 1 min 0 secs

Scheduled Maintenance Periods

No maintenance is scheduled

Add Scheduled Maintenance

e.g. "today 4pm", "two hours hence", "friday 2pm", "2012-01-28 13:00"
e.g. "1 hour", "2:30:00", "three days", etc
Times given will be interpreted in the local timezone of UTC (UTC+00:0)

Contacts

Name Media
Vaclav Strachon

Pagerduty

Zone of Surprise

Decommission check

Hide the check from the Flapjack web interface. Use this if you are no longer actively running this check.

Flapjack will automatically re-commission this check if it receives another event for it.