Skip to main content
Question

Google SecOps SIEM Dashboards Export and Import

  • February 16, 2026
  • 0 replies
  • 0 views

vnair

We have multiple instances of SecOps, one for Dev and the other for Prod - the nature of business requires us to do this. Developers build Dashboards in the Dev environment, publish for testing and once tested and found okay, will be exported to create the JSON files which will be imported in the Prod environment.

A dashboard can call another dashboard using a button. When copying the link details in the creation of the button, we cannot select from a list of available Dashboards. What we do today is view the Dashboard we need to connect to, copy the URL and then paste it in the box for the link. We can then remove everything after the dashboard ID and it will continue to work.

Q1: Are we doing this correctly? Is there a better way to do this?

 

The export creates the JSON file with appropriate dashboard IDs generated in the Dev environment. Button links point to the Dev environment dashboard, naturally and preserved in the import. To avoid linking to a different environment, we had to first view the linked dashboard in the Prod environment (if we have exported and imported it), then edit the newly imported dashboard that calls it, edit the specific button and paste the new link.

Q2. Are we doing this correctly? Is there a better way to do this? 

 

Q3. We are trying to migrate published code in Dev to Prod and publish it for consumption of customers; and trying to automate this process somehow. Has someone done this or is there a way to do this? In general, the export and import process works if there are no links outside the dashboard specific to a SecOps environment.