Use header X-Request-Id, or create a new uuid when no present, to identyfy log entries
Be able to set log level from env variable LOG_LEVEL, useful while testing: LOG_LEVEL=info npm test; even more human-readable: LOG_LEVEL=info npm t | ./node_modules/.bin/pino-pretty
Be able to reduce the footprint in the final log file depending on the environment
Use one logger for every service: Queries, Batch Queries (Jobs), and Data Ingestion (CopyTo/CopyFrom)
Stop using headers such as: X-SQL-API-Log, X-SQL-API-Profiler, and X-SQL-API-Errors as a way to log info.
Be able to tag requests with labels as an easier way to provide business metrics
Metro: Add log-collector utility (metro), it will be moved to its own repository. Attaching it here fro development purposes. Try it with the following command LOG_LEVEL=info npm t | node metro
Metro: Creates metrics-collector.js a stream to update Prometheus' counters and histograms and exposes them via Express' app (:9145/metrics). Use the ones defined in grok_exporter
Announcements:
The profiler is always set. No need to check its existence anymore
Unify profiler usage for every endpoint
Bug fixes:
Avoid hung requests while fetching user identifier
Breaking changes:
X-Request-Id, or create a newuuidwhen no present, to identyfy log entriesLOG_LEVEL, useful while testing:LOG_LEVEL=info npm test; even more human-readable:LOG_LEVEL=info npm t | ./node_modules/.bin/pino-prettyX-SQL-API-Log,X-SQL-API-Profiler, andX-SQL-API-Errorsas a way to log info.metro), it will be moved to its own repository. Attaching it here fro development purposes. Try it with the following commandLOG_LEVEL=info npm t | node metrometrics-collector.jsa stream to update Prometheus' counters and histograms and exposes them via Express' app (:9145/metrics). Use the ones defined ingrok_exporterAnnouncements:
Bug fixes:
cc @ilbambino