Stale/outdated output from "fly checks list"

1

I’m playing around with Postgres, trying out scenarios with a forced failover. What I am seeing is outdated output e.g.:

$ fly checks list
  NAME | STATUS  | ALLOCATION | REGION | TYPE | LAST UPDATED | OUTPUT
-------*---------*------------*--------*------*--------------*---------------------------------------------------------------------------
[...]
  role | passing | 970902b6   | lhr    | HTTP | 15m28s ago   | leader[✓]

The last updated is over 15 minutes ago, but as I understand from fly.toml this should be a much shorter interval:

[checks]
# ...
  [checks.role]
    grace_period = "30s"
    headers = []
    interval = "15s"
    method = "get"
    path = "/flycheck/role"
    port = 5500
    protocol = "http"
    restart_limit = 0
    timeout = "10s"
    tls_skip_verify = false
    type = "http"

If it’s running this every 15s, how can I see that more recent output in fly checks list?

3

Hi @jays !

The ‘Last Updated’ column means the last time this output changed rather than the last time it checked.

Naming is hard! :laughing:

1 Like