How to Change the Default Topic of a Device Service

[kayielt]

Hello everyone, I tried to change the configuration.yaml of device-modbus-go, expecting the data to be sent to the MessageBus with my modified configuration, but the device service raised an error in the logs.


Then I check this log core-metadata

I would appreciate some advice on this case. Is it acceptable to do this? Thank you.

[cloudxxx8]

Your config change will only be adopted by device-modbus service. You need to modify your config in common-config to apply to all services.
https://github.com/edgexfoundry/edgex-go/blob/72591cb8d59e464071c8624b664f23cc7ea8b8ea/cmd/core-common-config-bootstrapper/res/configuration.yaml#L60

After services first start up, all the config will be pushed Core Keeper, so you have to modify the configs in Core Keeper, or add -o flag to overwrite your config change.

[kayielt]

I tried cloning and rebuilding the core services, then changed the topic in the configuration file for each service and ran them. However, I got the following result from core-common-config-bootstrapper, as shown below.

[cloudxxx8]

The error logs show common-config-bootrsaper cannot communitcate with core-keeper, so you have to check the core-keeper logs and whether the docker network host setting is correct.

[kayielt]

I cloned the edgex-go repository and rebuilt all core services using version 4.0.1. Data ingestion from the device-modbus device service is working as expected.
Is it possible to customize the default MessageBus publish topic or event payload used by a device service when it publishes Events to the MessageBus (for example, changing the BaseTopicPrefix or the default topic structure)?

[cloudxxx8]

no, EdgeX doesn't support the event payload customization
You may write a service to receive the event and transform the payload, and then re-publish to another topic

[kayielt]

Thank you for your support and feedback