Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions juniper_official/Solutions/Traffic-Blackhole/pfe-stats.rule
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,19 @@ healthbot {
type string;
description "FPC name";
}
trigger pfe-input-output-stats {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does this look like a dummy trigger to me? Is AIML consuming any trigger data?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this needs to be stored? What is the purpose of this?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, its a dummy commit as we wanted to store ts-input-packets-pps and ts-output-packets-pps to TSDB to plot the Traffic Loss graph (in Routing and MPLS accordion) in real time like we plot the graphs for Hardware and Interfaces accordion.

synopsis "PFE input output stats KPI";
description "Default trigger to move pfe-stats KPI to tsdb";
frequency 1offset;
term ts-input-output-packets-pps {
then {
status {
color green;
message "$ts-input-packets-pps $ts-output-packets-pps";
}
}
}
}
rule-properties {
version 1;
contributor juniper;
Expand Down