- 最新
- 投票最多
- 评论最多
The documentation does not explicitly state so, but OR filters can also apply to whole phrases instead of just standalone words.
?"Event 1" ?"Event 2"
So have to fall back to plain text-phrase matching instead of JSON selector matching.
Edited by: icelava on Oct 6, 2021 4:28 AM
I need to filter on JSON properties with @ as a prefix as well. Can Amazon come out and explicitly say whether they don't support fields which start with special characters and that it was a significant oversight or give us a way around this? It's already painful to use this tool after coming from other log providers which support this or show logs from recent to oldest instead.
Considering the fact that many frameworks, such as "Serilog", use the character @ as the prefix for the log properties, it is very unconvenient that AWS CloudWatch filters don't support this format.
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前