ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

[UVMS] How to know if the Telemetry is correctly configured and being sent ?

book

Article ID: 198950

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

After enabling the Telemetry according to the Doc, there is a way to make sure the Telemetry data is being generated and sent as expected.

Environment

Release : 6.10

Component : DOLLAR UNIVERSE

Resolution

The telemetry details can be visible in the logs when the DEBUG level has been set through the UVMS Settings (Logging/Main log level).

Once done, you will see the messages below in the UVMS log (uvserver.log) :

- Data being generated :

| 2020-09-08 14:54:28 |DEBUG| TelemetryUpdateTimer | com.orsyp.central.telemetry.BroadcomSegment | Identify message map: [{product_sku=XXXXXX, domain_name=YYYY, product_version=6.0.0, instance_id=90be0484-e3a8-41erzrezrzra1e0a6b0b4c, pla_agreement=1, site_id=XXXXXX, sku_description=Dollar Universe Workload Automation Reporter, chargeback_id=90be0484-zrerz-41db-ab14-9a1e0a6b0b4c}]. 
| 2020-09-08 14:54:28 |DEBUG| TelemetryUpdateTimer | com.orsyp.central.telemetry.BroadcomSegment | Enqueued Identify

 

- Data being sent :

 2020-09-08 14:54:29 |DEBUG| Analytics | com.orsyp.central.telemetry.BroadcomSegment$BroadcomSegmentLog | Uploaded batch %s. 
| 2020-09-08 14:54:29 |DEBUG| Analytics | com.orsyp.central.telemetry.BroadcomSegment$BroadcomSegmentCallback | Successful message [IdentifyMessage{type=identify, messageId=rezrzerzrzer-8e89-4393-a044-8108d3d3d0cc, timestamp=Tue Sep 15 14:54:28 CEST 2020, context=null, anonymousId=null, userId=XXXXXX, integrations={}, traits={product_sku=XXXXXXXXX, domain_name=YYYY, product_version=6.0.0, instance_id=90be0484-e3a8-41db-ab14-rzrzrz, pla_agreement=1, site_id=XXXXXX, sku_description=Dollar Universe Workload Automation Reporter, chargeback_id=rezrzrzrez-e3a8-41db-ab14-9a1e0a6b0b4c}}]. 

 

Please note that DEBUG mode will drastically increase the log size. It needs to be removed afterward.