Description
For sites with multiple archives that serve different purposes (Pipeline) and for EA nodes in a multi-tenant configuration (ASP and Cloud) trouble shooting an issue for 1 customer or 1 archive for example, can be very difficult when that EA node is receiving and sending data to and from other tenants meant for other archives than the one under investigation. In these cases it would be very helpful to have an option in EA to separate the logging per archive. This could help service more easily filter out logging to the relevant archive and potentially narrow down the time taken to resolve an issue. |
For sites with multiple archives that serve different purposes (Pipeline) and for EA nodes in a multi-tenant configuration (ASP and Cloud) trouble shooting an issue for 1 customer or 1 archive for example, can be very difficult when that EA node is receiving and sending data to and from other tenants meant for other archives than the one under investigation. In these cases it would be very helpful to have an option in EA to separate the logging per archive. This could help service more easily filter out logging to the relevant archive and potentially narrow down the time taken to resolve an issue.