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

Troubleshooting and Reference pages do not reference multi-app-dapr-run #4444

Open
vaughnbuttiw opened this issue Dec 1, 2024 · 0 comments
Labels
content/incorrect-information Content in the docs is incorrect

Comments

@vaughnbuttiw
Copy link

Describe the issue
I was trying out the quickstart sample at https://github.com/dapr/quickstarts/tree/master/pub_sub/java/sdk and I was trying to get more logging from the dapr runtime (daprd).

I searched for how to control the log levels and Auntie Google directed me to (1) and (2).

I tried applying the instructions on (1) and (2) with dapr run --log-level debug -f . It didn't work - the applied log levels didn't change (the fact that it didn't work is not the issue that I am reporting).

After looking some more, I discovered (3). When I applied the instructions in (3) I got the logging that I wanted.

My issue is that (1) and (2) are phrased in such a way as to indicate (at least to me) that they describe a way that works for all dapr run commands and that no other configuration is required.

URL of the docs

  1. https://docs.dapr.io/operations/troubleshooting/logs-troubleshooting/
  2. https://docs.dapr.io/reference/arguments-annotations-overview/
  3. https://docs.dapr.io/developing-applications/local-development/multi-app-dapr-run/multi-app-template/

Expected content
I suggest that the content of (1) and (2) be changed to indicate that dapr run with multi-app configuration (so -f ?) is configured differently and that some of the information provided on (1) and (2) is not applicable to running dapr run -f and that the user be directed to, or at least provided with a link to, (3).

Screenshots
N/A

Additional context
IMHO, While the README.md for the quickstart does reference (3), I think (1) and (2) should also reference it.

@vaughnbuttiw vaughnbuttiw added the content/incorrect-information Content in the docs is incorrect label Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content/incorrect-information Content in the docs is incorrect
Projects
None yet
Development

No branches or pull requests

1 participant