This article describes how to use standard reports in Service Manager.
The simple reporting infrastructure that is included in Service Manager is built on SQL Server Reporting Services (SSRS), where data is accessed from the Service Manager data warehouse. The SSRS infrastructure provides for basic reporting functionality, such as report-level security, report subscriptions, browser-based access to reports, linked reports, and customization. This reporting functionally is similar to the experience that is included with System Center Operations Manager.
The Reporting workspace contains the catalog of reports that users can run on demand. Reports are viewable for all Service Manager console users. If users can view work items and have permission to the SystemCenter and ServiceManager folders on the SSRS server, they can also view reports in work item task lists. Like in Operations Manager, you can run a report in context. For example, you can select a computer in a view in the console and then run the Computer Details report about that computer. Any user can export report data from a report they view. Exported reports are saved in various file formats.
For more information about SSRS, see SQL Server Reporting Services. If you want to see the relationship between high-level processes and services that are involved between Service Manager and SSRS, refer to the Service Manager architecture diagram (ArchitectureDiagram.vsd) that is included in the Service Manager job aids (SM_job_aids.zip). Because the architecture diagram is too large to see properly in this guide, you can download it and the other jobs aids from the Microsoft Download Center.
You can use the following procedure to view the catalog of reports that is available in Service Manager.
By default, all System Center 2016 - Service Manager users have access to reports through the Reporting workspace. However, before users who don't have administrator permissions can view the Reporting workspace, you must add permissions through SQL Server Reporting Services (SSRS).
By default, all System Center - Service Manager users have access to reports through the Reporting workspace. However, before users who don't have administrator permissions can view the Reporting workspace, you must add permissions through SQL Server Reporting Services (SSRS).
You can grant access at the root level, which enables a user to view the Reporting workspace and all the reports in Service Manager. You can also grant restricted access to specific report folders, such as the Incident report folder, or to individual reports.
The following procedure describes how to grant SSRS access for all the Service Manager reports to an Active Directory group (woodgrove\SCSMReportAccess).
You can use the following procedure to run a report in Service Manager. In this procedure, you run an incident management report to determine how many incidents were resolved in the previous week.
Before you can run a report, the extract, transform, and load (ETL) process must be complete. For more information about the ETL process and about how to schedule it to run, see How to Enable Data Warehouse Jobs Schedules.
The Service Manager data warehouse doesn't create dimensions for classes or relationships in unsealed management packs. If you're using an unsealed management pack, you won't see any data from that management pack in your reports. Because of this, the best practice is to model all classes and relationships in sealed management packs.
For this example, you must have previously created an incident. Otherwise, the report will return no data.
Note If there is no data in the report, ensure that the ETL process is complete. A delay might occur between the start of the process and when data is available for reports.
You can use the following procedure to export a report into several different types of files so that you can use the data from the reports in different tools. For example, you can export the report data into a comma-separated value (CSV) file and then import it into Microsoft Office Excel.
You can use the following procedure to create a linked report.
A linked report is a shortcut to a report—it's similar to a program shortcut on your desktop. A linked report is derived from publicly defined reports from any management pack. A linked report retains some of the original report's properties, such as the report layout. Other properties of the linked report, such as parameters and subscriptions, can be different from the original report.
You might have to close and reopen the console after the synchronization job is complete to see the report.
You can use the following procedure to add a report to the Favorite Reports folder in Service Manager.
After you've run several reports and determined the best parameters to use to customize the report contents, you can save a report to the Favorite Reports folder. This enables you to run the report directly from the Reporting view without having to specify parameters.
You can set up subscriptions to your reports in Service Manager through SQL Server Reporting Services (SSRS) Report Manager. Configuring a subscription to a report enables you to automate the delivery of a report. Report subscriptions can be sent through email, stored on the report server, or even posted to a Microsoft SharePoint site.
In Service Manager, you can schedule a linked report to run regularly to ensure that the information is up to date. To do this, use SQL Server Reporting Services (SSRS) Report Manager. In SSRS Report Manager, you can schedule reports to run one time or on a continuous basis at intervals of hours, days, weeks, or months. You can do the following:
You can display SQL Server Reporting Services (SSRS) reports from any source using the Reporting workspace in the Service Manager console. The Reports workspace in Service Manager displays the folders and reports that are contained in the System Center\Service Manager folder on the SSRS server. Therefore, you can add any reports that you want to the folder. For example, you might have a financial report that you want to view from the Reporting workspace.
The following reports are available in Service Manager.
Report area | Report name | Description |
---|---|---|
Activity management | List of Activities | Provides a list of activities within a certain time frame that meet the specified criteria. The data in the report includes the type of activity, the current status, and the priority. |
Activity management | List of Manual Activities | Provides a list of all the manual activities within a certain time frame that also meet the specified criteria. The data in the report includes the current status, stage, priority, and user to whom the activity is assigned. |
Activity management | List of Review Activities | Provides a list of all the review activities within a certain time frame that meet the specified criteria. The data in this report includes the current status, stage, approval condition, and approval threshold. |
Activity management | Manual Activity Detail | Provides detailed information about a specific manual activity, including the title, description, status, and affected customers. |
Activity management | Review Activity Detail | Provides detailed information about a specific review activity, including the title, description, status, reviewers, and approval condition. |
Activity management | Activity Distribution | Provides the number of activities during a specified time frame. The data in this report includes the activity status, type, and stage. You can filter the data by status, stage, or type. |
Change management | Change Management KPI Trend | Provides the number and current state (in progress, completed, failed, or canceled) of change requests during a specified time frame. You can filter the data returned in this report by day, week, month, quarter, or year. |
Change management | List of Change Requests | Provides a list of change requests within a certain time frame. The data in this report includes the current status, category, and user to whom the request is assigned. |
Change management | Change Request Detail | Provides detailed information about a specific change request, including the title, description, status, change creator, and template. |
Configuration management | Computer Detail | Provides detailed configuration information for a specific computer. |
Configuration management | Computer Inventory | Provides a list of computers available in the management group. Note: The Computer Inventory report might contain more total computers than actually exist in a single Service Manager management group. This situation is uncommon but possible when you've more than one management group share a data warehouse. More specifically, if you manually create a computer in one management group and manually create a computer with the same name in another management group, the data warehouse can't reconcile the two manually-created computers. Because this situation doesn't occur when computers are discovered by a connector, you can avoid multiple computers appearing in the report by deleting the manually-created computer configuration item and then discover it by using a connector. |
Configuration Management | Software Update Compliance Trend | Provides detailed information for software update compliance. You can filter this data by classification or category, and by day, week, month, quarter, or year. |
Incident management | Incident Analyst | Provides key performance metrics for a specified analyst. The data in this report includes the number of incidents assigned to the analyst, the number of incidents resolved by the analyst, the number of incidents worked on by the analyst, and any labor logged against an incident. |
Incident management | Incident Details | Provides detailed information for a specific incident, including the title, description, classification, affected services, affected configuration items, and related activities. |
Incident management | Incident KPI Trend | Provides the number of incidents, including the number of incidents past their targeted resolution time, the number of escalated incidents, the average time to resolution, the labor minutes per incident, and the size of the incident backlog. You can filter this data by classification or category, and by day, week, month, quarter, or year. |
Incident management | Incident Resolution | Provides the number of incidents, including the number of incidents past their targeted resolution time and the average time to resolution. You can filter the data by day, week, month, quarter or year. |
Incident management | List of Incidents | Provides a list of all incidents within a certain time frame. The data in this report includes the users to whom incidents are assigned, when the incidents were created, and the current status of the incidents. |
Problem management | Configuration Items (CIs) with Most Incidents | Provides a list of the configuration items that have at least the number of incidents associated with them, as specified by the value you enter for Incidents per Configuration Item during the specified time frame. This report also includes the number of change requests and problems associated with the specific configuration item. |
Problem management | List of Problems | Provides a list of all problems within a certain time frame. |
Problem management | Problem detail | Provides detailed information for a specific problem. |
Release management | List of Release Records | Provides a list of all release records within a certain time frame. |
Release management | Release Record Detail | Provides detailed information for a specific release record. |
Service Management | Service KPI Trend | Provides key metrics across services, groups and collections for Service Manager, Operations Manager, and Configuration Manager. This report enables trending and flexible grouping. |
Service Management | Service Summary | Provides a scorecard-like report that includes a comprehensive view of the health of a service, including period-over-period analytic capabilities. |