Record changes to advanced search options in UXActionLog

[flodolo]

Analyzing the log for #3503 is not particularly useful, because we have too much noise coming from bots.

As a first step, I think it would be enough to record an action when the user clicks "apply search options" in the dropdown, recording as metadata: locale, project, search_* parameters set to true.

This would give us a sense of which options are used, and how frequently.

Measuring how frequently the menu is used compared to the standard search doesn't seem useful, since the options persist once set.

[flodolo]

Measuring how frequently the menu is used compared to the standard search doesn't seem useful, since the options persist once set.

Rethinking about this: maybe it makes sense to track how many searches are performed through the search field, and store as metadata the advanced search options, on top of the main filters (string statuses, extra filters). That would give us a better picture, but it would also be a lot more data.

As for the last point, maybe we need a retention policy for the UXActionLog (e.g. 2 years?).

[mathjazz]

As for the last point, maybe we need a retention policy for the UXActionLog (e.g. 2 years?).

We could do something like this:
https://mozilla-pontoon.readthedocs.io/en/latest/admin/deployment.html#sync-log-retention

OTOH, the uxactionlog_uxactionlog table size is small:

public.insights_projectlocaleinsightssnapshot | 4197 MB
public.base_translation                       | 4137 MB
public.base_translationmemoryentry            | 2016 MB
public.notifications_notification             | 1498 MB
public.django_session                         | 1338 MB
public.actionlog_actionlog                    | 884 MB
public.insights_localeinsightssnapshot        | 227 MB
public.base_entity                            | 90 MB
public.uxactionlog_uxactionlog                | 54 MB
public.sync_projectsynclog                    | 52 MB
public.base_translatedresource                | 51 MB
...