“Tim in accounts can’t access ServiceNow” you hear Joe the Line 2 technician who sits behind you say, you fire up a web browser and navigate to your ServiceNow instance – it works, you navigate to ServiceNow’s uptime statistics and see no blips/downtime reported … user error? intermittent network blip? issue for the finance team? You guess its likely a user error (Tim isn’t the best with technology) and leave it to Joe. Nothing the monitoring team can help with, time to get a tea.
After a chat with Barbra from marketing at the coffee machine you get back to a very busy IT department – It sounds like half the company can’t access ServiceNow! You crack open the SCOM console “just in case” and see if there are any alerts – nothing to see. Time for a biscuit.
After several hours it turns out Dave from the network team “made a few firewall changes” at the Frankfurt office at the time of the outage without an approved change window. After dealing with Dave *sigh … Dave!* your boss swings by your desk to ask why your monitoring team didn’t pick up the issue.
Sound familiar?
While there are many reasons why this outage could have been caused and many points you could have monitored to detect the impact of dodgy Dave’s change (monitoring the firewalls for example), often in-depth network monitoring simply isn’t realistic – it requires bespoke management packs for SCOM and/or network monitoring tooling which doesn’t come cheap.
The solution? Register for our webinar to learn how to monitor ServiceNow for free from SCOM!
Register for our webinar – 18-Dec @ 3pm GMT / 10am EST
Find out how SCOM can help with free outside in monitoring for ServiceNow so you can see what your end users see and get a deeper insight on your ServiceNow instances performance over time with over vital 30 performance counters
Find out how to get ahead of your boss and shine a light on issues such as this with your existing tooling