Skip to content

Buffered actions #2

@pierky

Description

@pierky

Implement a mechanism to avoid actions flooding via buffering.
Actions are added to a queue that is processed once every X (for streaming monitors) or after process_results().

Configurable options:

  • email actions can be grouped in a single message;
  • external programs can be executed only once for each X (result, probe, macro-expanded arguments list).

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions