I struggled to find out why I couldn't get SQL queries to work on my otherwise functioning custom log file.
When trying out another custom log file from a PR I realized that my file was called postgresCustom.json and all other log files were ending in _log.json (mine wasn't).
When I added the magic _log.json SQL finally started working!
Mentioning this in the docs is a good start. It would be even better if this was validated and logged in the debug logs.
For example, I created the custom config via the regex101 importer like this:
The importer should have either complained that I must end the file name in _log, e.g. postgresCustom_log, or it should have simply appended that _log suffix.
I struggled to find out why I couldn't get SQL queries to work on my otherwise functioning custom log file.
When trying out another custom log file from a PR I realized that my file was called
postgresCustom.jsonand all other log files were ending in_log.json(mine wasn't).When I added the magic
_log.jsonSQL finally started working!Mentioning this in the docs is a good start. It would be even better if this was validated and logged in the debug logs.
For example, I created the custom config via the regex101 importer like this:
The importer should have either complained that I must end the file name in
_log, e.g.postgresCustom_log, or it should have simply appended that_logsuffix.