...
There is a lot of state change within Opsview. Sometimes this state change is considered spiurious upon human inspection while its always deemed a genuine issue per Opsview. Yale should tread carefully regarding opening this Opsview dataflow up to Service Now so as to avoid a firehose condition.
Moreover this integration should be used as a lightning rod to initiate and push for amending the monitoring stack where appropriate to dial back the amount of state change.
-nick, 20120305
We can work on dialing down yelling by tracking Top Talkers
Tickets
Opsview
- OVS-3105 servicedesk notifications db on external mysqld and not localhost?
- OVS-3107 curious about how opsview treats state when service now incident record isnt created
- OVS-3110 notifications not received by service now ; need help debugging
- OVS-3111 userland configurability of fields sent to service now during servicedesk-connector use?
- OVS-3113 support for running servicedesk-connector @ slaves in cluster as opposed to master
- OVS-3114 describe use of Contact Variables in Notification Methods
- OVS-3115 notifications never make their way to notifications db, service now
- OVS-3116 support for admin purging of events at spool for servicedesk connector
...