This is the first in a number of blog posts that I have decided to put together that will show how to build a complete custom dashboard solution for your System Center Operations Manager (SCOM) 2007 R2 environment that incorporates the System Center Service Manager (SCSM) Dashboard, the SCOM Service Level Dashboard (SLD) 2.0 and also a Distributed Applications Health State Scorecard into a seamless tabbed window for easy-on-the-eye SCOM data consumption.
Dashboarding in SCOM out of the box is very minimal and the only official SCOM dashboard that Microsoft have provided is the Service Level Dashboard 2.0 which looks great but is only really effective when pointed to Distributed Applications and their respective Service Level Objectives.
What SCOM was lacking was a dashboard solution that was supported by Microsoft, included the ability to present data such as 'Computers with the most Alerts', 'SCOM DB size', 'Distributed Application Health State', 'Noisiest alerts' etc; and most importantly one that was provided for FREE!
I have come across a great number of blog posts from the SCOM community that cover each of these aspects of SCOM Dashboarding individually but have found nothing out there that brings all of the solutions centrally together onto one site.
The posts that follow in this series will go into detail with the information that you need to create these solutions and customise them for your different client environments.
See below for the links to the other posts in this series:
SCOM Dashboards - Part 1- Installing WSS 3.0
SCOM Dashboards - Part 2 - Installing the Dashboard Solution Accelerator
SCOM Dashboards - Part 3 - Customizing the Dashboard Banner and Logo
SCOM Dashboards - Part 4 - Customizing the Dashboard Tabs
SCOM Dashboards - Part 5 - Installing the Service Level Dashboard (SLD 2.0)
SCOM Dashboards - Part 6 - Adding SQL Queries to the Dashboards
SCOM Dashboards - Part 7 - The SCOM Distributed Application Health State Tab
SCOM Dashboards - Part 8 - Adding the SLD Tab to the SCOM Dashboard
SCOM Dashboards - Conclusion and References
Kevin Greene's IT Blog. This is a blog about all things Cloud and Datacenter!
I get as far as Part 5. In SLD, under "Site Settings", "Edit", I only get "No SLA's present" under Dashboard configuration. I installed the MP in SCOM prior to that. How can I troubleshoot this?
ReplyDeleteHi there and thanks for the comment. Are you having an issue with being able to see the Service Level Objectives within the dashboard or is it another issue in relation to customising it?
ReplyDeleteI am still at Part 5, "Installing the SLD". The instructions say to click on Site Settings>Edit> and then "Click on the available Service Levels from the list and then select 'Apply Filter'". When I do that I see no Service Levels, just a message under Service Level Section that says "No SLA's Present".
ReplyDeleteIf you see the 'No SLA's Present' message, then most likely you haven't configured any Service Level Objectives and attached them to your Distributed Applications.
ReplyDeleteThis would need to be done first from the 'Authoring' tab, under 'Management Pack Objects' and then 'Service Level Tracking'.
Once you configure the SLO's here, then you'll be good to go from within your SLD!
Hi kevin,
ReplyDeleteI am facing an issue with SCOM 2007 where in if community string name is not used as public but and other name is used mp discovery is not happening. Is it mandatory to have community name as public only
Hi there,
ReplyDeleteThanks for the comment.
It is definitely NOT mandatory to have the SNMP community name set to 'public'. In fact it is considered a security risk by leaving it set to 'public' and I would always recommend that you change the SNMP community string to something more secure.
You need to take into account that when discovering devices through SCOM using SNMP, that the SNMP community string can sometimes be configured or specified in different locations on the hardware that you are trying to monitor. For example, you may have one SNMP community string specified for Read Only SNMP access and a different one specified for Read and Write.
I would advise you to re-check the device that you want to monitor via SNMP again and refer to the user guide for the device to see exactly where the SNMP configurations are on it.
Hope this helps!
Kevin.
Hi Kevin,
ReplyDeleteWhat is happening here is when public community string is there as read only we are able to see 11 components under health collection data of scom. However if we change the community singh with other name but same read only access then we are able to see only 8 componenets and we cant see management processor, server networks and server storage componenets then.
Is it anything to do with access here.
Regards,