dapr list
display the paths to the application and daprd logs in multi-app run
#1228
Labels
area/cli
good first issue
Good for newcomers
kind/enhancement
enhancement to an existing feature
kind/proposal
A new proposal to be considered
P1
size/XS
2 days work
triaged/resolved
The issue has been triaged
Milestone
Describe the proposal
When using a run file (i.e.
dapr run -f <file>
), Dapr CLI redirects the application and Dapr logs of each application to its own file (under<appDirPath>/.dapr/logs
). Subsequent runs will create new log files to ensure that developers can go back to previous logs for analysis, with each log filename containing a "timestamp" of its first creation. This is great but, after a while, these logs can accumulate and make it difficult for the the user to pick out the right log (e.g. the log that's currently being written to). Tooling can help, by automating the process of finding the "latest" logs and opening those (e.g. in the current editor). However, that automation (based on filenames) is not entirely certain; there will always be a chance some combination of files in the directory disrupts any filename timestamp sort.Tooling is likely to care mostly about the logs being written to right now, and this is information that the Dapr CLI has. I propose that the Dapr CLI expose that information in the
dapr list
command. This will provide a more deterministic means to obtain the paths to application logs (and avoid having tooling care about Dapr log naming conventions).For example:
Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered: