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
When an error occurs or an exception is thrown from an Aggie instance, it logs that error or exception to a Slack channel and email address. However, if multiple instances were to be deployed at the same time, the team monitoring each would have no idea which instance the log came from.
A simple fix: I propose that we include an instanceId field in the config/secrets.json file that would prefix any logs sent to the active maintenance team.
The text was updated successfully, but these errors were encountered:
When an error occurs or an exception is thrown from an Aggie instance, it logs that error or exception to a Slack channel and email address. However, if multiple instances were to be deployed at the same time, the team monitoring each would have no idea which instance the log came from.
A simple fix: I propose that we include an
instanceId
field in theconfig/secrets.json
file that would prefix any logs sent to the active maintenance team.The text was updated successfully, but these errors were encountered: