Automating Tag Configuration Updates Across Multiple Gateways

I'm looking to gather insights or share experiences regarding the automation of tag configuration updates across multiple Ignition gateways. In our organization, we operate over 50 facilities, each equipped with its own Ignition gateway. Frequently, we find ourselves in situations requiring updates to tag configurations, such as enabling history on specific tags. Currently, this process involves manually signing into the designer of each gateway and updating tags one by one, which is time-consuming and prone to errors.

I'm exploring ways to streamline this process and was wondering if anyone here has tackled a similar challenge. Specifically, I'm curious about the feasibility and methods to execute the system.tag.configure function (or any equivalent approach) across all gateways in a more automated manner.

I'm interested in hearing if anyone has implemented a solution along these lines or has insights into best practices for managing such tasks.

1 Like

Consider connecting the gateways the Ignition gateway network and use message handlers to pass tag configuration changes.

2 Likes

Alternatively, if you connect them all to a central gateway as remote tag providers, you only have to open a project on the central gateway in designer, and then you can switch between the various tag providers without having to reopen each site in designer.

1 Like