Maniphest T274663

Icinga meta monitoring recovery didn't resolve VO page
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	herron
	Feb 12 2021, 4:02 PM

Tags

Referenced Files

None

Subscribers

Description

Meta monitoring alerted for icinga1001 going down during a reboot today, but the recovery notification didn't auto-resolve the VO incident.

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Resolved		fgiunchedi	T264016 Host page did not auto-resolve in VO
		Resolved		fgiunchedi	T274663 Icinga meta monitoring recovery didn't resolve VO page

Event Timeline

herron created this task.Feb 12 2021, 4:02 PM

herron triaged this task as Medium priority.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 12 2021, 4:02 PM

herron moved this task from Inbox to Backlog on the observability board.Feb 22 2021, 3:35 PM

herron moved this task from Backlog to In progress on the observability board.

• lmata edited projects, added SRE Observability (FY2021/2022-Q1); removed observability.Jul 12 2021, 2:20 AM

• lmata moved this task from Inbox to In progress on the SRE Observability (FY2021/2022-Q1) board.

• lmata lowered the priority of this task from Medium to Low.Aug 18 2021, 2:15 PM

• lmata edited projects, added Observability-Alerting; removed SRE Observability (FY2021/2022-Q1).

• lmata added a parent task: T264016: Host page did not auto-resolve in VO.

• lmata mentioned this in T313958: Evaluate viable candidates for incident paging.Jul 27 2022, 8:14 PM

• lmata moved this task from Inbox to Backlog on the Observability-Alerting board.Sep 6 2022, 6:56 PM

I'm fairly sure this is fixed by https://phabricator.wikimedia.org/T264016#10825271