CLI shows 0s cache duration

[jasonkeene]

This seems odd.

Source ID                             Count   Expired  Cache Duration
...
loggregator-router-84ccbb8479-57bcl   36      0        1s
loggregator-router-84ccbb8479-768bq   35      0        2s
loggregator-router-84ccbb8479-cp92t   31      0        0s
loggregator-router-84ccbb8479-lkrlz   27      0        0s
...

There is for sure data there.

$ lc tail loggregator-router-84ccbb8479-lkrlz
Retrieving logs for loggregator-router-84ccbb8479-lkrlz...

2018-05-21T09:24:27.29-0600 [loggregator-router-84ccbb8479-lkrlz] LOG/ERR 2018/05/21 15:23:49 pprof bound to: 127.0.0.1:6062
2018-05-21T09:24:27.29-0600 [loggregator-router-84ccbb8479-lkrlz] LOG/ERR 2018/05/21 15:23:49 health bound to: 127.0.0.1:6063
...
2018-05-21T09:24:27.30-0600 [loggregator-router-84ccbb8479-lkrlz] LOG/ERR 2018/05/21 15:23:48 Metrics endpoint is listening on 0.0.0.0:6061
2018-05-21T09:24:27.30-0600 [loggregator-router-84ccbb8479-lkrlz] LOG/ERR 2018/05/21 15:23:48 pprof bound to: 127.0.0.1:6060

Curl shows a time range, probably sub-second.

pivotal@crabapple playground $ curl -s $LOG_CACHE_ADDR/v1/meta | jq '.meta | .["loggregator-router-84ccbb8479-lkrlz"]'
{
  "count": "27",
  "oldest_timestamp": "1526916267291597824",
  "newest_timestamp": "1526916267302521088"
}

I would expect the CLI to display this as a sub-second duration.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/157747397

The labels on this github issue will be updated when the story is started.