diff --git a/docs/about_releases.mdx b/docs/about_releases.mdx index a924e7a68a..865a0aa685 100644 --- a/docs/about_releases.mdx +++ b/docs/about_releases.mdx @@ -27,13 +27,13 @@ Version `6.1.0` introduces changes to the SSR software release model. Every six | Release 6.2 | [6.2.0](release_notes_128t_6.2.md#release-620-39) | November 16, 2023 | [6.2.4](release_notes_128t_6.2.md#release-624-14r2) | August 16, 2024 | November 3, 2024 | | Release 6.1 | [6.1.0](release_notes_128t_6.1.md#release-610-55) | April 14, 2023 | [6.1.8](release_notes_128t_6.1.md#release-618-15) | September 22, 2025 | June 22, 2026 | | Release 5.6 | [5.6.7](release_notes_128t_5.6.md#release-567-4) | March 16, 2023 | [5.6.14](release_notes_128t_5.6.md#release-5614-7) | June 16, 2024 | December 16, 2024 | -| Release 5.5 | [5.5.3](release_notes_128t_5.5.md#release-553-4) | August 11, 2022 | [5.5.12](release_notes_128t_5.5.md#release-5512-9) | November 19, 2023 | May 19, 2024 | ## Out of Support | Version | FRS Date | End of Software Engineering support | End of Support | | ----------- | ----------------- | ----------------------------------- | ------------------ | | Release 6.0 | July 18, 2022 | November 30, 2023 | November 30, 2023 | +| Release 5.5 | August 11, 2022 | November 19, 2023 | May 19, 2024 | | Release 5.4 | February 18, 2022 | December 18, 2022 | June 18, 2023 | | Release 5.3 | August 6, 2021 | February 6, 2022 | August 6, 2022 | | Release 5.2 | May 10, 2021 | November 10, 2021 | May 10, 2022 | diff --git a/docs/cli_stats_reference.md b/docs/cli_stats_reference.md index 179a087c61..23b9948360 100644 --- a/docs/cli_stats_reference.md +++ b/docs/cli_stats_reference.md @@ -189,7 +189,7 @@ show stats aggregate-session [since ] [force] [router ] [] [force] [router ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -7947,7 +7947,7 @@ show stats aggregate-session by-node bandwidth [since ] [force] [router < | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -7972,7 +7972,7 @@ show stats aggregate-session by-node bandwidth-other-protocol [since ] [f | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -7997,7 +7997,7 @@ show stats aggregate-session by-node bandwidth-received [since ] [force] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8022,7 +8022,7 @@ show stats aggregate-session by-node bandwidth-received-forward [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8051,7 +8051,7 @@ show stats aggregate-session by-node bandwidth-received-other-protocol [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8163,7 +8163,7 @@ show stats aggregate-session by-node bandwidth-received-tcp [since ] [for | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8188,7 +8188,7 @@ show stats aggregate-session by-node bandwidth-received-tcp-forward [since ] [for | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8271,7 +8271,7 @@ show stats aggregate-session by-node bandwidth-received-udp-forward [since ] [force] [rout | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8354,7 +8354,7 @@ show stats aggregate-session by-node bandwidth-transmitted [since ] [forc | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8379,7 +8379,7 @@ show stats aggregate-session by-node bandwidth-transmitted-forward [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8545,7 +8545,7 @@ show stats aggregate-session by-node bandwidth-transmitted-tcp-forward [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8628,7 +8628,7 @@ show stats aggregate-session by-node bandwidth-transmitted-udp-forward [since ] [force] [rout | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8711,7 +8711,7 @@ show stats aggregate-session by-node bytes [since ] [force] [router ] [forc | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8769,7 +8769,7 @@ show stats aggregate-session by-node bytes-dropped-other-protocol-forward [since | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8798,7 +8798,7 @@ show stats aggregate-session by-node bytes-dropped-other-protocol-reverse [since | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8827,7 +8827,7 @@ show stats aggregate-session by-node bytes-dropped-reverse [since ] [forc | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8856,7 +8856,7 @@ show stats aggregate-session by-node bytes-dropped-tcp-forward [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8885,7 +8885,7 @@ show stats aggregate-session by-node bytes-dropped-tcp-reverse [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8914,7 +8914,7 @@ show stats aggregate-session by-node bytes-dropped-udp-forward [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8943,7 +8943,7 @@ show stats aggregate-session by-node bytes-dropped-udp-reverse [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -8972,7 +8972,7 @@ show stats aggregate-session by-node bytes-other-protocol [since ] [force | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9001,7 +9001,7 @@ show stats aggregate-session by-node bytes-received [since ] [force] [rou | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9030,7 +9030,7 @@ show stats aggregate-session by-node bytes-received-forward [since ] [for | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9059,7 +9059,7 @@ show stats aggregate-session by-node bytes-received-other-protocol [since ] [for | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9175,7 +9175,7 @@ show stats aggregate-session by-node bytes-received-tcp [since ] [force] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9204,7 +9204,7 @@ show stats aggregate-session by-node bytes-received-tcp-forward [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9233,7 +9233,7 @@ show stats aggregate-session by-node bytes-received-tcp-reverse [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9262,7 +9262,7 @@ show stats aggregate-session by-node bytes-received-udp [since ] [force] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9291,7 +9291,7 @@ show stats aggregate-session by-node bytes-received-udp-forward [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9320,7 +9320,7 @@ show stats aggregate-session by-node bytes-received-udp-reverse [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9349,7 +9349,7 @@ show stats aggregate-session by-node bytes-tcp [since ] [force] [router < | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9378,7 +9378,7 @@ show stats aggregate-session by-node bytes-transmitted [since ] [force] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9407,7 +9407,7 @@ show stats aggregate-session by-node bytes-transmitted-forward [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9436,7 +9436,7 @@ show stats aggregate-session by-node bytes-transmitted-other-protocol [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9552,7 +9552,7 @@ show stats aggregate-session by-node bytes-transmitted-tcp [since ] [forc | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9581,7 +9581,7 @@ show stats aggregate-session by-node bytes-transmitted-tcp-forward [since ] [forc | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9668,7 +9668,7 @@ show stats aggregate-session by-node bytes-transmitted-udp-forward [since ] [force] [router < | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9755,7 +9755,7 @@ show stats aggregate-session by-node gross-entitlement [since ] [force] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9780,7 +9780,7 @@ show stats aggregate-session by-node packets [since ] [force] [router ] [fo | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9834,7 +9834,7 @@ show stats aggregate-session by-node packets-dropped-other-protocol-forward [sin | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9863,7 +9863,7 @@ show stats aggregate-session by-node packets-dropped-other-protocol-reverse [sin | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9892,7 +9892,7 @@ show stats aggregate-session by-node packets-dropped-reverse [since ] [fo | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9921,7 +9921,7 @@ show stats aggregate-session by-node packets-dropped-tcp-forward [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9950,7 +9950,7 @@ show stats aggregate-session by-node packets-dropped-tcp-reverse [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -9979,7 +9979,7 @@ show stats aggregate-session by-node packets-dropped-udp-forward [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10008,7 +10008,7 @@ show stats aggregate-session by-node packets-dropped-udp-reverse [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10037,7 +10037,7 @@ show stats aggregate-session by-node packets-other-protocol [since ] [for | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10062,7 +10062,7 @@ show stats aggregate-session by-node packets-received [since ] [force] [r | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10087,7 +10087,7 @@ show stats aggregate-session by-node packets-received-forward [since ] [f | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10116,7 +10116,7 @@ show stats aggregate-session by-node packets-received-other-protocol [since ] [f | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10228,7 +10228,7 @@ show stats aggregate-session by-node packets-received-tcp [since ] [force | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10253,7 +10253,7 @@ show stats aggregate-session by-node packets-received-tcp-forward [since | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10282,7 +10282,7 @@ show stats aggregate-session by-node packets-received-tcp-reverse [since | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10311,7 +10311,7 @@ show stats aggregate-session by-node packets-received-udp [since ] [force | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10336,7 +10336,7 @@ show stats aggregate-session by-node packets-received-udp-forward [since | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10365,7 +10365,7 @@ show stats aggregate-session by-node packets-received-udp-reverse [since | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10394,7 +10394,7 @@ show stats aggregate-session by-node packets-tcp [since ] [force] [router | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10419,7 +10419,7 @@ show stats aggregate-session by-node packets-transmitted [since ] [force] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10444,7 +10444,7 @@ show stats aggregate-session by-node packets-transmitted-forward [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10473,7 +10473,7 @@ show stats aggregate-session by-node packets-transmitted-other-protocol [since < | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10498,7 +10498,7 @@ show stats aggregate-session by-node packets-transmitted-other-protocol-forward | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10527,7 +10527,7 @@ show stats aggregate-session by-node packets-transmitted-other-protocol-reverse | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10556,7 +10556,7 @@ show stats aggregate-session by-node packets-transmitted-reverse [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10585,7 +10585,7 @@ show stats aggregate-session by-node packets-transmitted-tcp [since ] [fo | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10610,7 +10610,7 @@ show stats aggregate-session by-node packets-transmitted-tcp-forward [since ] [fo | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10693,7 +10693,7 @@ show stats aggregate-session by-node packets-transmitted-udp-forward [since ] [force] [router | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10776,7 +10776,7 @@ show stats aggregate-session by-node session-arrival-rate [since ] [force | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10801,7 +10801,7 @@ show stats aggregate-session by-node session-count [since ] [force] [rout | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10826,7 +10826,7 @@ show stats aggregate-session by-node session-departure-rate [since ] [for | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10851,7 +10851,7 @@ show stats aggregate-session by-node tcp-bad-flag-combinations [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10880,7 +10880,7 @@ show stats aggregate-session by-node tcp-bad-flag-combinations-forward [since ] [force] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10967,7 +10967,7 @@ show stats aggregate-session by-node tcp-duplicate-acks-forward [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -10996,7 +10996,7 @@ show stats aggregate-session by-node tcp-duplicate-acks-reverse [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11025,7 +11025,7 @@ show stats aggregate-session by-node tcp-invalid-state-transitions [since ] [force] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11141,7 +11141,7 @@ show stats aggregate-session by-node tcp-out-of-window-forward [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11170,7 +11170,7 @@ show stats aggregate-session by-node tcp-out-of-window-reverse [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11199,7 +11199,7 @@ show stats aggregate-session by-node tcp-resets [since ] [force] [router | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11228,7 +11228,7 @@ show stats aggregate-session by-node tcp-resets-received [since ] [force] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11257,7 +11257,7 @@ show stats aggregate-session by-node tcp-resets-received-forward [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11286,7 +11286,7 @@ show stats aggregate-session by-node tcp-resets-received-reverse [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11315,7 +11315,7 @@ show stats aggregate-session by-node tcp-resets-transmitted [since ] [for | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11344,7 +11344,7 @@ show stats aggregate-session by-node tcp-resets-transmitted-forward [since ] [force] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11427,7 +11427,7 @@ show stats aggregate-session by-node tcp-retransmissions-received [since | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11452,7 +11452,7 @@ show stats aggregate-session by-node tcp-retransmissions-received-forward [since | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11481,7 +11481,7 @@ show stats aggregate-session by-node tcp-retransmissions-received-reverse [since | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11510,7 +11510,7 @@ show stats aggregate-session by-node tcp-retransmissions-transmitted [since ] [since ] [for | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11752,7 +11752,7 @@ show stats aggregate-session by-service bandwidth [service ] [since ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -11829,7 +11829,7 @@ show stats aggregate-session by-service bandwidth-received-forward [service ] [since | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12169,7 +12169,7 @@ show stats aggregate-session by-service bandwidth-transmitted [service | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12195,7 +12195,7 @@ show stats aggregate-session by-service bandwidth-transmitted-forward [service < | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12225,7 +12225,7 @@ show stats aggregate-session by-service bandwidth-transmitted-other-protocol [se | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12251,7 +12251,7 @@ show stats aggregate-session by-service bandwidth-transmitted-other-protocol-for | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12281,7 +12281,7 @@ show stats aggregate-session by-service bandwidth-transmitted-other-protocol-rev | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12311,7 +12311,7 @@ show stats aggregate-session by-service bandwidth-transmitted-reverse [service < | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12340,7 +12340,7 @@ show stats aggregate-session by-service bandwidth-transmitted-tcp [service ] [since | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12535,7 +12535,7 @@ show stats aggregate-session by-service bytes [service ] [since | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12565,7 +12565,7 @@ show stats aggregate-session by-service bytes-dropped-forward [service | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12595,7 +12595,7 @@ show stats aggregate-session by-service bytes-dropped-other-protocol-forward [se | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12625,7 +12625,7 @@ show stats aggregate-session by-service bytes-dropped-other-protocol-reverse [se | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12655,7 +12655,7 @@ show stats aggregate-session by-service bytes-dropped-reverse [service | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned.| ##### Positional Arguments @@ -12685,7 +12685,7 @@ show stats aggregate-session by-service bytes-dropped-tcp-forward [service ] | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12834,7 +12834,7 @@ show stats aggregate-session by-service bytes-received [service ] [sinc | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -12864,7 +12864,7 @@ show stats aggregate-session by-service bytes-received-forward [service ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -13043,7 +13043,7 @@ show stats aggregate-session by-service bytes-received-tcp-forward [service ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -13132,7 +13132,7 @@ show stats aggregate-session by-service bytes-received-udp-forward [service ] [since ] [s | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -13250,7 +13250,7 @@ show stats aggregate-session by-service bytes-transmitted-forward [service | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -13429,7 +13429,7 @@ show stats aggregate-session by-service bytes-transmitted-tcp-forward [service < | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -13459,7 +13459,7 @@ show stats aggregate-session by-service bytes-transmitted-tcp-reverse [service < | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -13488,7 +13488,7 @@ show stats aggregate-session by-service bytes-transmitted-udp [service | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -13518,7 +13518,7 @@ show stats aggregate-session by-service bytes-transmitted-udp-forward [service < | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -13548,7 +13548,7 @@ show stats aggregate-session by-service bytes-transmitted-udp-reverse [service < | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -13577,7 +13577,7 @@ show stats aggregate-session by-service bytes-udp [service ] [since ] [since ] [si | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -13923,7 +13923,7 @@ show stats aggregate-session by-service packets-received-forward [service ] | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -14094,7 +14094,7 @@ show stats aggregate-session by-service packets-received-tcp-forward [service ] | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -14179,7 +14179,7 @@ show stats aggregate-session by-service packets-received-udp-forward [service ] [since < | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -14263,7 +14263,7 @@ show stats aggregate-session by-service packets-transmitted [service ] | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -14289,7 +14289,7 @@ show stats aggregate-session by-service packets-transmitted-forward [service ] [since < | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -14629,7 +14629,7 @@ show stats aggregate-session by-service session-arrival-rate [service ] | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -14654,7 +14654,7 @@ show stats aggregate-session by-service session-count [service ] [since | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -14679,7 +14679,7 @@ show stats aggregate-session by-service session-departure-rate [service ] [ | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -14825,7 +14825,7 @@ show stats aggregate-session by-service tcp-duplicate-acks-forward [service ] [s | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -15005,7 +15005,7 @@ show stats aggregate-session by-service tcp-out-of-window-forward [service ] [since ] | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -15123,7 +15123,7 @@ show stats aggregate-session by-service tcp-resets-received-forward [service ] | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service | The name of the service generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -15296,7 +15296,7 @@ show stats aggregate-session by-service tcp-retransmissions-received [service ] [s | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service-class | The name of the service class generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -15625,7 +15625,7 @@ show stats aggregate-session by-service-class bandwidth [service-class ] [s | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service-group | The name of the service group generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -19498,7 +19497,7 @@ show stats aggregate-session by-service-group bandwidth [service-group ] [s | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | | service-route | The name of the service route generating this metric (comma-separated list) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | ##### Positional Arguments @@ -23371,7 +23370,7 @@ show stats aggregate-session by-service-route bandwidth [service-route ] [since ] [force] | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -27243,7 +27242,7 @@ show stats aggregate-session by-tenant bandwidth [tenant ] [since | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -27294,7 +27293,7 @@ show stats aggregate-session by-tenant bandwidth-received [tenant ] [sin | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -27320,7 +27319,7 @@ show stats aggregate-session by-tenant bandwidth-received-forward [tenant ] | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -27491,7 +27490,7 @@ show stats aggregate-session by-tenant bandwidth-received-tcp-forward [tenant ] | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -27576,7 +27575,7 @@ show stats aggregate-session by-tenant bandwidth-received-udp-forward [tenant ] [since ] [ | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -27686,7 +27685,7 @@ show stats aggregate-session by-tenant bandwidth-transmitted-forward [tenant ] [since ] [since ] [ | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28056,7 +28055,7 @@ show stats aggregate-session by-tenant bytes-dropped-forward [tenant ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28086,7 +28085,7 @@ show stats aggregate-session by-tenant bytes-dropped-other-protocol-forward [ten | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28116,7 +28115,7 @@ show stats aggregate-session by-tenant bytes-dropped-other-protocol-reverse [ten | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28146,7 +28145,7 @@ show stats aggregate-session by-tenant bytes-dropped-reverse [tenant ] [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28176,7 +28175,7 @@ show stats aggregate-session by-tenant bytes-dropped-tcp-forward [tenant ] [s | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28325,7 +28324,7 @@ show stats aggregate-session by-tenant bytes-received [tenant ] [since < | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28355,7 +28354,7 @@ show stats aggregate-session by-tenant bytes-received-forward [tenant ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28385,7 +28384,7 @@ show stats aggregate-session by-tenant bytes-received-other-protocol [tenant ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28504,7 +28503,7 @@ show stats aggregate-session by-tenant bytes-received-tcp [tenant ] [sin | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28534,7 +28533,7 @@ show stats aggregate-session by-tenant bytes-received-tcp-forward [tenant ] [sin | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28623,7 +28622,7 @@ show stats aggregate-session by-tenant bytes-received-udp-forward [tenant ] [since ] [sinc | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28741,7 +28740,7 @@ show stats aggregate-session by-tenant bytes-transmitted-forward [tenant ] [ | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -28920,7 +28919,7 @@ show stats aggregate-session by-tenant bytes-transmitted-tcp-forward [tenant ] [ | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29009,7 +29008,7 @@ show stats aggregate-session by-tenant bytes-transmitted-udp-forward [tenant ] [since ] [since ] | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29123,7 +29122,7 @@ show stats aggregate-session by-tenant packets-dropped-forward [tenant ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29153,7 +29152,7 @@ show stats aggregate-session by-tenant packets-dropped-other-protocol-forward [t | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29183,7 +29182,7 @@ show stats aggregate-session by-tenant packets-dropped-other-protocol-reverse [t | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29213,7 +29212,7 @@ show stats aggregate-session by-tenant packets-dropped-reverse [tenant ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29243,7 +29242,7 @@ show stats aggregate-session by-tenant packets-dropped-tcp-forward [tenant ] | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29388,7 +29387,7 @@ show stats aggregate-session by-tenant packets-received [tenant ] [since | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29414,7 +29413,7 @@ show stats aggregate-session by-tenant packets-received-forward [tenant | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29444,7 +29443,7 @@ show stats aggregate-session by-tenant packets-received-other-protocol [tenant < | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29470,7 +29469,7 @@ show stats aggregate-session by-tenant packets-received-other-protocol-forward [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29500,7 +29499,7 @@ show stats aggregate-session by-tenant packets-received-other-protocol-reverse [ | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29530,7 +29529,7 @@ show stats aggregate-session by-tenant packets-received-reverse [tenant | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29559,7 +29558,7 @@ show stats aggregate-session by-tenant packets-received-tcp [tenant ] [s | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29585,7 +29584,7 @@ show stats aggregate-session by-tenant packets-received-tcp-forward [tenant ] [s | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29670,7 +29669,7 @@ show stats aggregate-session by-tenant packets-received-udp-forward [tenant ] [since ] [si | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29780,7 +29779,7 @@ show stats aggregate-session by-tenant packets-transmitted-forward [tenant ] | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29951,7 +29950,7 @@ show stats aggregate-session by-tenant packets-transmitted-tcp-forward [tenant < | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -29981,7 +29980,7 @@ show stats aggregate-session by-tenant packets-transmitted-tcp-reverse [tenant < | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30010,7 +30009,7 @@ show stats aggregate-session by-tenant packets-transmitted-udp [tenant ] | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30036,7 +30035,7 @@ show stats aggregate-session by-tenant packets-transmitted-udp-forward [tenant < | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30066,7 +30065,7 @@ show stats aggregate-session by-tenant packets-transmitted-udp-reverse [tenant < | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30095,7 +30094,7 @@ show stats aggregate-session by-tenant packets-udp [tenant ] [since ] [s | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30145,7 +30144,7 @@ show stats aggregate-session by-tenant session-count [tenant ] [since ] | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30196,7 +30195,7 @@ show stats aggregate-session by-tenant tcp-bad-flag-combinations [tenant ] [sin | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30316,7 +30315,7 @@ show stats aggregate-session by-tenant tcp-duplicate-acks-forward [tenant ] [sinc | force | Skip confirmation prompt. Only required when targeting all routers | | node | The name of the node generating this metric | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30496,7 +30495,7 @@ show stats aggregate-session by-tenant tcp-out-of-window-forward [tenant ] [since ] [si | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30614,7 +30613,7 @@ show stats aggregate-session by-tenant tcp-resets-received-forward [tenant ] | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30703,7 +30702,7 @@ show stats aggregate-session by-tenant tcp-resets-transmitted-forward [tenant ] [si | ---- | ----------- | | force | Skip confirmation prompt. Only required when targeting all routers | | router | The router for which to display stats (default: <current router>) | -| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp] | +| since | The displayed stats will be calculated as a delta from the given time. The given time can either be a timestamp or a delta, such as 45m, 1d, or 1mo. Providing "launch" ensures that no start time for the delta is set [type: timestamp]. The since argument (command) is a general utility which performs a delta between the two values supplied by the arguments. The primary use is for cumulative metrics - ones that keep incrementing. aggregate-session are rate metrics which return a per 5 second view of the stat. Rate in the past could be higher then the current rate (or rate at the selected time) and a negative value may be returned. | | tenant | The name of the tenant generating this metric (comma-separated list) | ##### Positional Arguments @@ -30787,7 +30786,7 @@ show stats aggregate-session by-tenant tcp-retransmissions-received [tenant `remote` > `host` fields, the plugin will not start the tunnels if the FQDNs of the tunnels are unresolvable. + +- **WAN-1848** Tunnel monitoring failures did not cause traffic failover to other tunnels. + + _**Resolution:**_ If tunnel monitoring is configured, the tunnel monitoring status will be tied into the ingress KNI's operational status which will cause traffic to failover. + +- **WAN-2648** Excessive logging in `ipsec-controller` journal. + + _**Resolution:**_ Reduced logging to provide a simplified journal. + +- **WAN-2994** Port 500 sessions were stuck even with session deletion feature. + + _**Resolution:**_ Delete the port 500 and 4500 sessions whenever the tunnel does not come up. + ### Release 3.6.0 **Release Date:** Oct 13, 2023 diff --git a/docs/release_notes_wan_assurance_plugin_3.8.md b/docs/release_notes_wan_assurance_plugin_3.8.md new file mode 100644 index 0000000000..04d14c90b7 --- /dev/null +++ b/docs/release_notes_wan_assurance_plugin_3.8.md @@ -0,0 +1,66 @@ +--- +title: WAN Assurance Plugin 3.8 Release Notes +sidebar_label: '3.8' +--- +## Release 3.8.0 + +**Release Date:** June 04, 2024 + +### New Features +- **WAN-2632 Display the interface description on MIST UI** + +Any description configured under the `device-interface` will be displayed on the WAN Edge view on MIST UI. + +- **WAN-2309 Generate an alarm when device fails to register with MIST** + +A new alarm will be generated when a device is unable to register with the MIST cloud during initial onboarding and will include the failure reason. + +### Resolved Issues + +- **WAN-2839 The `show mist` command sometimes reports inaccurate status** + + _**Resolution:**_ The logic to detect the connection down state and reason was made more robust to capture additional scenarios. + +- **WAN-2842 LTE interface missing tx/rx_bps** + + _**Resolution:**_ The rx/tx bps for interfaces will now average the value across the 3 minute oc-stats window as opposed to sending a single snapshot at time of data collection. + +- **WAN-2853 Same interface is reported twice under different names** + + _**Resolution:**_ For conductor managed devices runnning on Juniper branded hardware, the logic now accounts for custom user defined device names for HA sync and HA fabric interfaces. + +- **WAN-2991 DHCP pool exhaustion event not being generated** + + _**Resolution:**_ The DHCP pool exhaustion event generation better accounts for the previous event status to accurately generate the event. + +- **WAN-3000 Process data collection spamming the logs** + + _**Resolution:**_ The logs were updated to be less aggressive. + +- **WAN-3001 TSI collection times out on certain devices** + + _**Resolution:**_ TSI collection is handled more efficiently by limiting the amount of CPU and memory the collection can consume and affording more time for the operation to complete. + +- **WAN-3003 For port errors, same value is being reported for both nodes in an HA pair** + + _**Resolution:**_ Each node will report the local error counts for a given port. + +- **WAN-3049 Probe up/down events are generated even when the physical WAN port is down** + + _**Resolution:**_ The probe up/down events are suppressed for a physical down port. + +- **WAN-3053 Duplicate path add/remove events being generated for HA interfaces** + + _**Resolution:**_ The path add/remove events will be suppressed for fabric interfaces + +- **WAN-3072 Path Up events related to Application Path insights have incorrect reason** + + _**Resolution:**_ Remove the reason code from path up events since the previous Path Down will always have the correct reason code. + +- **WAN-3077 DHCP pool events are missing the pool name** + + _**Resolution:**_ Add the pool name for DHCP pool events in addition to the DHCP pool udpates. + +- **WAN-3104 Duplicate LTE interface with null stats being reported** + + _**Resolution:**_ The logic to detect LTE interfaces for conductor managed whitebox devices was made more robust to handle user configured device names. diff --git a/kb/2024-05-29-I95-56484.md b/kb/2024-05-29-I95-56484.md new file mode 100644 index 0000000000..2afb00eef3 --- /dev/null +++ b/kb/2024-05-29-I95-56484.md @@ -0,0 +1,93 @@ +--- +title: High Memory usage for application-director +date: 2024-5-29 +tags: ['6.2.3', '6.2.4'] +hide_table_of_contents: false +--- + +Changes to use a new database in the app-id engine have introduced high memory utilization for the application-director. + + + +**Issue ID:** I95-56484 + +**Last Updated:** 2024-05-29 + +**Introduced in SSR Version:** 6.2.3 + +### Problem +The application-director has a race condition that can occur during app-id module updates, app-id database reloads, and configuration changes. + +It is possible that stale connections to a database will utilize excessive memory over a long duration (application-director uptime). + +The administrator might notice alarms for high system memory and an Application Director alarm with the message `IP Database reload failed.` + +### Release Notes +Resolve application-director stale database connection memory leak. + +### Severity +
+The potential impact of a software defect if encountered. Severity levels are: +* Critical: Could severely affect service, capacity/traffic, and maintenance capabilities. May have a prolonged impact to the entire system. +* Major: Could seriously affect system operation, maintenance, administration and related tasks. +* Minor: Would not significantly impair the functioning or affect service. +
+Major + +### Status +Resolved + +### Resolved In +6.2.5 + +### Product +SSR + +### Functional Area +System Health + +### Workaround +
+Juniper may provide a method to temporarily circumvent a problem; workarounds do not exist for all issues. +
+Utilizing SSR metrics data, custom charts can be used to view memory usage over time to identify processes that are increasing. Also, the PCLI provides a way to view current process memory utilization and a way to compare the current value a previous point in time. + +``` +admin@node.router# show stats process memory process-name application-director +Thu 2024-05-30 20:38:03 UTC +✔ Retrieving statistics... + +Process Memory Metrics +---------------------- + +======== ====== ====================== ============ + Metric Node Process-name Value +======== ====== ====================== ============ + rss node application-director 61681664 + vsz node application-director 1589444608 + ``` + +The above values will appear as bytes. Shown below is comparing the current value to 10 days prior. + +``` +admin@node.router# show stats process memory process-name application-director since 10d +Thu 2024-05-30 20:52:39 UTC +✔ Retrieving statistics... + +Since: 2024-05-20 20:52:39 + +Process Memory Metrics +---------------------- + +======== ====== ====================== ========= + Metric Node Process-name Value +======== ====== ====================== ========= + rss node application-director 1171456 + vsz node application-director 0 +``` + +In this case, the delta is 10Mb which is normal operating behavior. + +However, if the deltas over time are increasing significantly such that the current utilization has doubled or tripled, this is a good indicator that this issue is occurring. + +If you have confirmed the `application-director` has significant memory increases over time, the service can be restarted on the offending device using `systemctl restart application-director` as a privileged User. diff --git a/sidebars.js b/sidebars.js index 6e9657053c..7351213fd1 100644 --- a/sidebars.js +++ b/sidebars.js @@ -386,6 +386,7 @@ module.exports = { "type": "category", "label": "WAN Assurance", "items": [ + "release_notes_wan_assurance_plugin_3.8", "release_notes_wan_assurance_plugin_3.7", "release_notes_wan_assurance_plugin_3.6", "release_notes_wan_assurance_plugin_3.5", diff --git a/static/img/nmtui-linux-b-static-ipv4-config.png b/static/img/nmtui-linux-b-static-ipv4-config.png index b5cbbc13cb..96fc262ba5 100644 Binary files a/static/img/nmtui-linux-b-static-ipv4-config.png and b/static/img/nmtui-linux-b-static-ipv4-config.png differ