dqualizer / dqanalyzer

DEPRECATED The initial dqanalyzer (integrated into the Domain Story Modeler) enables domain experts to specify and perform RQA without profound knowledge of the underlying technical infrastructure and analysis tools
Apache License 2.0
0 stars 0 forks source link

[Bug] - Analyzer fails to forward RQA #29

Closed franksn90 closed 1 year ago

franksn90 commented 1 year ago

Describe the bug

Since PR#25, using the docker compose file from https://github.com/dqualizer/dqualizer, the modeler does not forward the RQA.

To Reproduce

Steps to reproduce the behavior:

  1. Open the modeler
  2. Specify RQA
  3. Press Execute
  4. (nothing happens)

Expected behavior

I expect results on the Grafana board or at least log messages of the executed RQA on the console.

Additional information (screenshots, stack traces, etc.)

On PR#24: Screenshot 2023-05-05 at 09 55 59

On PR#25 / latest: Screenshot 2023-05-05 at 09 43 59

Desktop (please complete the following information):

Additional context

According to the screenshots, RQAs are now sent to different addresses (localhost:8070 vs localhost:8080). I suggest to have a look at the default "VITE_BACKEND_URL" environment variable of the modeler container. As a quick fix, changing it in the docker compose file (as shown below) seems to solve the issue, but changes to the dqanalyzer component might be necessary as well.

  dqanalyzer-frontend:
    image: ghcr.io/dqualizer/dqanalyzer-frontend
    ports:
      - "9080:80"
    environment:
      - VITE_BACKEND_URL=http://localhost:8070
levinkerschberger commented 1 year ago

Specifying the variable VITE_BACKEND_URL in docker-compose is already the solution, since it defaults to 8080. How should I proceed? Change the default or add the environment variable in the dqualizer docker-compose? Or both?

JenSeReal commented 1 year ago

Add the environment variable to both docker-compose files (in this repo and in dqualizer/dqualizer). I would not hardcode a default in code