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

Expand logging beyond async-std's task::spawn calls #5

Open
yoshuawuyts opened this issue Mar 20, 2020 · 1 comment
Open

Expand logging beyond async-std's task::spawn calls #5

yoshuawuyts opened this issue Mar 20, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@yoshuawuyts
Copy link
Collaborator

Given that parallel-stream is likely to be a source of many spawned tasks, it's probably useful to add additional log points. This would help trace where tasks are coming from, which is useful when debugging systems.

Also zooming out slightly; this marks another point for why parallel-stream is useful outside of manually spawning tasks for a loop. It's unlikely that regular business logic would consistently add trace points when spawning tasks. Instead by abstracting the parallelization into a library we can do this once, and provide this for everyone.

@yoshuawuyts yoshuawuyts added the enhancement New feature or request label Mar 20, 2020
@Songtronix
Copy link

Hmm I wonder if going with tracing would be beneficial compared to the classic log fascade. One benefit definitly will be the use of scopes to structure the logs and avoid the "async mess" you end up with log not knowing where which log came from in what context/task.

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

No branches or pull requests

2 participants