EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

Platform Analytics Homepage


Jing (Sally) Cheng

Senior Principal Consultant • MicroStrategy


Platform Analytics is our next-generation monitoring tool that captures data in real-time across the platform.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Welcome to Platform Analytics!

The vision of Strategy is Intelligence Everywhere. Our analytics and mobility platform transforms data into actionable insights that help people make better business decisions. By the same token, our platform is also the source of valuable data. Every time that a user does something in Strategy, like running a dossier, publishing a cube, or creating a subscription, the Strategy platform generates data (also known as telemetry) about that event. And because we are an analytics company, we take advantage of this wealth of information to make the Strategy platform more intelligent.
 
That is why with Strategy 11.0 we are introducing a new monitoring tool called Platform Analytics (PA). Platform Analytics captures telemetry from the Strategy platform in real-time, and then it presents this data to the administrators, developers, and analysts to help them optimize the performance of their Strategy system, offer personalized recommendations to their business users, improve their analytics apps, secure their data, and more.
 

Telemetry for everyone

One key principle behind Platform Analytics is the democratization of telemetry. Instead of storing telemetry in a warehouse and using it to create administrative reports only, Platform Analytics captures telemetry and spreads it to other parts of our platform. This makes it easier for more users to find the telemetry and gain insights while using other Strategy products, without having to rely on administrative reports that those users may not understand, have access to, or even know that exist.
 
Let’s look at one example. Laura is a developer who created the ‘Team Capacity and Load’ dossier a few days ago and wishes to know how many people have run this dossier and how fast it runs on average. Thanks to Platform Analytics, all she needs to do is right-click on her dossier in Workstation and go to the Activity tab where she will find the answer to this and other key questions. Quick and easy!
 

ka0PW0000001JYXYA2_0EM44000000R2nz.png

Embedded Dossier Telemetry in Workstation
 
If Laura wants to get more details about the adoption and usage of her dossier, she can go to the out-of-the-box Platform Analytics project and run one of the default Platform Analytics dossiers included there. These dossiers provide a lot more granularity about the telemetry generated by our platform. Alternatively, Laura can create a dossier using the self-service schema (attributes and metrics) which is included out-of-the-box with the Platform Analytics project.
 

Thousands of data points in real-time

Platform Analytics captures more data from the Strategy platform than ever before. We are literally talking about thousands of events and data points from all the key areas of the platform. This data is captured in real-time and can be accessed by running the default Platform Analytics dossiers, creating ad-hoc dossiers using the Platform Analytics schema, and using the telemetry embedded in Workstation.
 
The list below provides a few examples of the type of telemetry captured by Platform Analytics:

  • Environment and system data. For example the CPU type, CPU speed, memory, and operating system of an I-Server; the Strategy services running on an I-Server and the version of those services; the metadatas connected to a Strategy environment; etc.
  • Project data. For example the schema, application, and managed objects that live inside a Strategy project; the number of users connecting to each project; the sources where these connections originated from; the load on each project; etc.
  • User activity. For example the most active Strategy users; the time that they have spent in the system; the activities they have performed in the system; the dossiers that they have run; the errors that they have faced; etc.
  • Object usage. For example the most popular dossiers/reports/documents in the system; the objects that take the longest to run; the objects that haven’t been used; the average run time for an object; the number of users running an object; etc.
  • Subscription data. For example the content that users subscribe the most to; the users with the most amount of subscriptions; the days and times when most subscriptions are sent; the subscriptions that haven’t been used; etc.
  • Cube and caches data. For example the total size of all cubes both in memory and in disk; the originating source of a cube; the objects that depend on a cube; the historical hit count of a cube; the time that it takes to publish a cube; etc.
  • Error occurrence. For example the most common errors in the system; the content with the highest error rates; the users with the highest error rates; the rate of errors by source; the trends of error rates; etc.

 

Centralized monitoring of multiple environments

In order to capture all of this data Platform Analytics uses a modern messaging streaming architecture that provides 3 key benefits: scalability, performance, and redundancy. This architecture allows a single instance of Platform Analytics to monitor multiple Strategy environments simultaneously and in real-time.
Let’s look at another example. Acme Co. has a Strategy implementation with 4 environments: Development, QA, Mirror, and Production. John is the Strategy administrator in Acme. Previously, Acme had to monitor each Strategy environment individually, and John had to create the same set of monitoring reports for each environment. However, now that they are using Platform Analytics, Acme can monitor its 4 environments using a single instance of Platform Analytics. To access data from all the environments John runs the Platform Analytics out-of-the-box dossiers, and then he uses a simple filter to select the specific environment (i.e. Intelligent Server cluster connecting to a metadata) that he wishes to analyze.
 

ka0PW0000001JYXYA2_0EM44000000R2pM.png

 
 

There is more to come

With Platform Analytics, Strategy customers can optimize the performance of their Strategy implementations, improve their analytics apps, troubleshoot issues, and ensure that all their users get the best possible analytics experience. And this is just the beginning. Come back to see all the functionality that we will be adding to this powerful tool in the next months.
 

Learning Resources

Interested in learning more about Platform Analytics? Visit the Learning Center on Community!
Or feel free to go to our Documentation pages for product information.
 


Comment

0 comments

Details

Knowledge Article

Published:

August 28, 2018

Last Updated:

March 21, 2024