Have sent you a mail directly.
Emailed you directly.
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).
email sent directly
2 of 2 people found this helpful
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.
1 of 1 people found this helpful
Our main summary view is one of many that are used in displaying our current environment. We have a NOC area where we have three 60" displays pointed to our web console displaying the Alerts page, a process/application specific view and a view showing all volume alert, and down and critical applications...
I emailed my views directly to you. I'm still in "tweak" mode with my summary view, but i'm approaching the design with the idea that my summary page should provide a very quick "10,000 foot" view of our infrastructure and it's health.
Hey all, feel free to share stories of what you want, views from other products (scrubbed of course and/or emailed to me directly only), and perfect world descriptions. Keep 'em coming!
Kellie, I have sent you some of our dashboards and some information about them; hope it helps!
4 of 4 people found this helpful
Our NOC view is mainly a Network WAN view. It relies heavily on Gob's custom resources, How long a node/interface down, and his filtered events resource. The Sactun view is all the nodes along a traceroute to this site. It is an unstable IPSec VPN site, and has just one path to Mexico. This lets us monitor where we have packet loss. We also watch the number of sessions on Riverbeds since its licensed by concurrent session. Rest are various node issues.
I like the map in the middle and how you added clocks for the parts of the world you care about. Thanks for sharing!