Managing 200+ Ignition Edge Devices: Best Practices for CI/CD and API Maintenance

I’m working on a project with over 200 Ignition Edge devices with few of Ignition GW , each connected to different sites and their PLCs. These devices also make API calls (POST requests) to external systems. We use a schema generator for these APIs, which includes versioning.

I’m looking for advice on how to manage and maintain this setup effectively. Here are some specific questions: [I known some new features in 8.3 may Help add to that EAM as well ]

  1. Edge Device Management
  • How can I manage so many Edge devices across multiple sites?
  • Are there best practices for organizing configurations, tags, and projects to keep everything consistent and scalable?
  1. CI/CD for Ignition Edge
  • Can CI/CD pipelines be used to deploy changes (like tag updates, scripts, or configurations) to Edge devices?
  • How can I test updates properly before rolling them out to production?
  1. API Maintenance and Updates
  • What’s the best way to update APIs across all Edge devices when schemas or endpoints change?
  • How can I track and manage different API versions across sites?
  1. Version Control and Collaboration
  • What are the best practices for version-controlling Ignition Edge projects and working as a team?
  1. Monitoring and Troubleshooting
  • How can I monitor Edge device performance and API calls to ensure everything runs smoothly?
  • Are there tools or strategies for logging and troubleshooting issues in a distributed system like this?

If anyone has experience managing a similar setup or has tips to share, I’d really appreciate your input!