You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.
In the current version, the library is storing the event receive time and event insert time into the database.
It would be useful to add an option to be able to enable this feature only on-demand.
It appears that these timestamps do not seem to be very useful since the EventSubscriber is already monitoring the min and max processing time. Disabling this feature could help saving quite a lot of space.
The text was updated successfully, but these errors were encountered:
Config variable store_diag_times was added. Default is true, to maintain like behaviour with the current module. When set to false, it will stop storing diagtimes. Code can be traced with this flag.
Intention is to move this to default false in the future.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the current version, the library is storing the event receive time and event insert time into the database.
It would be useful to add an option to be able to enable this feature only on-demand.
It appears that these timestamps do not seem to be very useful since the EventSubscriber is already monitoring the min and max processing time. Disabling this feature could help saving quite a lot of space.
The text was updated successfully, but these errors were encountered: