Difference between number of "stated" logs and actual logs

[Erasure5959]

Hello,

I often see a difference between what is stated as the number of logs and the number of available logs. Not really sure how to phrase this correctly, but hopefully the below screenshot helps to illustrate things:

In this screenshot, the page says there are 2 logs available, but in reality there are far more (I cut the snip short as I felt this was sufficient to illustrate the point). There are two filters applied here, but either way the actual number is significantly higher than 2 logs.

I also see the reverse sometimes: the page may say 4 logs, or 1-4 of 4 logs, but only one or two will be visible.

Is this amount calculated over a specific timeframe? In the screenshot above (and default) it goes to 24 hours, so I would imagine the total would be for that time period.

I don't know if this is a bug, expected behaviour or a configuration issue on my side. Any guidance would be much appreciated.

[Polliog]

Confirmed: the displayed total comes from an estimated count. On TimescaleDB (the default engine) it uses the Postgres query planner row estimate, which can be off in both directions, especially at small scale with stale table statistics. The listed logs themselves are exact. We'll make the count accurate at low volumes.

[Erasure5959]

Apologies for not including that information - I am using TimescaleDB.