There are three logs which generate logs in the millions per day. These three logs are for the same indexing event and represent: Start, finish, time to visibility.
The change here is to introduce a new configuration allowing Indexer to issue a single log entry when reporting time to visibility with additional information found in the start/stop log entries. This new log is also in json and is as short as possible.
There are also Kondo updates in this change.
Checklist
[x] I have updated/added unit and integration tests that prove my fix is effective or that my feature works
[x] New and existing unit and int tests pass locally and remotely with my changes
[x] I have removed unnecessary/dead code and imports in files I have changed
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[-] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[-] I have cleaned up integration tests by doing one or more of the following:
de-duped, consolidated, removed dead int tests
transformed applicable int tests into unit tests
refactored to reduce number of system state resets by updating fixtures (use-fixtures :each (ingest/reset-fixture {})) to be :once instead of :each
Overview
What is the feature/fix?
Please summarize the feature or fix.
What is the Solution?
There are three logs which generate logs in the millions per day. These three logs are for the same indexing event and represent: Start, finish, time to visibility.
The change here is to introduce a new configuration allowing Indexer to issue a single log entry when reporting time to visibility with additional information found in the start/stop log entries. This new log is also in json and is as short as possible.
There are also Kondo updates in this change.
Checklist