Uses of Interface
org.camunda.bpm.engine.telemetry.TelemetryData
Package
Description
Public API of the Camunda Platform engine.
Typical usage of the API starts by the creation of a
Through the services obtained from such a
Typical usage of the API starts by the creation of a
ProcessEngineConfiguration
(typically based on a configuration file), from which a ProcessEngine
can be obtained.Through the services obtained from such a
ProcessEngine
, BPM and workflow operation
can be executed:RepositoryService
:
Manages Deployment
sRuntimeService
:
For starting and searching ProcessInstance
sTaskService
:
Exposes operations to manage human (standalone) Task
s,
such as claiming, completing and assigning tasksIdentityService
:
Used for managing User
s,
Group
s and the relations between themManagementService
:
Exposes engine admin and maintenance operations,
which have no relation to the runtime execution of business processesHistoryService
:
Exposes information about ongoing and past process instances.FormService
:
Access to form data and rendered forms for starting new process instances and completing tasks.API implementation classes, which shouldn't directly be used by end-users.
-
Uses of TelemetryData in org.camunda.bpm.engine
Modifier and TypeMethodDescriptionManagementService.getTelemetryData()
This method returns the current state of the collected telemetry data. -
Uses of TelemetryData in org.camunda.bpm.engine.impl
-
Uses of TelemetryData in org.camunda.bpm.engine.impl.telemetry
Modifier and TypeMethodDescriptionvoid
TelemetryLogger.sendingTelemetryDataFails
(TelemetryData productData) -
Uses of TelemetryData in org.camunda.bpm.engine.impl.telemetry.dto
-
Uses of TelemetryData in org.camunda.bpm.engine.rest.dto.telemetry
Modifier and TypeMethodDescriptionstatic TelemetryDataDto
TelemetryDataDto.fromEngineDto
(TelemetryData other)