...
- 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
Next Steps
- Bind creds @ Service Now
- Verify least privledge through Opsera + Service Now
- https://secure.opsview.com/jira/browse/OVS-3110
- Need Service Now ticket
- Generate dummy data in SN sbx ECC queue to verify conduit function
- http://docs.opsview.com/doku.php?id=servicedesk-connector-latest:configuration#testing
No Format $ NAGIOS_LASTHOSTCHECK=1234567891 NAGIOS_LASTHOSTUP=1234567890 NAGIOS_HOSTOUTPUT="Test failure" NAGIOS_HOSTADDRESS=10.11.12.13 NAGIOS_LONGDATETIME="Dec 1 2009" NAGIOS_HOSTALIAS="temp host 1" NAGIOS_LASTHOSTDOWN=0 NAGIOS_LASTHOSTSTATECHANGE=0 NAGIOS_NOTIFICATIONTYPE=PROBLEM NAGIOS_HOSTSTATE=DOWN NAGIOS_HOSTNAME=host1 /opt/opsview/notifications/bin/opsview_notifications servicenow Notification submitted
- Egress packet filter in the way. Eval scalable means to open up.
- Verify endpoints for Service Now for egress packet filter purposes (Yale firewalls outbound)
- Is 199.91.136.0/21 too much, too little, etc?
- Bootstrap Notification Methods
- Verification of fields being fixed, unchangeable
- Consider keywords for service now only ; not all events would enter SN only those we say to per tags