Class InternalsImpl
java.lang.Object
org.camunda.bpm.engine.impl.telemetry.dto.InternalsImpl
- All Implemented Interfaces:
Internals
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected ApplicationServerImplprotected DatabaseImplprotected Dateprotected JdkImplprotected LicenseKeyDataImplstatic final Stringstatic final Stringstatic final Stringstatic final String -
Constructor Summary
ConstructorsConstructorDescriptionInternalsImpl(DatabaseImpl database, ApplicationServerImpl server, LicenseKeyDataImpl licenseKey, JdkImpl jdk) InternalsImpl(InternalsImpl internals) -
Method Summary
Modifier and TypeMethodDescriptionInformation about the application server Camunda is running on.Used Camunda integrations (e.g, Spring boot starter, Camunda Platform Run, WildFly/JBoss subsystem or Camunda EJB service).Information about the number of command executions performed by the Camunda engine.Information about the connected database system.The date when the engine started to collect dynamic data, such as command executions and metrics.getJdk()Information about the installed Java runtime environment.Information about the Camunda license key issued for enterprise editions of Camunda Platform.A selection of metrics collected by the engine.Webapps enabled in the Camunda installation (e.g., cockpit, admin, tasklist).voidmergeDynamicData(InternalsImpl other) voidputCommand(String commandName, int count) voidvoidsetApplicationServer(ApplicationServerImpl applicationServer) voidsetCamundaIntegration(Set<String> camundaIntegration) voidsetCommands(Map<String, Command> commands) voidsetDatabase(DatabaseImpl database) voidsetDataCollectionStartDate(Date dataCollectionStartDate) voidvoidsetLicenseKey(LicenseKeyDataImpl licenseKey) voidsetMetrics(Map<String, Metric> metrics) voidsetWebapps(Set<String> webapps)
-
Field Details
-
SERIALIZED_APPLICATION_SERVER
- See Also:
-
SERIALIZED_CAMUNDA_INTEGRATION
- See Also:
-
SERIALIZED_LICENSE_KEY
- See Also:
-
SERIALIZED_DATA_COLLECTION_START_DATE
- See Also:
-
database
-
applicationServer
-
licenseKey
-
camundaIntegration
-
dataCollectionStartDate
-
commands
-
metrics
-
webapps
-
jdk
-
-
Constructor Details
-
InternalsImpl
public InternalsImpl() -
InternalsImpl
public InternalsImpl(DatabaseImpl database, ApplicationServerImpl server, LicenseKeyDataImpl licenseKey, JdkImpl jdk) -
InternalsImpl
-
-
Method Details
-
getDatabase
Description copied from interface:InternalsInformation about the connected database system.- Specified by:
getDatabasein interfaceInternals
-
setDatabase
-
getApplicationServer
Description copied from interface:InternalsInformation about the application server Camunda is running on.- Specified by:
getApplicationServerin interfaceInternals
-
setApplicationServer
-
getDataCollectionStartDate
Description copied from interface:InternalsThe date when the engine started to collect dynamic data, such as command executions and metrics. If telemetry sending is enabled, dynamic data resets on sending the data to Camunda. This method returns a date that represents the date and time when the dynamic data collected for telemetry is reset. Dynamic data and the date returned by this method are reset in three cases:- At engine startup, the date is set to the current time, even if telemetry is disabled. It is then only used by the telemetry Query API that returns the currently collected data but sending telemetry to Camunda is disabled.
- When sending telemetry to Camunda is enabled after engine start via API (e.g.,
ManagementService.toggleTelemetry(boolean). This call causes the engine to wipe all dynamic data and therefore the collection date is reset to the current time. - When sending telemetry to Camunda is enabled, after sending the data, all existing dynamic data is wiped and therefore the collection date is reset to the current time.
- Specified by:
getDataCollectionStartDatein interfaceInternals- Returns:
- A date that represents the start of the time frame where the current telemetry data set was collected.
-
setDataCollectionStartDate
-
getCommands
Description copied from interface:InternalsInformation about the number of command executions performed by the Camunda engine. If telemetry sending is enabled, the number of executions per command resets on sending the data to Camunda. Retrieving the data throughManagementService.getTelemetryData()will not reset the count.- Specified by:
getCommandsin interfaceInternals
-
setCommands
-
putCommand
-
getMetrics
Description copied from interface:InternalsA selection of metrics collected by the engine. Metrics included are:- The number of root process instance executions started.
- The number of activity instances started or also known as flow node instances.
- The number of executed decision instances.
- The number of executed decision elements.
ManagementService.getTelemetryData()will not reset the count.- Specified by:
getMetricsin interfaceInternals
-
setMetrics
-
putMetric
-
mergeDynamicData
-
getJdk
Description copied from interface:InternalsInformation about the installed Java runtime environment. -
setJdk
-
getCamundaIntegration
Description copied from interface:InternalsUsed Camunda integrations (e.g, Spring boot starter, Camunda Platform Run, WildFly/JBoss subsystem or Camunda EJB service).- Specified by:
getCamundaIntegrationin interfaceInternals
-
setCamundaIntegration
-
getLicenseKey
Description copied from interface:InternalsInformation about the Camunda license key issued for enterprise editions of Camunda Platform. May be null when no license is used.- Specified by:
getLicenseKeyin interfaceInternals
-
setLicenseKey
-
getWebapps
Description copied from interface:InternalsWebapps enabled in the Camunda installation (e.g., cockpit, admin, tasklist).- Specified by:
getWebappsin interfaceInternals
-
setWebapps
-