1 個回答
- 最新
- 最多得票
- 最多評論
0
What is the retention policy you have set for the logs? - Could it be that they have expired and that they are just showing as a result of some cached value? Also, does this happen on other browsers/machines? Lastly, have you tried accessing the logs via API instead?
已回答 1 年前
相關內容
AWS 官方已更新 1 年前
Hi thanks for responding - Retention policy is set to never expire. I have previously been able to view past log groups, and the log groups in question are less than a week old.
I have tried this on Firefox, Chome and Edge, all with the same results, I haven't tested on another machine yet though.
I have not tried the API yet either
Also there is this error in the web console
Unhandled rejection fail@https://a.b.cdn.console.awsstatic.com/a/v1/LWD5NV3DAV6SISCOQ2K2UUURFXDM3EKHF4ROIJW27IZYEJZFEIAQ/9614.min.js:1:38091 validateStructure@https://a.b.cdn.console.awsstatic.com/a/v1/LWD5NV3DAV6SISCOQ2K2UUURFXDM3EKHF4ROIJW27IZYEJZFEIAQ/9614.min.js:1:38315 validateMember@https://a.b.cdn.console.awsstatic.com/a/v1/LWD5NV3DAV6SISCOQ2K2UUURFXDM3EKHF4ROIJW27IZYEJZFEIAQ/9614.min.js:1:38700 validate@https://a.b.cdn.console.awsstatic.com/a/v1/LWD5NV3DAV6SISCOQ2K2UUURFXDM3EKHF4ROIJW27IZYEJZFEIAQ/9614.min.js:1:37747 472274/i.EventListeners.Core</<@https://a.b.cdn.console.awsstatic.com/a/v1/LWD5NV3DAV6SISCOQ2K2UUURFXDM3EKHF4ROIJW27IZYEJZFEIAQ/9614.min.js:1:13572 callListeners@https://a.b.cdn.console.awsstatic.com/a/v1/LWD5NV3DAV6SISCOQ2K2UUURFXDM3EKHF4ROIJW27IZYEJZFEIAQ/9614.min.js:1:65467 a@https://a.b.cdn.console.awsstatic.com/a/v1/LWD5NV3DAV6SISCOQ2K2UUURFXDM3EKHF4ROIJW27IZYEJZFEIAQ/9614.min.js:1:65353 472274/i.EventListeners.Core</</<@https://a.b.cdn.console.awsstatic.com/a/v1/LWD5NV3DAV6SISCOQ2K2UUURFXDM3EKHF4ROIJW27IZYEJZFEIAQ/9614.min.js:1:12583 n@https://a.b.cdn.console.awsstatic.com/