Hi,
SonarQube reflects what was found by - and passed in to - the last analysis. So analyze your repository with all the coverage reports present, and the coverage for everything should show up.
This might need some untangling. Normally it’s one project in SonarQube per buildable software project. So I would expect each microservice to have it’s own SonarQube project.
In that^ context, I’m not sure I understand your scenario for populating coverage for every microservice. Just make sure running the tests before analysis & passing the reports in is part of the pipeline for each microservice.
Does that help?
Ann