How to send a subset of tags from one Canary historian to another

Forum / Questions & Answers

Developer
isaac_fowler
3 days ago
1reply

Hello, I was wondering what the best practice is for a hypothetical scenario:

A plant has a subset of Canary tags they'd like to share with a partner who also has their own Canary historian. Either real-time or a minimum of daily updates if possible. Assuming remote access can be routed that way, what service can be used to accomplish this?

- Can the SAF tile be used to select a subset of tags from the source historian and send to the destination?

- Would we need to configure a second session on the OPC collector for only a subset of tags to be shared with the partner historian?

- Or is the only way to accomplish this by using the web API?

Let me know, thanks!

- smason
- 2 days ago
- Reported - view
Hi ! Great question!

The easiest solution would be to set up an alternative OPC Collector session and send the data to their Historian directly, assuming the network allows it.

If the tags you want to send are already in their own distinct SaF session, you could configure the original Historian to be a proxy for that particular session and forward the data onto the next Historian. In that case, you would probably use the SessionName option. This is similar to option 1 because it is still using SaF to transfer the data. The one drawback of this method is it adds a step in between the Collector and the final Historian destination. If the first Historian goes down, the 2nd Historian won't get its data until it comes back up.

If the tags you want to transfer are just a subset of a bigger SaF session, this option will not work.

You could install/enable the Publisher on the first Historian to send the data in real-time using the SparkplugMQTT option. You would need to spin up an MQTT broker (Canary includes the open-source Mosquitto broker in its install which would probably suffice), then install the MQTT Collector on the 2nd Historian to ingest the data. If you designate the MQTT Collector as the primary host, the Publisher will buffer data in the event the Collector disconnects from the broker.

Your final option would be to use the API.