As it stands, the logging in the dcs-package-ingest code is deficient when it comes to troubleshooting errors related to deposit. Even though errors typically produce a stacktrace, it can be difficult to ascertain what the root cause of a failed deposit it.
Since the package ingest service is in its formative stages, I'd like to see some more verbose logging present in the codebase, perhaps enabled by default (e.g. shipping with a logback.xml that has DEBUG enabled). I think this would facilitate debugging deposit errors, especially for users of the package ingest service, because the logs would have everything needed by the developers in order to determine the root cause of an issue.
As it stands, the logging in the dcs-package-ingest code is deficient when it comes to troubleshooting errors related to deposit. Even though errors typically produce a stacktrace, it can be difficult to ascertain what the root cause of a failed deposit it.
Since the package ingest service is in its formative stages, I'd like to see some more verbose logging present in the codebase, perhaps enabled by default (e.g. shipping with a logback.xml that has DEBUG enabled). I think this would facilitate debugging deposit errors, especially for users of the package ingest service, because the logs would have everything needed by the developers in order to determine the root cause of an issue.