On Fri, Apr 30, 2021 at 10:03:49PM -0500, Scott Cheloha wrote:
> > On Apr 28, 2021, at 03:47, Claudio Jeker wrote:
> >
> > There are various time fields in the JSON output.
> > last_read, last_write, last_updown on sessions, last_update for rib
> > entries and last_change for sets. Currently the
> On Apr 28, 2021, at 03:47, Claudio Jeker wrote:
>
> There are various time fields in the JSON output.
> last_read, last_write, last_updown on sessions, last_update for rib
> entries and last_change for sets. Currently the value is the fmt_timeframe
> string (which looks something like 7w3d12h)
Claudio Jeker(cje...@diehard.n-r-g.com) on 2021.04.28 10:45:20 +0200:
> There are various time fields in the JSON output.
> last_read, last_write, last_updown on sessions, last_update for rib
> entries and last_change for sets. Currently the value is the fmt_timeframe
> string (which looks somethin
There are various time fields in the JSON output.
last_read, last_write, last_updown on sessions, last_update for rib
entries and last_change for sets. Currently the value is the fmt_timeframe
string (which looks something like 7w3d12h) and is hard to parse for
machines. Include an additional _sec