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

new(filtering): whitelist current executable #129

Merged
merged 3 commits into from
Jan 19, 2023

Conversation

MatteoNardi
Copy link
Contributor

Fix #128 by whitelisting the current process path instead of the current PID. This allows to ignore the client CLI executable. Failing to ignore it would lead to loops of events, see issue #128 for more details.

Add option process-monitor.ignore_self, which can be used to disable this default behaviour.

I have

  • run cargo fmt;
  • run cargo clippy;
  • run cargo testand all tests pass;
  • linked to the originating issue (if applicable).

@MatteoNardi MatteoNardi linked an issue Jan 17, 2023 that may be closed by this pull request
Fix #128 by whitelisting the current process path instead of the current
PID. This allows to ignore the client CLI executable. Failing to ignore
it would lead to loops of events, see issue #128 for more details.

Add option `process-monitor.ignore_self`, which can be used to disable
this default behaviour.
@MatteoNardi MatteoNardi force-pushed the 128-pulsar-monitor-all-generates-loop-of-events branch from 07816ec to d25a9ab Compare January 19, 2023 11:01
@MatteoNardi MatteoNardi merged commit dc036f9 into main Jan 19, 2023
@MatteoNardi MatteoNardi deleted the 128-pulsar-monitor-all-generates-loop-of-events branch January 19, 2023 12:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

pulsar monitor --all generates loop of events
2 participants