- 最新
- 投票最多
- 评论最多
UPDATE: I found them! It looks like the link to the logs has now moved to the bottom of the Job Attempts tab in the individual Child Job (I don't usually look at that, so that's why I missed it). I guess this is its new home now?!
It sounds like there might be a temporary issue with the AWS Batch console or a change in the user interface that you're not aware of. Here are a few steps you can take to troubleshoot this:
-
Sometimes, simply refreshing the AWS Management Console can resolve temporary glitches.
-
Try accessing the console in a different browser or in incognito/private mode to rule out any browser-specific issues.
-
If you're unable to access the logs through the console, you can use the AWS Command Line Interface (CLI) or one of the AWS SDKs to retrieve the logs. For example, if your jobs are writing logs to Amazon CloudWatch Logs, you can use the
aws logs
CLI commands to view the logs. -
Visit the AWS Service Health Dashboard to see if there are any ongoing issues with AWS Batch or related services in your region.
- Tried refreshing (and Ctrl+F5) and logging out and back in again, no change. Someone else in my organisation also reported seeing the same thing yesterday (not sure if the link came back for them or not).
- Tried accessing it from a different computer, same result - the log link is gone.
- I can see the logs on the Cloudwatch console but this is not a convenient way to find the log for a specific job.
- no issues in the Health in any of our regions (we have jobs running in two regions, the log links are gone in both regions)
Either it's a weird (and hopefully temporary) glitch or Amazon have changed something here... :(
Noticed the exact same problem today. It was okay a few days back. The logs can be still found in CloudWatch, but the link in job Details
tab in Batch console is gone.
AWS, please bring it back!
I found them, the link should now be in the Job Attempts tab for the individual Child Job (see my screencap above)
相关内容
- AWS 官方已更新 7 个月前
- AWS 官方已更新 1 年前
The
Job attempts
or theLogging
panel has another problem. If the job has been retried for whatever reason, it shows the logs for previous attempts only, not the current running one. There seems no way to find the link for the current attempt except search it in CloudWatch.