...
- per Lou: Critical Alerts from Opsview should be set to a priority level of "High" in SN and Warnings be set as "Average".
- field mappings: "CLIENT=OPsView, "CONTACT=Operator" "NOTIFY=NONE", "CONTACT TYPE=Tier 2", "Incident Type=Service Event", and Priority=3-High" on the SN screen.
- left-nav item for unassigned opsview tickets (or bookmark/view) for ops staff
- Downtimed state change => handled => open ticket?
- Yellows/warnings + tickets as they effect workflow
- OVS-3236
- Assign warns to proper group ; assign crit to DC Ops
- Acknowledgements
- auto-ack @ Opsview and how this impacts Yale workflow
- this means that Unhandled column in Opsview goes away, becomes meaningless, etc. Important if thats a catalyst for starting Ops work (procedure, call, etc).
- Getting keyword data transmitted
- OVS-3237
- PS engagement underway, no ETC
- Oddballs (non-ITS like YUHS)
- Oddballs can stay behind if needed; they dont block ITS from moving. This is all driven with notification profiles where we can poz match keywords.