Help, the links to my batch job logs have suddenly disappeared!

0

Previously when I wanted to check a batch job log I would click on the job, click the Child Jobs tab, click an individual job there and click on a link in the top left corner of the child job page and that would load up the log for that job. Now all of a sudden that link has gone! What's happened? How am I supposed to see the logs for the jobs now? Now I can't see any links to any jobs in the past either.

This literally was working fine a few hours ago and now it's all disappeared (it's 8:07pm PST here - did AWS decide to change something at midnight UTC Feb 29?)

If it is a deliberate change in the interface then how am I supposed to access specific logs for specific jobs now? (Did anyone even ask for this? Why would they suddenly make it harder to access this information?)

EDIT: Ah, I think I found it! It looks like the link to the logs has now moved to the bottom of the Job Attempts tab in the Child Job (I don't usually look at that, so that's why I missed it). Is that its new home now?

cthomas
已提問 2 個月前檢視次數 195 次
3 個答案
1
已接受的答案

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?!

links to Log files are in Job Attempts tab now

cthomas
已回答 2 個月前
profile picture
專家
已審閱 2 個月前
  • The Job attempts or the Logging 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.

0

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:

  1. Sometimes, simply refreshing the AWS Management Console can resolve temporary glitches.

  2. Try accessing the console in a different browser or in incognito/private mode to rule out any browser-specific issues.

  3. 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.

  4. Visit the AWS Service Health Dashboard to see if there are any ongoing issues with AWS Batch or related services in your region. AWS Service Health Dashboard

profile picture
專家
已回答 2 個月前
    1. 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).
    2. Tried accessing it from a different computer, same result - the log link is gone.
    3. I can see the logs on the Cloudwatch console but this is not a convenient way to find the log for a specific job.
    4. 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... :(

0

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!

zubiao
已回答 2 個月前
  • I found them, the link should now be in the Job Attempts tab for the individual Child Job (see my screencap above)

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南