Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Fix: monitoring networks tracing #826

Merged

Conversation

mrnicegyu11
Copy link
Member

What do these changes do?

Fix #825

Related issue/s

Related PR/s

Checklist

  • I tested and it works

@mrnicegyu11 mrnicegyu11 added observability alerting/monitoring FAST labels Sep 30, 2024
@mrnicegyu11 mrnicegyu11 self-assigned this Sep 30, 2024
@mrnicegyu11 mrnicegyu11 added this to the MartinKippenberger milestone Sep 30, 2024
@YuryHrytsuk
Copy link
Collaborator

YuryHrytsuk commented Sep 30, 2024

It seems that if we want to "jaeger" trace all our services, we need to put all of them to the same docker network. Is this assumption correct? @mrnicegyu11

@mrnicegyu11
Copy link
Member Author

Almost correct @YuryHrytsuk , it is about the otel-collector specifically, but this is part of the jaeger stack

@mrnicegyu11 mrnicegyu11 merged commit 7eeef42 into ITISFoundation:main Sep 30, 2024
3 checks passed
@mrnicegyu11 mrnicegyu11 deleted the fix/monitoringNetworksTracing branch September 30, 2024 15:45
Copy link
Member

@pcrespov pcrespov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FAST observability alerting/monitoring
Projects
None yet
Development

Successfully merging this pull request may close these issues.

simcore datcore-adapter service periodically fails to connect otel-collector host in inhouse-master deploy
3 participants