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

[Feature] Add persistent drop monitor functionality #3501

Open
10 tasks done
arista-hpandya opened this issue Feb 8, 2025 · 0 comments · May be fixed by #3509
Open
10 tasks done

[Feature] Add persistent drop monitor functionality #3501

arista-hpandya opened this issue Feb 8, 2025 · 0 comments · May be fixed by #3509

Comments

@arista-hpandya
Copy link

arista-hpandya commented Feb 8, 2025

Description:

This issue tracks the implementation of the persistent drop monitor feature within the dropmonitor orchagent, as described in the SONiC drop counter monitoring HLD. This feature will enable the monitoring of drop counters against configurable thresholds, triggering syslog entries for persistent drops, enhancing network troubleshooting capabilities.

Tasks:

  • Implement the logic to monitor drop counters against configured thresholds.
  • Add support for the following configurable parameters:
    • Status (enabled/disabled toggle)
    • Window size (sliding time window in seconds)
    • Drop count threshold (minimum drops per window for an incident)
    • Incident count threshold (minimum incidents to trigger a syslog entry)
  • Implement the logic to track incidents within the specified window size.
  • Implement the logic to generate syslog entries when the incident count threshold is met.
  • Ensure minimal CPU overhead. (Target: Nominal increase of the mean CPU utilization by 1 percentage points or less).
  • Verify that the feature has minimal effect on memory usage.

Background:

The persistent drop monitor feature enhances the existing SONiC drop counter functionality by adding the ability to monitor for sustained drop patterns. The dropmonitor orchagent will be responsible for implementing the core logic of this feature, including monitoring drop counters, tracking incidents, and generating syslog entries. The configurations are global and will apply to all configured drop counters on the device.

References:

@arista-hpandya arista-hpandya changed the title [Feature] Implement persistent drop monitor in dropmonitor orchagent [Feature] Implement persistent drop monitor functionality Feb 8, 2025
@arista-hpandya arista-hpandya changed the title [Feature] Implement persistent drop monitor functionality [Feature] Add persistent drop monitor functionality Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant