RS2005 Health Check

We currently have an instance of a Reporting Services 2005 server running
that host many different reports for many different groups (over 100 groups)
within the company. We would like to setup a "health check" page that will
give us a status (like running or not running) for all of the components
within Reporting Services. I would like to know what are all of the
components within Reporting Services that I should test for to verfiy that
everything is running. Also, has anyone done this that can provide me any
input. Any code examples or tools would be helpful to me too.We setup a very basic IISOK page. All the report does is display IISOK
in the body. An corporate wide monitoring program calls this page and
checks that IISOK is being displayed every 15 minutes. This proves
that RS is up and running and able to check it's DB. You could
probably do the same calling the RS webservices just to see that
they're responding.|||Thanks for kelkoenig's input.
Hi David,
Basically, what we can check against the SSRS are the server application
and database's availability, include:
** whether reportserver application is available
**whether report manager application is available
** whether the reporting service windows service is running
** whether the backend database is connected
Also, for more complex health monitoring or analysis, you can consider use
the reporting service's built-in performance counters and the log
files(text format which can be queried programmaticaly).
#Monitoring Report Server Performance
http://msdn2.microsoft.com/en-us/library/ms159809.aspx
#Reporting Services Log Files
http://msdn2.microsoft.com/en-us/library/ms157403.aspx
Hope this also helps some.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.