The mapping microservice provides endpoints to control the lifecycle and manage mappings. in details these endpoint are:
.../configuration/connection: retrieve and change the connection details to the MQTT broker.../configuration/serice: retrieve and change the configuration details, e.g. loglevel of the mapping service.../operation: execute operation: reload mappings, connect to broker, disconnect from broker, reset the monitoring statistic, reload extensions.../monitoring/status/connector: retrieve service status: is microservice connected to broker, are connection details loaded.../monitoring/status/mapping: retrieve mapping status: number of messages, errors processed per mapping.../monitoring/tree: all mappings are organised in a tree for efficient processing and resolving the mappings at runtime. This tree can be retrieved for debugging purposes..../monitoring/subscriptions: retrieve all active subscriptions..../mapping: retrieve, create, delete, update mappings.../test/{method}?topic=URL_ENCODED_TOPIC: this endpoint allows testing of a payload. The send parameter (boolean) indicates if the transformed payload should be sent to Cumulocity after processing. The call return a list ofProcessingContextto record which mapping processed the payload and the outcome of the mapping process as well as error.../extension/: endpoint to retrieve a list of all extensions.../extension/{extension-name}: endpoint to retrieve/delete a specific extension