Skip to content

SonarQube Pipelines run successfully but no data in dashboard - v1.0.2-beta1 #8091

Description

@srinathsankara

Looks like SonarQube Dashboard is crashing. After successful import using pipelines, dashboard has no data.

image

Activity

  1. changed the title [-]SonarQube Pipelines run successfully but no data in dashboard[/-] [+]SonarQube Pipelines run successfully but no data in dashboard - v1.0.2-beta1[/+] on Sep 24, 2024
  2. dosubot commented on Sep 24, 2024

    @dosubot

    Hello @mrpaapi! I'm here to help you with any bugs, questions, or contributions you may have. If you need assistance, feel free to ask. Dosu

    I found two similar closed issues that might be relevant to your problem:

    1. [Bug][Dashboard] Wrong bug title in the Sonarqube dashboard: This issue was resolved by modifying the character set of several tables. The suggested solution was to run the following scripts to change the collation, then run the SonarQube blueprint again:

      ALTER TABLE _tool_sonarqube_projects CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
      ALTER TABLE _tool_sonarqube_issues CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
      ALTER TABLE _tool_sonarqube_issue_code_blocks CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
      ALTER TABLE _tool_sonarqube_hotspots CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
      ALTER TABLE _tool_sonarqube_file_metrics CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
      ALTER TABLE _tool_sonarqube_accounts CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
      ALTER TABLE cq_projects CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
      ALTER TABLE cq_issues CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
      ALTER TABLE cq_issue_code_blocks CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
      ALTER TABLE cq_file_metrics CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;

      You can find more details here [1].

    2. [Bug][Sonarqube] Lack of metrics for dashboard: This issue was resolved by adding the number of lines metric. You can find more details here [2].

    Additionally, common reasons for the SonarQube dashboard displaying 'No data' after a successful pipeline run could include:

    • Data Scope Configuration: Ensure that the correct SonarQube projects and data entities are selected during the data scope configuration.
    • Sync Policy: Verify that the sync frequency and other sync settings are correctly configured.
    • Data Collection Issues: Check if there were any errors during the data collection process.

    For more detailed troubleshooting, you can refer to the Troubleshooting section or the SonarQube Configuration Documentation [3][4].

    To continue talking to Dosu, mention @dosu.

  3. added
    devopsSomething about CI/CD (devops)
    severity/p1This bug affects functionality or significantly affect ux
    type/bugThis issue is a bug
    on Sep 24, 2024
  4. klesh commented on Sep 24, 2024

    @klesh
    Contributor

    Looks like a known issue to me. Can you confirm? @Startrekzky

  5. srinathsankara commented on Sep 24, 2024

    @srinathsankara
    Author

    I ran this but still no Luck

    can you run the following scripts to change collation, then run the sonarqube bp again:
    ALTER TABLE _tool_sonarqube_projects CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
    ALTER TABLE _tool_sonarqube_issues CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
    ALTER TABLE _tool_sonarqube_issue_code_blocks CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
    ALTER TABLE _tool_sonarqube_hotspots CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
    ALTER TABLE _tool_sonarqube_file_metrics CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
    ALTER TABLE _tool_sonarqube_accounts CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
    ALTER TABLE cq_projects CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
    ALTER TABLE cq_issues CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
    ALTER TABLE cq_issue_code_blocks CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
    ALTER TABLE cq_file_metrics CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;

  6. srinathsankara commented on Sep 25, 2024

    @srinathsankara
    Author
  7. VadimVoykin commented on Oct 1, 2024

    @VadimVoykin

    Hello @Startrekzky!
    We managed to determine that the issue lies in the Grafana queries. In order to fix it, we changed the Data Source of each "Panel" from "Mixed" to "mysql" and changed the table in the query by appending the "lake." prefix.
    2024-10-01_09h13_18

  8. added a commit that references this issue on Oct 10, 2024
    90814fd
  9. added a commit that references this issue on Oct 10, 2024
    c60230e
  10. added a commit that references this issue on Oct 11, 2024
    68bf067
  11. added a commit that references this issue on Oct 11, 2024
    7e058d1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

devopsSomething about CI/CD (devops)severity/p1This bug affects functionality or significantly affect uxtype/bugThis issue is a bugtype/questionThis issue is a question

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions