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
  3. Topics

KB486838: Usage Panel is Not Available in Bots, Dashboards, or Telemetry APIs Return 404 Errors

Kyle Kelley

Product Owner, Senior • MicroStrategy

MicroStrategy ONE (June 2024) introduces a Usage panel when using MicroStrategy AI. If the Usage panel is not available or telemetry produces 404 errors, see the following article for solutions.

Symptoms


See the following possible symptoms:

  • Usage panel does not display in Bots or dashboards
ka0PW0000002ULNYA2_0EMPW000007hg1Z.jpeg
  • APIs under 
    /api/telemetry/
    return 404 errors
ka0PW0000002ULNYA2_0EMPW000007hGjq.jpeg
  • Workstation Topology and Service scripts display Platform Analytics as stopped even though it is running

Problem


The Telemetry Service cannot be managed correctly by Workstation Topology or the Service scripts (Service Strategy status or the direct scripts in 

/etc/init.d
). When the service starts or checks status using these two workflows, the service will never be started in the Telemetry Service mode, and will return an incorrect Stopped status, even if the telemetry service is running.

Solution

  1. Utilize the cloud console to manage the service (Store under the Telemetry section).
  2. Utilize the Platform Analytics specific script to manage the service: 
    /opt/mstr/PlatformAnalytics/bin/platform-analytics-consumer.sh start/stop/status.


To check that the telemetry service was started in the correct mode and is running:

  • Check 
    platform-analytics-consumer_yyyy-mm-dd.log
    and see the Spring Boot logo, as shown below.
ka0PW0000002ULNYA2_0EMPW000007hf2I.jpeg
  • Check 
    platform-analytics-consumer.log
    for the following line: 
    2024-06-18 12:58:03,061 INFO TelemetryServiceApplication:49 - Starting Telemetry Service Application

Context


Strategy ONE (June 2024) introduces a new mode of the Platform Analytics consumer, now known as the Telemetry Service, which exposes a set of APIs to allow new workflows to directly interact with the 

platform_analytics_wh
without going through the Platform Analytics project. The first set of APIs is focused on Auto adoption metric. In Strategy ONE (June 2024), the APIs power a new Usage panel in Bots and Dashboards that have Strategy AI enabled. You can use this update to view aggregated statistics on the usage of your Strategy AI content and download CSVs with more detailed telemetry.

Additional Troubleshooting

  1. Ensure that the 
    configOverride.properties
    on each library node has the following configuration and was restarted after the configuration was in place:
    1. service.telemetry.baseURL="https://<primary node hostname>:<default port 8222>
    2. features.telemetryService.supported = true
  2. Ensure that the 
    PAConsumerConfig.yaml
    has the following configuration:
    1. telemetryService:

      port: 8222

      identityToken:

      secretKey:

      "+b34hO/BwSNrLD764j/r+S+twXyl4Qbe/6K+LB6GRnYtJD2CrtbWL0ykxw0EC5yzBx/CzJZOFRL2zjXJmC0S4tIV3DLLjxisMnQoZf3hihXHCxKYHK8/1IaTHWgSB7MsNUk2cd7/hzs=,iQGNGpLBjTYfjRy8"

    2. Where the 
      secretKey
      matches the 
      identityToken.secretKey
      from the library 
      configOverride.properties
      file after it has been encrypted by the 
      platform-analytics-encryptor.sh
Comment

0 comments

Details

Knowledge Article

Published:

June 20, 2024

Last Updated:

June 21, 2024