🐛 Fix opentelemetry errors in autoscaling microservice

[mrnicegyu11]

What do these changes do?

Connect autoscaling microservice to default network in local dev-deploy. Enables autoscaling to communicate with the opentelemetry collector.

Related issue/s

How to test

1. make build up-prod
2. Run docker service logs master-simcore_autoscaling, see no more opentelemetry errors

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.0%. Comparing base (cafbf96) to head (6326b37).
Report is 670 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #6582      +/-   ##
=========================================
+ Coverage    84.5%   86.0%    +1.4%     
=========================================
  Files          10    1556    +1546     
  Lines         214   63674   +63460     
  Branches       25    2085    +2060     
=========================================
+ Hits          181   54790   +54609     
- Misses         23    8580    +8557     
- Partials       10     304     +294     

Flag	Coverage Δ
unittests	86.0% <ø> (+1.4%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1505 files with indirect coverage changes

[pcrespov]

I wonder if we could add tests on the networks. Something like "assert service A reaches service B". We have a system level test in this repo where I will start adding tests that include the reverse proxy. I might also add some "connectivity" tests from A to B using the /status entrypoints between services.

[sanderegg]

Ok this will fix it, thanks.

Nevertheless the autoscaling is not in the default network because it did not need to be there, due to the rule of not adding unnecessary stuff if not needed. Where is this collector in the deployments? in a separate stack I guess?

Anyway thanks!

[mrnicegyu11]

Ok this will fix it, thanks.

Nevertheless the autoscaling is not in the default network because it did not need to be there, due to the rule of not adding unnecessary stuff if not needed. Where is this collector in the deployments? in a separate stack I guess?

Anyway thanks!

Yes the collector is in the ops-stack in osparc-simcore and in the jaeger stack in osparc-ops-environments

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud