KB442094: Platform Analytics FAQ

Senior Principal Consultant • MicroStrategy

Get all your questions answered about MicroStrategy's Platform Analytics.

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

I. General Questions

1. What is Platform Analytics?

Platform Analytics is the new monitoring tool in Strategy 11.0. It collects real-time data (also known as telemetry) which is generated by different components of the Strategy platform like the Intelligence Server. Then it presents this data to the administrators, developers, and analysts to help them optimize the performance of Strategy, offer personalized recommendations to their users, improve their analytics applications, secure their data, and more.

2. Why should I use Platform Analytics?

The reasons why customers should use Platform Analytics can be summarized as follows:

Platform Analytics captures more data from the Strategy platform than Enterprise Manager, and unlike Enterprise Manager, Platform Analytics captures this data in real-time.
Platform Analytics is more stable than Enterprise Manager, thanks to a modern and scalable architecture that has no data load to schedule or maintain.
Platform Analytics is easier to use than Enterprise Manager, thanks to a user-centric approach and new workflows that show data directly in Workstation.
Platform Analytics is at the center of our innovation efforts to make the Strategy a smarter data-driven platform, so there are many exciting features to come.

3. Where can I see the out of the box dossiers currently delivered with Platform Analytics?

Platform Analytics ships with a Strategy project just as Enterprise Manager does. Customers can find the Platform Analytics out-of-the-box dossiers inside that project (called Platform Analytics), along with the self-service project schema that they can use to create ad-hoc content.

II. Platform Analytics versus Enterprise Manager

1. Is Platform Analytics a replacement for Enterprise Manager?

Platform Analytics and Enterprise Manager are the 2 fully supported monitoring tools in Strategy 11.0. So technically speaking, Platform Analytics does not replace Enterprise Manager because both tools are available for customers to use.
Having said that, we do encourage our customers to use Platform Analytics to take advantage of the improvements in performance, scalability, and usability that it delivers over Enterprise Manager.

2. What are the benefits of Platform Analytics over Enterprise Manager?

Both Platform Analytics and Enterprise Manager are monitoring tools that capture the telemetry generated by the Strategy platform. However, Platform Analytics is a new tool built with a user-centric approach on top of the latest technology, thus it offers many advantages over its predecessor. Some of the Platform Analytics benefits are:

Captures telemetry in real-time.
Has no data load to schedule or maintain.
Has a smaller footprint on the I-Server than Enterprise Manager.
Collects telemetry from more areas of Strategy.
Uses a unified data model that combines telemetry from Strategy and Usher.
Exposes telemetry through other Strategy products like Workstation.
Includes a set of powerful and highly curated dossiers.
Allows users who are not administrators to see the telemetry they care about.
Uses user-friendly naming conventions.

3. What will I lose if I switch over to Platform Analytics?

Platform Analytics and Enterprise Manager are different monitoring tools with separate components, including separate data warehouses. Therefore, customers switching to Platform Analytics will not lose anything because they will continue to have access to their historical data, reports, and dashboards through the Enterprise Manager project.

4. I have a lot of custom reports currently built into Enterprise Manager. Can I migrate those into Platform Analytics?

Customers can recreate their Enterprise Manager content using the Platform Analytics project schema and the Platform Analytics data import cube. However, it is not possible to migrate Enterprise Manager reports and dossiers to Platform Analytics. The main reason for this limitation is that Platform Analytics uses a completely different schema model that is not compatible with the Enterprise Manager schema.

5. Can I migrate historical data from Enterprise Manager to Platform Analytics?

Historical data from Enterprise Manager is not compatible with the new Platform Analytics data model, therefore it cannot be migrated to Platform Analytics. However, customers that upgrade to Strategy 11.0 will not lose their historical data as it will remain available in their Enterprise Manager warehouse and Enterprise Manager project. Furthermore, with Strategy 11.0 customers can choose to continue to use Enterprise Manager to monitor their Strategy environments or even use Platform Analytics and Enterprise Manager at the same time.

6. How to upgrade between Enterprise Manager to Platform Analytics?

Platform Analytics is a completely new product introduced in Strategy 11.0. It delivers a streamlined data model, simpler schema and real-time monitoring. As such, the upgrade between Enterprise Manager and Platform Analytics is not supported. Customers wishing to use Platform Analytics in 11.0 can do so by running the Strategy installer and selecting the Platform Analytics components.

7. Are all the use cases in Enterprise Manager covered by Platform Analytics?

In Strategy 11.0, the two Enterprise Manager use cases which are not covered in Platform Analytics are Performance Counter telemetry and Strategy iOS Mobile Client telemetry. All other Enterprise Manager use cases are covered by Platform Analytics.

8. Is the data model and schema the same in Platform Analytics as it is Enterprise Manager?

Platform Analytics introduced a redesigned data model that allows it to use approximately 25% less space in the data warehouse than Enterprise Manager to capture the same level of telemetry. As a result, the data model and project schema of Platform Analytics are not compatible with the data model and project schema from Enterprise Manager.

9. What is the impact of having both Enterprise Manager and Platform Analytics enabled?

There is no functional impact to having both Enterprise Manager and Platform Analytics enabled on the same environment. Both tools can be turned on and controlled independently from each other. If Platform Analytics is enabled, Enterprise Manager can be disabled and vice versa. Furthermore, it is possible to enable advanced statistics on Enterprise Manager and basic telemetry on Platform Analytics, and vice versa.
Having said so, enabling both Enterprise Manager and Platform Analytics has a cost associated with machine resources. Because the Intelligence Server is the data source for both products, the telemetry will be redundantly stored in the two separate warehouses for both products.

III. Platform Analytics Supported Installations and Configurations

1. How do I install, setup and configure PA?

For Strategy 2020, install and configure Platform Analytics using the following guide: MicroStrategy Platform Analytics 2020 Help.
For Strategy 2021,use the following guide: MicroStrategy Platform Analytics 2021 Help.

2. What operating systems does Platform Analytics support?

Platform Analytics is certified on all Strategy supported platforms: Linux, Windows and Strategy on AWS.

3. What databases are supported by Platform Analytics?

In Strategy 2020, both MySQL and PostgreSQL are supported as a Platform Analytics warehouse. A new component, Repository, is installed by selecting the Platform Analytics option in the Strategy Installation Wizard. The underlying database for Repository is PostgreSQL. If you upgrade from an earlier version of Platform Analytics to 2020, you can choose to use MySQL as the repository or to migrate your existing data from MySQL to PostgreSQL. For more information, see Migrate Data from a MySQL Database to a PostgreSQL Database.
In Strategy 2019, the only database supported for the Platform Analytics warehouse is MySQL (versions 5.6, 5.7 and 8.0). However, MySQL 8.0 is only certified with a database user who was created with "Legacy Authentication Method." Platform Analytics does not support the option "Strong Password Encryption for Authentication (SHA256 mode). The metadata of the Platform Analytics project can be hosted on any of the Strategy supported/certified metadata databases.

4. Can I use my existing database, or do I need to use the database included with the Strategy installation?

In Strategy 2020, a new component called Repository is installed by selecting the Platform Analytics option in the Strategy Installation Wizard. The underlying database for Repository is PostgreSQL. It's recommended to use the Repository Strategy installs as everything is already set up and ready to use.
To use an existing PostgreSQL database you already have for Platform Analytics, see How to Configure Remote PostgreSQL with Platform Analytics.
If you are using Strategy 2019, it depends on the installation method. You can either choose to have Strategy download MySQL and create the Platform Analytics warehouse as part of the installation, or add Platform Analytics to your existing MySQL Database. For installing Platform Analytics 2019 on Linux, downloading MySQL prior to installation is a pre-requisite.
The below chart explains which methods are available for each installation wizard:

conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X	conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X	conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X
conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X	conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X	conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X
conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X	conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X	conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X
conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X	conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X	conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X
conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X	conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X	conflict rule of Content GroupMD - recipientsPackage - recipientsresult - recipientsMD - contentPackage - contentresult - contentuse existingA, BB, CA, B, CA, BB, CA, B, C(force) replaceA, BB, CB, CA, BB, CB, C(force) keep bothA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, Bkeep both + same versionA, BB, Cno new (existing Content Group) A, B, CA, BB, Cno new (existing Content Group) A, B, Cuse existing + same versionA, BB, CA, B, CA, BB, CA, B, Creplace + same versionA, BB, CA, B, CA, BB, CA, B, Cforce replace + same verA, BB, CB, CA, BB, CB, Cforce keepboth + same verA, BB, C(new Content Group) B, C (existing Content Group) A, BA, BB, C(new Content Group) B, C (existing Content Group) A, BInternal IDImpactCommunity Article NameData Engine VersionStrategy VersionDE64937SQL, DataKB440791: Security Filter is not applied to Report when linked to a nested user group in MicroStrategy 10.4.3 and MicroStrategy 10.7 and lowerN/A2019F5749SQLKB438401: Security Fix in 10.5: Secure Freeform SQL report’s text prompt answer(s) using prepared statementsN/A2019DE39508CSI, DataKB442145: Security filters on indirectly related attributes don't apply when using data blendingN/A2019DE100668CSI, DataKB483225: Applying a security filter to a derived attribute may cause the Intelligence Server to crash .N/A2019DE81637SQLKB483228: A Metric Limit Filter set on the Dataset does not work and disables other filters if there is a security filter on the user .N/A2019DE89763Data, SQLKB483232: Security Filter is not applied in Connect Live mode20192019DE162773Data, CSIKB484104: Data leak caused by conditional metricsN/A2019 Update 6DE160248Data, CSIKB484157: When a security filter applies to one of the metrics in a derived metric's expression, it is ignoredN/A2019 Update 6DE168304Data, CSIKB484380: Security filter is not applied, leading to data leakN/A2019 Update 7DE161522Data, CSIKB484237: A security fix addressed in MicroStrategy 2019 U7, MicroStrategy 2020 Update 2 and MicroStrategy 2021N/A2019 Update 7 Download MySQLUse Existing MySQLStrategy on AWSX (Amazon RDS) Windows Express InstallationX Windows Custom InstallationXXWindows Silent InstallationXXLinux Installation X

5. Is it possible to use Platform Analytics without Strategy Messaging Services?
No, Platform Analytics is built on top of a modern and scalable architecture which utilizes Strategy Messaging Services as a core component. By default, when Platform Analytics is installed, a single node of Strategy Messaging Services is included with the installation. For production environments, it is recommended to use a cluster of 3 or more Messaging Services nodes for data redundancy.

6. Can I disable the Intelligence Server from logging telemetry to Platform Analytics?

Yes, there are 2 options that you can choose from:

Stop the Intelligence Server from sending telemetry to Platform Analytics.
Stop the Intelligence Server from sending telemetry from individual projects to Platform Analytics.

The following guide can be used as a reference for both commands, Enable Statistics from Command Manager.

7. Can I determine where the telemetry originated from when I have multiple environments logging to a single Platform Analytics warehouse?

Yes, all the telemetry logs generated by the Intelligence Server Producer contain the metadata_repository_id and repository_connection_string. Using these, Platform Analytics can differentiate logs which are sent by multiple Intelligence Server(s) clusters to a single Platform Analytics warehouse. Furthermore, the telemetry logs also contain the Intelligence server Machine Host/Port for tracking the Intelligence Server node which was used during the action which generated the log (i.e. execution of a report, republishing a cube, etc.).
For more details about this configuration see, Monitor Metadata Repositories Across Multiple Environments

8. Does Platform Analytics use any scheduled data loads to transform the telemetry logs?

No, Platform Analytics does not use any scheduled data loads to process and transform the Intelligence Server telemetry logs. After installing and configuring Platform Analytics, the Intelligence Server will send telemetry logs to the Strategy Messaging Services layer in near real-time. The Platform Analytics Consumer will process and store these telemetry logs into the Platform Analytics Warehouse through constant streaming.
Besides this constant stream of data from the Intelligence Server, there is a small number of operations which are best handled in an hourly or daily fashion rather than in near real-time. These include operations for repopulating time hierarchy relate tables, calculating daily fact table aggregation or simple clean-up operations. You do not need to configure these procedures after installing Platform Analytics, as it is done by default. However, if needed the schedule for the daily procedure can be changed, but the hourly procedure is triggered by the Platform Analytics consumer and its schedule is not intended to be modified.

Learning Resources

Interested in learning more about Platform Analytics or new features? Visit the Learning Center on Community!
Feel free to visit our Documentation pages for more on Platform Analytics.

Comment

0 comments

Details

Knowledge Article

Published:

October 12, 2018

Last Updated:

March 21, 2024