Self-hosted dashboards won't initialize after architecture change 0.66 --> ~/0.76

[phazeight]

Bug description

Please describe.
If this affects the front-end, screenshots would be of great help.

Expected behavior

I am deploying a self hosted version of Signoz on an ec2 instance. On version 0.66.0 I was able to add my own dashboards at path /deploy/docker/clickhouse-setup/dashboards many from the templates at Signoz Dashboards repo, by adding them in .json style similar to a Grafana setup. I just had to create a dashboards directory as spelled out above and change the docker-compose-minimal.yaml file that was my main config getting deployed from the below

    volumes:
      - ../dashboards:/root/config/dashboards

to

    volumes:
      - ./dashboards:/root/config/dashboards

and that was it

This allowed me to have a good amount of pre-built dashboards available to my engineers on the signoz instance on fresh install. Also allows us to define dashboards as code for the future that we build. See attached screenshot for visual.

This has worked consistently for me for a time, but I have been trying to follow the docs and upgrade our signoz version to 0.76.2 with a fresh install and I've been merging the updates from Signoz main branch to the branch I am deploying and keeping the changes that are specific to our implementation of Signoz, but with the Re-architecture I have lost the ability to get my dashboards upon fresh install/initialization and I can't track down why.

Here, I can see the restructuring of the docker directories, but when I tried to match what I did above to retain the ability to have my dashboards upon fresh 0.76.2 deployment, they now don't show up. I've tried both pointing the dockerfile at /deploy/common/dashboards and like what I did above, make my own dashboards directory in the same path /deploy/docker/dashboards and neither works. Screenshot below

in new file after re-arch docker-compse.yaml

    volumes:
          - ../common/signoz/prometheus.yml:/root/config/prometheus.yml
          - ../common/dashboards:/root/config/dashboards

to

    volumes:
          - ../common/signoz/prometheus.yml:/root/config/prometheus.yml
          - ../common/dashboards:/root/config/dashboards

I might be missing something easy or simple, but I've tried to be thorough and really would not like to lose this functionality

How to reproduce

1. Create dashboards as .json files, and populate in either deploy/docker/dashboards or deploy/common/dashboards
2. match docker compose file that stands up signoz stack to ensure volume's match up to dashboards
3. stand up app and check that dashboards are not there

Version information

• Signoz version: 0.66.0 --> 0.76.2
• Browser version: Arc- 1.88.0 Chromium Engine: 135.0.7049.17
• Your OS and version: Mac OSX Sequoia 15.3.2
• Your CPU Architecture(ARM/Intel): Apple M4 Pro

Additional context

Thank you for your bug report – we love squashing them!

[welcome]

Thanks for opening this issue. A team member should give feedback soon. In the meantime, feel free to check out the contributing guidelines.

[Nageshbansal]

cc: @grandwizard28