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
Ideally the logging capabilities for the storage backends should include information for individual files in order to help debug any issues with downloads. It might be worth checking if the existing logs are available to all ACED developers and analysts.
In the long term this logging will be required for MinIO, Wasabi, and Ceph storage endpoints.
Setting up one common logging target such as Splunk for the entire Gen3 system is worth looking into as well as that would create a single source for access logs.
The text was updated successfully, but these errors were encountered:
Following the lead on this with @burcheja to extract logs from the k8s pods on AWS and forward them to the internal Splunk endpoint. This will go a long way with improving overall status monitoring as well!
Configured the system and audit loggers on the MinIO server to send data to Splunk. Looks like we need some ACLs updated to allow the logging data to flow as expected.
Ideally the logging capabilities for the storage backends should include information for individual files in order to help debug any issues with downloads. It might be worth checking if the existing logs are available to all ACED developers and analysts.
In the long term this logging will be required for MinIO, Wasabi, and Ceph storage endpoints.
Setting up one common logging target such as Splunk for the entire Gen3 system is worth looking into as well as that would create a single source for access logs.
The text was updated successfully, but these errors were encountered: