MicroStrategy - Enterprise Manager - Reports

mstr-em

Continue reading page 914 of the Admin.pdf file

What reports are available by default?

General:

  1. Real-Time Server Usage Dashboard: This dashboard provides a comprehensive real-time overview of activity on your server machines. Best viewed with default prompt answer (Today's data).
  2. Server Caching Optimization Advisor: This interactive dashboard is an Intelligence server workload optimization wizard. It provides guidance on optimal caching based on historical usage monitoring.
  3. Enterprise Manager Overview Dashboard: This Interactive Dashboard looks at different areas of Business Intelligence Analysis. This Dashboard explores Intelligence Server, Report Services, Distribution Services, and OLAP Services usage.
  4. (Performance Analysis) 40. System Performance Trends: Graph of performance metrics determined by prompts on metrics and a date dimension attribute.
  5. (Performance Analysis) 40.1 Average Execution Time vs. Number of Jobs per User: Provides a comparison of the elapsed report execution duration and the average number of jobs per user over time.
  6. (Performance Analysis) 40.2 Average Execution Time vs. Number of Sessions: Provides a comparison of the elapsed report execution duration and the number of sessions over time.
  7. (Performance Analysis) 42. Job Performance Trend: Provides a comparison of the elapsed report execution duration and the number of jobs over time.
  8. (Performance Analysis) 45. User Data Request Performance Breakdown: This report provides insight into how Users are using the monitored Projects and Intelligence Server. This report also looks at the User experience for the monitored systems with respect to the data requested.
  9. (Operations Analysis > Resource Utilization) 30. Execution Cycle Breakdown: Provides the breakdown over time of the four steps in the report execution cycle: queue, sql generation, sql execution, and analytical engine. This report is prompted on time.
  10. (Operations Analysis > Resource Utilization) 30.1 Queue Time Breakdown: QUEUE TIME BROKEN DOWN INTO PROMPT RESOLUTION AND EXECUTION WAIT TIMES
  11. (Operations Analysis > Resource Utilization) 30.2 Queue to Exec time ratios by Server Processing Unit: Breakdown of queue time and execution time per processing unit.
  12. (Operations Analysis > Resource Utilization) 30.3 Effect of job prioritization on queue time: Provides an analysis of the effect of job prioritization on the queue time, cpu time & elapsed duration.
  13. (Operations Analysis > Resource Utilization) 31. Activity Analysis by Weekday/Hour Working Set: Provides the activity analysis on a hourly basis. This report prompts the user for an appropriate metric and also for a time period over which the analysis should be based.
  14. (Operations Analysis > Resource Utilization) 32. Peak Time Periods: Provides information of the average queue duration per job, the report execution duration, and number of jobs on hourly basis. This report is prompted on time.
  15. (Operations Analysis > Resource Utilization) 33. Server Activity Analysis Summary: Provides the total number of jobs, number of projects and the average daily usage duration per Intelligence Server. This report is prompted on time and presents the metrics as pie charts broken down by individual MicroStrategy clients.
  16. (Operations Analysis > Resource Utilization) 33.1 Scheduled Report Load on Intelligence Server: Provides a comprehensive analysis of scheduled jobs.
  17. (Operations Analysis > Resource Utilization) 33.2 Subscribed Report Load on Intelligence Server: Provides a comprehensive analysis of subscribed jobs through NCS.
  18. (Operations Analysis > Resource Utilization) 33.3.1 Web Access Trends: Provides the number of jobs run from the web, the total number of jobs run and the percentage of jobs run from the web over time. This report is prompted on time.
  19. (Operations Analysis > Resource Utilization) 33.3.2 Web and Non-Web Usage: Provides a comparison of the percentage of usage by web and non-web users. This report is prompted on time.
  20. (Operations Analysis > Resource Utilization) 33.3.3 Web Usage Statistics: Provides the number of users, the average number of jobs per user and the average elapsed report execution time per job for web users over time. This report is prompted on time.

Real-time:

  1. (Real Time Analysis) 101. Recently Completed Jobs: This prompted working set report provides details of recently completed report job executions.
  2. (Real Time Analysis) 102. Recent Sessions, Users: This working set report can be used to monitor recent user connection activity on the Intelligence Server.
  3. (Real Time Analysis) 103. Recently Completed Scheduled Jobs: This prompted report provides details of recently completed scheduled report job executions including information such as when the job completed and whether it was successful.

Inbox:

  1. (Operations Analysis > Inbox Message Analysis) 118. Inbox Message Action over Time: This Report provides a look at the Inbox Message Population and the number of actions performed on the set of Messages and how many of those actions resulted in errors. This Report is prompted on time.
  2. (Operations Analysis > Inbox Message Analysis) 119. Number of Messages by User over Time: This report provides a look at the user population using the Inbox Messages. This Reports looks at number of messages for each user along with the number of actions taken on these messages. This report is prompted on time.
  3. (Operations Analysis > Inbox Message Analysis) 120. Inbox Contributions to Job Counts: This report looks at the contribution of Inbox Message Jobs to the total Job count on the Intelligence Server. This report is prompted on time.
  4. (Operations Analysis > Inbox Message Analysis) 121. Top 10 Users of Inbox Messages by Project: This report Provides the Top 10 Users consuming the Inbox Message population by Project. This report is prompted on time.
  5. (Operations Analysis > Inbox Message Analysis) 122. Top 10 Reports in Inbox Messages by Project: This report provides a look at the top Reports in the Inbox Message population. This report is prompted on time.
  6. (Operations Analysis > Inbox Message Analysis) 123. Top 10 Documents in Inbox Messages by Project: This report provides a look at the top Documents in the Inbox Message population. This report is prompted on time.
  7. (Operations Analysis > Inbox Message Analysis) 124. Unread Inbox Messages: This report looks at the activity of Inbox Messages that have not been read. This report is prompted on time.
  8. (Operations Analysis > Inbox Message Analysis) 125. Inactive Inbox Messages: This report looks at the Inbox Messages that have not had any performed in a given amount of days. This report is prompted on a measuring metric and a number of days of inactivity.

Cube:

  1. (Performance Analysis > Cube Advisor) 45. DB Execution of Prompted Reports by Project: This report will show statistics for Prompted Report Jobs and what percentage of time is spent on the Database.
  2. (Performance Analysis > Cube Advisor) 46. Report Object Listings: This report details the Attribute and Metric associations with a particular Report. This report is prompted on either Report, or qualifying on a set of Report Processing Metrics.
  3. (Performance Analysis > Cube Advisor) 47. Projected Cube Execution Times of Prompted Reports by Project: This report projects the Execution times of Report Jobs if they were to hit an Intelligence Cube. This report is prompted on Time and Report or Qualifying on a Report Processing Metrics.
  4. (Performance Analysis > Cube Advisor) 48. Report Request Statistics per Project: Provides a look at Database Execution Statistics for Report Requests. This report is prompted on time and on Project. It may also be exported and used as input for the Cube Advisor.
  5. (Operations Analysis > Resource Utilization) 34. Intelligent Cube Usage Statistics: Provides the overall usage of an Intelligent Cube in memory. This report is prompted on time.

Cache:

  1. (Performance Analysis) 41. Cache Analysis: Provides a comprehensive analysis of caching on the system.
  2. (Performance Analysis) 46. Cache Analysis (End-to-End): Provides a breakdown of User Requests via MSTR Mobile based on which requests hit 1) Application Cache (usually from back button requests), 2) Device Cache, 3) Server Cache or 4) No Cache

