Details
-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Description
Context:
See parent ticket. We need DTOs to represent the data that are to be included in telemetry with the first iteration, so we can send them to the relevant telemetry endpoint. The required information is the following:
To be implemented with this ticket:
- Optimize version
- Edition (required by ET, always "enterprise")
- Unique Installation ID
- Elasticsearch version
To be implemented with follow up tickets:
- Optimize License key/customer name (decision to be made whether this should be the entire license key or just the customer name, or both)
- Connected Engines Installation IDs (requires engine endpoint to retrieve installation ID)
To be used in sample request:
{ "installation": "8343cc7a-8ad1-42d4-97d2-43452c0bdfa3" (must be a valid UUID)
"product": {
"name": "Camunda Optimize",
"version": "3.2.0",
"edition": "enterprise",
"internals": {
"license key": "someLicenseKey", // not decided yet
"database":{
"vendor": "elasticsearch", (optional)
"version": "7.6.1"
},
"engineInstallationIds": ["engineInstallationId1", "engineInstallationId2",..]
}
}
}
AT:
- Telemetry DTOs are added to Optimize
- A helper is added to build the telemetry data when required