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
I am working with the cloud metrics team to ingest the UAT CloudWatch logs into the cloud metrics platform to capture specific metrics. The timeseries Lambda logs the response it sends to the user and if the user requested a full geoJSON response, it logs all coordinates which is causing issues with ingestion as the log statement size is too large. We need to modify the response so that it does not display the full coordinates or displays less significant figures.
The text was updated successfully, but these errors were encountered:
The error logging in the timeseries Lambda also needs to be modified so that it consistently logs all HTTP codes and error messages for each type of error encountered.
I am working with the cloud metrics team to ingest the UAT CloudWatch logs into the cloud metrics platform to capture specific metrics. The timeseries Lambda logs the response it sends to the user and if the user requested a full geoJSON response, it logs all coordinates which is causing issues with ingestion as the log statement size is too large. We need to modify the response so that it does not display the full coordinates or displays less significant figures.
The text was updated successfully, but these errors were encountered: