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

Beyla does not stop execution if only NetO11y or AppO11y component fails. #1514

Closed
mariomac opened this issue Jan 10, 2025 · 0 comments
Closed
Assignees
Labels

Comments

@mariomac
Copy link
Contributor

In Beyla 1.6, when either NetO11y or AppO11y couldn't initialize, Beyla stopped.

Example, setting a wrong BEYLA_NETWORK_AGENT_IP value:

time=2025-01-10T15:38:26.461Z level=INFO msg="Grafana Beyla" Version=cc5a468f Revision=cc5a468f "OpenTelemetry SDK Version"=1.24.0
time=2025-01-10T15:38:26.462Z level=INFO msg="starting PProf HTTP listener" port=6060
time=2025-01-10T15:38:26.462Z level=INFO msg="starting Beyla in Network metrics mode"
time=2025-01-10T15:38:26.462Z level=INFO msg="initializing Flows agent" component=agent.Flows
time=2025-01-10T15:38:26.462Z level=ERROR msg="can't start network metrics capture" error="acquiring Agent IP: can't parse provided IP alsdkfjlk***ads!!"

At some point in Beyla 1.7, this is not the behavior anymore and Beyla keeps running without showing any error. PR #1509 restores the error messages but the failure would anyway become unnoticed for most users unless they see the logs of all their Beyla isntances.

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

No branches or pull requests

2 participants