The User Experience group wants to see how you've customized your Orion to create your own NOC view, or NOC views you like and are using from other products. What do you like about your NOC view? What challenges, frustrations or issues do you have with it?--Show us your NOC view either here OR email it directly to me at email@example.com and share your NOC view stories by August 10 and we'll award you 500 thwack points for sharing.
UPDATE: we're no longer awarding points for this, but it's become a really popular post. Please continue to share how you create NOC views, pictures of them, etc with each other as there has been clear value to users in seeing what other users do, but UX can no longer award points for this.
Message was edited by: Kellie Mecham
I found it hard to display all the need to know info on one page, so i just made maps that contain the critical devices/apps to be able to quickly view if there are any issues and drill down from there.
Kellie, I emailed you the views as I am not allowed to post them.
We have a main view that gives us Severity, DateTime, Name, IP, Description of the alert, Alert Type (Device Type), alert Source, If it has been acknowledge, if there is a ticket and the status of the ticket.
We have the ability to get details of the current alert, history of the node, create a ticket from the alert, send the alert in an email, add notes to the alert, Triage (which takes you to the details page of the the node ie Solarwinds, dynatrace, etc), we can get the contact procedures for the alert and obviously clear it.
we can toggle the view to have a side by side map which allows us to see the alerts by region and weather to correlate issues.
This is our main daily view we see every morning. If anything goes down in the Map section needs immediate attention while down nodes will help show specificly what is down which is helpful especially if something is red in the MAP view. The group view shows who the down nodes belong to in our group. We filtered any nodes that IT we are not resposible for by email address and if the node does not have that email it will ignore the down node.(it will still alert someone else just not our group and we won't see it the other group does).
As the monitoring team, we need to see things as they happen. This view shows us Nodes and interfaces with problems. Also a full hardware health overview and the graph on the right is a graph of the pollers pulling # of users on our VPN (the break in the graph was poller server repair earlier today) Normally a break or "Dip" in that graph means VPN issues and then i really start working. Critical Applications (DHCP Server Service & Wireless Radius Services begin monitored). Then High Errors and discards for today (Customized to filter out FW's and other appliances that discard packets) ; and Discards this hour for more granularity. Also we have the last 1- config changes, so each morning we can come in and see who did what to what and where. Polling Engine status has been inportant to us in the past, but that will be replaced after we confirm our pollers to be up to speed and an installation of another.
Now, if you were sitting here and i scrolled down.... which does happen from time to time on our big screens.
you would see also
1 :Interfaces with High % usage
2: Custom Property - Tracking Nodes with open tickets/work orders ; & ;
3: a UnDP Table showing Cisco devices with a VTP Mode value other than Transparent (3)
4: A Long list of all dependencies that are setup (but that one is way down there)
The idea here, being anything that breaks will show at the top, real issue or problem area's will also show within our problem fields and the errors/discards for the day. And quick access to config changes and (below that) current open tickets allows us to see if it is yet to be resolved or if a rogue engineer made a change last night and did not tell anyone.
This is a view that I use on my own machine; as the 1st post is what shows on 1 of our 42" monitors on the wall.
The Tops AJAX View is the main section that we alert on; that is the sutff we really care about.
The 2nd AJAX view are items that we either don't alert on (as the department needed a view or a way to see up/down but wanted no emails) or these have alerts setup for specific departments and the IT groups are not notified about these.
How did you accomplish your ticket integration? I noticed the view with nodes with tickets. I need to create that using Remedy but I'm not an SQL guy and I'm looking for ideas. Thanks a bunch!!
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.