On 1/13/25 5:13 PM, Ali Zamani wrote:
Hi,
* I can see guacamole history tab in admin dashboard shows max 40
pages of 25 rows per page i.e. 1000 records. However, this is
different in the actual database. Is this due to limitation applied
in frontend design?
No, it's a decision that was made when designing the REST API of the
backend. The search results from the database are intentionally limited
to the first 1000 results to avoid taxing the database if the history is
extensive (NOTE: which results are "first" will depend on what you've
searched for and the sorting order that you've chosen).
We chose 1000 because that produces 40 pages of results in the UI, which
already feels like an unrealistically large number of results to search
through manually. A user that needs more results than that would
naturally also need something to digest those results further before
they can be meaningfully consumed, which would mean SQL.
* Also, when a user is deleted, actual history remains in database and
is still shown when navigating through history page, but when
filtering history records based on that user in guacamole web UI, no
records shown after deletion. Is this a bug?
Not exactly. It's a known, intentional limitation of the search
performed for connection history.
History records are maintained so that they can be used by
administrators for auditing. This includes history records for users
that no longer exist. You can only search for history entries based on
usernames if those users are in the database because that query is
significantly faster if it can be limited to only users that are indexed
by the users table.
If you need to produce reports for users that have been deleted, you
would need to use SQL.
- Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
