Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IDEA] Display which node is effective in sending data #5741

Open
Kurt-AZ opened this issue Mar 31, 2023 · 1 comment
Open

[IDEA] Display which node is effective in sending data #5741

Kurt-AZ opened this issue Mar 31, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@Kurt-AZ
Copy link

Kurt-AZ commented Mar 31, 2023

We are using the advanced clustering plugin (version 4.0.1) and have noticed that it is not always the Mirth node which has the polling role, that is effectively sending out the data.
In certain circumstances, it can be that another node is sending out the data to its destination.
For the moment this can nowhere be seen in the interface (GUI) which node is effectively sending the data.
Only the node that has received the data can be checked in the GUI (column Original Server ID).

If a certain node has to be rebooted or is failing, it would be helpful to check in advance if the node is sending out some data.

So an extra column or any other way to show this in the GUI would be a great benefit when using a HA environment.

Related discussion: #5735

@Kurt-AZ Kurt-AZ added the enhancement New feature or request label Mar 31, 2023
@pladesma
Copy link
Collaborator

A possible workaround is to add the server ID to a custom metadata field in the Destination connector. For example, create a new custom metadata field named SENDING_SERVER_ID with the variable mapping serverId. Then in the destination connector, add a Javascript transformer step with the following code:

var serverInstance = Packages.com.mirth.connect.server.controllers.ConfigurationController.getInstance();
var serverId = serverInstance.getServerId();
connectorMap.put('serverId', serverId);

Would that properly handle your use case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants