With #305 multiple deployments to the same namespace were introduced.
We deploy the fluent-bit helmchart two times to the same namespace.
However, the Grafana Dashboard can only be deployed for one of the deployed charts as the dashboard json contains the same uid:
logger=provisioning.dashboard t=2024-03-08T12:38:32.966386088Z level=warn msg="the same UID is used more than once" orgId=1 uid=d557c8f6-cac1-445f-8ade-4c351a9076b1 times=2 providers=[sidecarProvider]
In #391 the grafana dashboard uid was fixed to:
"uid": "d557c8f6-cac1-445f-8ade-4c351a9076b1"
If the uid is manually changed after the second deployment both dashboards are loaded correctly in Grafana.
Is there a good reason to fix the dashboard uid in this chart or is this a bug?
With #305 multiple deployments to the same namespace were introduced.
We deploy the fluent-bit helmchart two times to the same namespace. However, the Grafana Dashboard can only be deployed for one of the deployed charts as the dashboard json contains the same uid:
logger=provisioning.dashboard t=2024-03-08T12:38:32.966386088Z level=warn msg="the same UID is used more than once" orgId=1 uid=d557c8f6-cac1-445f-8ade-4c351a9076b1 times=2 providers=[sidecarProvider]In #391 the grafana dashboard uid was fixed to:
"uid": "d557c8f6-cac1-445f-8ade-4c351a9076b1"If the uid is manually changed after the second deployment both dashboards are loaded correctly in Grafana. Is there a good reason to fix the dashboard uid in this chart or is this a bug?