Our users create painfully complex Custom segments with large amounts of data. This can cause performance issues for other users.
We have browser triggering disabled but custom segments trigger archiving anyway, as described here:
When we enable this option, the custom segments are no longer processed by the browser and they are also not processed by the archiver.
; disable browser trigger archiving for all requests (even those with a segment) browser_archiving_disabled_enforce = 1
I suspect that is due to the “auto_archive” option that a) I can see in the database and b) root users can see, but c) our users can not see.
This means all of their custom segments are set to “Auto_archive” = 0.
To the questions:.
- How can I ensure that all segments are auto_archive=1 automatically going forward?
- Is there a way to ensure that API calls with a custom segment definition get archived so they return faster in the future?