-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
AC:
- There is a Java API to retrieve information about the platform. In the first iteration, the result contains telemetry information.
- The telemetry enabled flag is not included, because there is a dedicated ManagementService API endpoint to retrieve that
- The commands and metrics are counted at all times (irrespective if telemetry is activated), so that calling the new API endpoint always returns this data
- The data is discarded when telemetry is activated (i.e. we never report data to Camunda that was collected before telemetry sending was activated)
- The discarding works in a cluster setup, i.e. when the reporter detects via the database that telemetry was activated in the meantime, then it discards previously recorded commands and metrics
Example for telemetry content (serialized, API returns Java object):
{
"installation": "8343cc7a-8ad1-42d4-97d2-43452c0bdfa3",
"product": {
"name": "Camunda BPM Runtime",
"version": "7.14.0",
"edition": "enterprise",
"internals": {
"database": {
"vendor": "h2",
"version": "1.4.190 (2015-10-11)"
},
"application-server": {
"vendor": "Wildfly",
"version": "WildFly Full 19.0.0.Final (WildFly Core 11.0.0.Final) - 2.0.30.Final"
},
"jdk": {
"version": "14.0.2",
"vendor": "Oracle Corporation"
},
"commands": {
"StartProcessInstanceCmd": {"count": 40},
"FetchExternalTasksCmd": {"count": 100}
},
"metrics": {
"root-process-instance-start": { "count": 936 },
"activity-instance-start": { "count": 6125 },
"executed-decision-instances": { "count": 140 },
"executed-decision-elements": { "count": 732 }
},
"camunda-integration": [
"spring-boot-starter",
"camunda-bpm-run"
],
"license-key": {
"customer": "customer name",
"type": "UNIFIED",
"valid-until": "2022-09-30",
"unlimited": false,
"features": {
"camundaBPM": "true"
},
"raw": "customer=customer name;expiryDate=2022-09-30;camundaBPM=true;optimize=false;cawemo=false"
},
"webapps": [
"cockpit",
"admin"
]
}
}
}