Symptoms
When trying to create a new analytics search, the dashboard or UI turns white. The analytics license is valid.
This issue is seen when analytics is enabled for the first time, and there is some configuration issue due to which the desired analytics data is not seen.
Diagnosis
When the analytics-agent.log is checked, the following message appears:
analytics-agent / Connection to [http://<events-service-host>:<events-service-port>/v1]: (unhealthy) The supplied auth information is incorrect or not authorized.
When the nside server.log is checked, the following message appears:
com.singularity.ee.controller.ui.services.analytics.AAnalyticsUiService|_ThreadID=83;_ThreadName=Thread-5;|Could not find account [customer1_df108b04-0781-4224-8879-861492ce1f50] via lookup
The Events Service logs report as healthy.
Please collect related components logs as mentioned above, i.e. events service, controller server.log and analytics-agent.log.
Once the logs are collected, try to isolate the issue. In this particular case, the issue was caused by the wrong auth information being used between components.
Solution
To resolve this issue, please verify the auth info being passed by following these steps:
- As with analytics, it's recommended to use the standalone events-service, so make sure that the following key values match:
- Verify that the http.event.accessKey is correct from the License page account access key value.
- In the analytics-agent.properties file, modify the following property to the value:
http.event.endpoint=http://<events-service-host>:<events-service-port>/v1
ad.accountmanager.key.controller inside events-service-api-store.properties.
appdynamics.analytics.server.store.key inside controller administrator console(admin.jsp).
- Verify that the value for appdynamics.analytics.server.store.url inside the controller administrator console points to the exact events-service:
http://<events-service-host>:<events-service-port>
Once the above configuration is modified, restart the events-service and analytics agent to bring the aforementioned config changes into effect.
