Sentry initializes the metrics server although it is not enabled

[AlbertoVPersonal]

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.

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.