Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PM2 already supports selecting stdout and stderr independently with
pm2 logs --outandpm2 logs --err. This change adds equivalent stream selection topm2 flush:pm2 flush <app> --outclears only stdout logs.pm2 flush <app> --errclears only stderr logs.--errtakes precedence, matchingpm2 logs.Existing flush commands continue clearing both streams. The programmatic API remains backward-compatible.
Flushing uses existing process log metadata, supporting custom paths, application names, process IDs, and cluster workers. Selecting either stream clears a shared stdout/stderr file.