geostore
geostore copied to clipboard
Logging: Add a 'correlation' id
To assist in troubleshooting and tracing issues back to root log / root problem, we want to add a correlation ID to all logs
Should be correlated by a user action, i.e. triggering a lambda endpoint (dataset, dataset version, import status).
To assist in troubleshooting and tracing issues back to root log / root problem, we want to add a correlation ID to all logs
Should be correlated by a user action, i.e. triggering a lambda endpoint (dataset, dataset version, import status).
The Correlation IDs is famous for microservices architectures when you have many services calling each others and you want to track the logs using uniquely ID for fast troubleshooting. I think we need to be sure how it will be helpful here.