Warehouse:

  1. Data Warehouse Optimization Advisor: This interactive dashboard is a data warehouse optimization wizard for the worst performing reports in a particular MicroStrategy project.
  2. (Performance Analysis) 43. Top 10 Database Tables: This report shows the top 10 most accessed database tables per project, and how many jobs those tables are accessed in.
  3. (Performance Analysis) 44. Warehouse Tables Accessed: Provides a count of the Warehouse tables and columns accessed in various SQL clauses.
  4. (Operations Analysis > Resource Utilization>Top Consumers) 43. Top 10 Database Tables: This report shows the top 10 most accessed database tables per project, and how many jobs those tables are accessed in.

Delivery:

  1. (Operations Analysis > Delivery Processing Analysis) 111. Weekly Subscription Activity: Provides a comprehensive weekly summary of Subscription activity.
  2. (Operations Analysis > Delivery Processing Analysis) 112. Subscription Statistics: Provides a look at Subscription Activity over a given time interval. This report is prompted on time.
  3. (Operations Analysis > Delivery Processing Analysis) 113. User Subscription Statistics: Provides information for users on subscription execution over a given time interval. This report is prompted on time.
  4. (Operations Analysis > Delivery Processing Analysis) 114. Top 10 Subscribed Documents: Provide insight into the Document contributors of the top 10 percent of Recipients, execution time, or number of Subscriptions over a time interval. This report is prompted on time and metrics for Subscription analysis.
  5. (Operations Analysis > Delivery Processing Analysis) 115. Top 10 Subscribed Reports: Provide insight into the Report contributors of the top 10 percent of Recipients, execution time, or number of Subscriptions over a time interval. This report is prompted on time and metrics for Subscription analysis.
  6. (Operations Analysis > Delivery Processing Analysis) 116. Top 10 Subscribed Contacts: Provide insight into the User contributors of the top 10 percent of Recipients, execution time, or number of Subscriptions over a time interval. This report is prompted on time and metrics for Subscription analysis.
  7. (Operations Analysis > Delivery Processing Analysis) 117. Top 10 Longest Executing Subscriptions: Provides a look at the top 10 percent of subscriptions that contribute to the execution times over a given time period. This report is prompted on time.

Data loader:

  1. Data Load History: Provides a historical look at the data loads that have been run in the past.

Document:

  1. Document Processing Analysis Dashboard: This interactive dashboard Measures Document Execution on Intelligence Servers and on Projects. It provides insight into how Document execution affects the BI System, and how each Document is requested and executed.

Report:

  1. (Operations Analysis > Resource Utilization > Top Consumers) 6. Top 10 Longest Executing Reports: Provides the number of jobs and the average elapsed report execution duration for the ten longest executing reports. This report is prompted on time.
  2. (Operations Analysis > Resource Utilization > Top Consumers) 62. Top 10 Reports: Provides the number of jobs, the average queue duration and the average elapsed report execution duration for the ten most often executed reports. This report is prompted on time.
  3. Report Processing Analysis Dashboard: This interactive dashboard Measures Report Execution on Intelligence Servers and on Projects. It provides insight into how Report execution affects the BI System, and how each Report is requested and executed.
  4. (Operations Analysis > Report Processing Analysis) 1. Weekly Summary - Activity Analysis: PROVIDES A COMPREHENSIVE WEEKLY SUMMARY OF PROJECT ACTIVITY.
  5. (Operations Analysis > Report Processing Analysis) 10. Document Analysis based on Wait Time (End-to-End): Provides a breakdown of Documents executed via Mobile along with the END-TO-END Wait time. This involves Intelligence Server Time, Device Rendering Time and Network Time.
  6. (Operations Analysis > Report Processing Analysis) 11. Document Analysis based on Request Type (End-to-End): Provides a breakdown of Documents executed via Mobile based on the type of request i.e. User Request, Report Queue Request, Application Recovery Request, Back Button Request etc.
  7. (Operations Analysis > Report Processing Analysis) 2. Report Execution Analysis Working Set: COMPREHENSIVE REPORT EXECUTION ANALYSIS
  8. (Operations Analysis > Report Processing Analysis) 3. Document Execution Analysis Working Set: Analysis of Document Executions
  9. (Operations Analysis > Report Processing Analysis) 4. Report Error Analysis: ERROR ANALYSIS FOR REPORT JOBS
  10. (Operations Analysis > Report Processing Analysis) 4.1 Report Job Time Out Analysis: Provides information about which and how many report executions have exceeded the execution timeout limit.
  11. (Operations Analysis > Report Processing Analysis) 4.2 Job Cancellation Trend: Provides the number of cancelled jobs and non-cancelled jobs over time. This report is prompted on time.
  12. (Operations Analysis > Report Processing Analysis) 4.3 Job Cancellation Breakdown: Provides details of report executions that were cancelled with and without SQL executions.
  13. (Operations Analysis > Report Processing Analysis) 5. DB Result Rows by Report: Provides the number of jobs, the number of database result rows and the average elapsed report execution duration per report and project. This report is prompted on time.
  14. (Operations Analysis > Report Processing Analysis) 5.1 Report Executions with no data returned: Details of report executions with no data
  15. (Operations Analysis > Report Processing Analysis) 5.2 Post-Report Execution Activity: Details of user activity after executing a particular report.
  16. (Operations Analysis > Report Processing Analysis) 6. Top 10 Longest Executing Reports: Provides the number of jobs and the average elapsed report execution duration for the ten longest executing reports. This report is prompted on time.
  17. (Operations Analysis > Report Processing Analysis) 7. Top 10 Longest Executing Documents: Provides the number of jobs and the average elapsed document execution duration for the ten longest executing documents. This report is prompted on time.
  18. (Operations Analysis > Report Processing Analysis) 8. Minute Level Job Concurrency: Provides a view of how many reports were executing on a particular Intelligence Server over a time interval in one day over a set of days. This report is prompted on Minute and on Day.
  19. (Operations Analysis > Report Processing Analysis) 9. Prompt Answer Time vs. Report Elapsed Time
  20. (Operations Analysis > Resource Utilization > Top Consumers) 91. Popular reports in a user's User Group: List top n (based on prompt value) reports in terms of usage (number of jobs) in a particular user's user group/s.

Project:

  1. Project Analysis Dashboard: This dashboard provides a comprehensive overview of usage and activity on your projects. Best viewed with default prompt answers (3 months or more of data).
  2. Project Analysis Interactive Dashboard: This Interactive Dashboard provides different views of the Project. It looks at overall project size, object storage patterns, usage of the project and its objects as well as growth patterns.

User:

  1. (Operations Analysis > Resource Utilization > Top Consumers) 80. Top n users: This report is used to determine the top n users based on any chosen criterion.
  2. User Analysis Dashboard: This Interactive Dashboard provides insights into how users are using the system with regards to Report and Document execution, and Session information.
  3. (Operations Analysis > Concurrency Analysis > User/Session Analysis) 10. Concurrency by Hour of Day: Provides number of active users and number of active sessions by hour of day. This report is prompted on time.
  4. (Operations Analysis > Concurrency Analysis > User/Session Analysis) 11. Daily Session Concurrency Analysis: Provides an analysis with various metrics on session concurrency over time. This report is prompted on time.
  5. (Operations Analysis > Concurrency Analysis > User/Session Analysis) 12. Session Duration Analysis: Provides an analysis with various metrics on user session duration over time. This report is prompted on time.
  6. (Operations Analysis > Concurrency Analysis > User/Session Analysis) 13. Daily User Connection Concurrency Analysis: Provides an analysis with various metrics on user connection concurrency over time. This report is prompted on time.
  7. (Operations Analysis > Concurrency Analysis > User/Session Analysis) 14. Minute Level User Concurrency During Peak Hours: Provides a minute level graph for the active users and sessions during the peak hours of the day. This report is prompted on time.
  8. (Operations Analysis > Concurrency Analysis > User/Session Analysis) 14.1 Top n Maximum User Concurrency Hours - report as filter: Provides a list of the top 3 hours in terms of maximum user concurrency paged by the Intelligence server, day and the connection source. This report is prompted on time.

Mobile:

  1. Mobile Usage and Adoption: This interactive dashboard measures the mobile usage and its contribution to the BI system. It gives insights into mobile interactive jobs, mobile subscriptions and most popular mobile reports and documents.

Other:

  1. (Performance Analysis) 47. Network Type Analysis (End-to-End): Provides a breakdown of the different Networks (wifi or WWAN) users were on while requested content.

What statistics do I want to determine from using Enterprise Manager?

  1. What is the usage characteristics? What time is the system most busy? What is the availability or what is the resource usage of the system during this time?
  2. Given a time period of the day, I want to see the usage break down by web versus schedule reports (one a pie chart), by project (another pie chart), by number of concurrent web users by project (another pie chart)
  3. What report is most frequently used / run?
  4. Which report is most subscribed?
  5. Which user is the most active? How often they access the reports?
  6. What are the user experience? How long does it take to run each report?
  7. Which user defined reports are most frequently executed? Should we make these reports available to all users?
  8. Find and delete unused objects to save resources. How to find un-used objects? We can specify a time frame and it will tell you which reports were not run during this time frame.
  9. Report on project growth trend
  10. Workload
  11. Concurrency (How many users are running MSTR at any moment)
  12. Peak time analysis
  13. Number of open sockets
  14. Load average
  15. CPU utilization
  16. Bandwidth utilization
  17. Packet drop
  18. Number of MicroStrategy users currently online
  19. Number of prompted reports recently run
  20. Number of scheduled reports recently run
  21. We need to monitor the availability of the SMTP server independently using IT360 or a separate monitoring system. Perhaps we also need to monitor other metrics (CPU, memory, number of messages in the queue) on the SMTP server as well.
  22. At some point in time, we will probably want to have some tool to determine if the user is still employed at the facility (has not been deactivated on the application side) and delete these users and their subscriptions.

What is the significance of the number in the report name?

Enterprise Manager report names are preceded by a number. The integer-numbered reports (such as 81. Activity by User) indicate that the report returns data on a high-level analysis area. The decimal-numbered reports (such as 81.1 Ad-hoc Job Activity by User or 81.2 DB Result Rows by User) indicate that that these reports provide more detail within the higher-level analysis area.

Do we need to add additional indexes to make the reports run faster?

Not really. Indexes are included for out-of-the-box reports on the Enterprise Manager fact tables. Check the indexes for the Enterprise Manager reports that you run most frequently or that take the longest to complete. If necessary, you should build additional indexes if you find some reports using tables that do not currently have an index.

Where can we find a list of facts, attributes, and metrics that are available as part of the Enterprise Manager project?

For a detailed list of all Enterprise Manager facts, attributes, and metrics, see the Enterprise Manager Data Dictionary in the Supplemental Reference for System Administration.

How can we create project documentation for Enterprise Manager?

The Project Documentation Wizard can provide detailed information about any objects in the Enterprise Manager project. For example, to find which metric to use for a specific purpose, you can generate and view the project documentation for the Enterprise Manager metrics. When you step through the Project Documentation Wizard, you specify the objects that you want information about. The Project Documentation Wizard records information about these objects as an HTML file. You can view and search this HTML file, or print it for quick reference later.

The Enterprise Manager project documentation is initially only available on the machine that has the Enterprise Manager project installed. To enable other users to view the project documentation, share the HTML files over your network. To create project documentation for Enterprise Manager:

  1. In Developer, log in to the Enterprise Manager project. You must log in with an account that has administrative privileges in this project.
  2. From the Tools menu, select Project Documentation. The Project Documentation Wizard opens.
  3. Step through the Project Documentation Wizard. Select the Enterprise Manager project, and the objects and information that you want to include in the project documentation. For instructions on how to use the wizard, click Help.
    1. To include information about metrics or reports, select Application objects. To include information about attributes, select Schema objects.
  4. On the last page of the wizard, click Finish. The project documentation HTML files are generated in the location you specify in the wizard.

Can we modify the existing reports, metrics, and attributes?

Not really. You can, but it is not recommended. MicroStrategy recommends that we make a copy and modify the copy.

How can we make sure that the links in the reports work correctly?

We have to make copy of the original dashboard and edit the dashboards and change all occurrences of Main.aspx in the links to mstrWeb.

What is the purpose of the Data Warehouse Optimization Advisor dashboard?

This dashboard provides information that can guide you when optimizing the performance of your data warehouse. The user specifies the time frame for analysis, the number of database tables to consider for optimization, and the percentage of jobs to consider in the optimization calculations. The top half of the dashboard summarizes the current database usage. This summary includes:

  • An executive summary of the database usage over the specified time period, including the number of report requests and report result rows, the average execution time for each request, and the total execution time.
  • A gauge graph showing the percent of total database load that is taken up by the specified percentage of reports.
  • A grid showing which reports consume the most database resources. This grid can be sorted by number of report requests, number of result rows, or execution time.

The bottom half of the dashboard contains a list of the database tables being considered for optimization. Clicking on a table brings up a list of optimizations and their potential effectiveness. These optimizations include aggregate table grouping and different types of secondary indexes.

What is the purpose of the Document Processing Analysis Dashboard?

This dashboard provides an overview of document usage and performance in your projects, including average wait times and number of execution errors encountered.

The Processing Summary section provides a general picture of document activity for a given project and Intelligence Server. It includes:

  1. Line graphs showing key performance indicators for document execution, including average wait times, execution times, and number of errors encountered.
  2. An area graph showing the number of jobs and execution errors over time.
  3. An area graph showing average wait, execution, and queue times for executed documents.

The Document Details section provides in-depth information on specific documents within a given project. Select a document from the drop-down list to view:

  1. A bubble graph of popular documents, with the number of users and job requests for each document.
  2. General information about the selected document, including the owner, description, and date the document was last modified.
  3. An area graph showing the average wait time, execution time, and queue time encountered when executing the document.

What is the purpose of the Project Analysis Dashboard?

This dashboard provides a comprehensive overview of usage and activity on your projects, over the time frame that you specify. The top portion of the dashboard contains a general analysis of the system. It includes:

  1. Pie charts showing the project usage by total time spent executing jobs, total number of jobs executed, and number of users connected.
  2. An overview of system usage for each project, including cache hits, number of jobs, and other metrics.

On the dashboard, below the general analysis section is a separate section for each project. These sections contain a detailed analysis of the project, including:

  1. A line graph showing the weekly growth trend for the numbers of reports and other objects in the project.
  2. A line graph showing the weekly usage trend, in terms of number of users and number of user requests.
  3. A line graph showing the weekly project performance trend, in terms of job execution time and number of jobs.
  4. A graph showing the load distribution (ad-hoc versus scheduled jobs).

What is the purpose of the Project Analysis Interactive Dashboard?

This dashboard provides usage information for a given project, including object storage, patterns in project growth, and a list of unused application objects for cleanup. The Overview section provides a general view of project performance and project size. It includes:

  1. Line graphs of key performance indicators for the project over time, including the number of users, sessions, and document jobs.
  2. Bar graphs of the number of application and schema objects in the project, broken down by object type. These include reports, documents, attributes, and hierarchies.

The Growth section provides details about new application objects added to the project. It includes:

  1. A graph of the number of application objects that have been added to the project by week, broken down by object type.
  2. A funnel graph of new application objects added to the project, organized by the owner of the object.

The Usage section provides a picture of the most frequently used objects in the project. It includes:

  1. Heat maps of the top ten frequently used reports and documents in the project.
  2. Lists of the top ten attributes, metrics, and filters in the project.

The Clean Up section provides a view of unused objects in the project, including:

  1. A list of unused reports, documents, attributes, and other application objects for the project.
  2. Links to generate scripts for deleting unused application objects from the metadata.

What is the purpose of the Real-Time Server Usage Dashboard?

This dashboard provides an overview of recent system activity. The user specifies the earliest date for which data is reported. The dashboard includes:

  1. Critical system metrics such as average job duration and total jobs processed for a given server machine.
  2. Pie charts indicating the recent job distribution by project, and execution status such as Completed, Error, and so on.
  3. A line graph showing system throughput and response time for a given server machine.
  4. A grid indicating the current status of scheduled jobs on the server machine, on a per project basis.
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License