Closed yanavasileva closed 1 day ago
To remove, no longer used: org.camunda.bpm.engine.impl.telemetry.dto.InternalsImpl.telemetryEnabled
https://github.com/camunda/camunda-bpm-platform/blob/58a68573bae5053b88a0a3b89c82dca7a459a2a5/engine/src/main/java/org/camunda/bpm/engine/impl/telemetry/dto/InternalsImpl.java#L55
It's not exposed in public Java API and not available in REST API at all.
❓ Do we need migration test?
telemetry.lock
from the sql scripts?
Database schema backwards compatibility
doesn't mention that scenario.❓ If telemetry reporter is removed, do we need special handling for diagnostics endpoint?
Existing database will have the telemetry.lock
so we don't need to keep it.
Docs PR is still work in progress.
https://github.com/camunda/camunda-bpm-platform/pull/4544 is ready for merge.
Acceptance Criteria (Required on creation)
ProcessEngineConfigurationImpl
- Remove configuration properties and related code that are not needed anymore. won't start up after an updateBootstrapEngineCommand
- don't add telemetry lock and propertyTelemetryReporter
andTelemetrySendingTask
IsTelemetryEnabledCmd
TelemetryConfigureCmd
connect
dependency - remove it and check if shading is working as expectedtelemetryHttpConnector
(sending HTTP requests for telemetry) and the aconnect
dependencywiremock
- remove where not needed anymoreTelemetryReporter
andTelemetrySendingTask
TimerTask
as it is not needed anymoreHints
Links
Breakdown