Livestatus Proxy Caching

We are using checkmk enterprise with livestatus proxy.

The Caching ensures that static queries need only be responded-to once by the slave, and from that point of time can be responded to directly and locally, without delay. An example of this is the list of monitored hosts required by Quicksearch . (https://checkmk.com/cms_distributed_monitoring.html#livestatusproxy)

How long this caching is stored?
what happens when a new host is added?
when it is updated?
What are the other examples where this livestatus caching is used?
Local caching of queries that deliver static data. Any other examples?

I think this is more a questions for the dev team im Munich @fayepal

1 Like

Hi @shivdev14,

I asked the devs and if I understood correctly, query results are cached until the core config is reloaded.