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

Sentry initializes the metrics server although it is not enabled #1472

Open
AlbertoVPersonal opened this issue Nov 27, 2024 · 0 comments
Open
Labels
kind/bug Something isn't working

Comments

@AlbertoVPersonal
Copy link

Expected Behavior

Sentry must not start the internal metrics server is not enabled.

Actual Behavior

Sentry starts the internal metrics server and it is not enabled.

Steps to Reproduce the Problem

Environment

  • dapr v14.1
  • self-hosted
  • Windows 10 IoT

Steps

  1. Run the following command.
.\bin\sentry.exe --issuer-credentials .\bin\certs\ --trust-domain cluster.local --config .\config.yaml

The console output is:

...
time="2024-11-27T10:13:09.5850661+01:00" level=info msg="metrics server started on :9090/" instance=WS490 scope=dapr.sentry type=log ver=1.14.1
...

So the metrics server is started without the parameter --enable-metrics.

Workaround

Use --enable-metrics False or --enable-metrics 0 does not have effect.

Release Note

RELEASE NOTE: FIX Bug in the 'Sentry' runtime.

@AlbertoVPersonal AlbertoVPersonal added the kind/bug Something isn't working label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant