Existing AOT logging code uses a variety of aot+xxx tag combinations to group messages and direct them to independent log streams. Likewise they employ ad hoc conventions regarding format of message content. In most cases the choice of tags and message content/format was motivated by the need to simplify debugging of the AOT code. This does not make it easy to provide tooling intended to answer JDK user's questions about AOT cache content, construction and usage. Existing log messages determined to be appropriate for collection, filtering and analysis by external tooling should be modified to employ log tags from a tag set specified to answer this need, format their message content using well-defined keyword prefixes and ensure that content contains readily readable content formatted following consistent conventions. the same model should be used for any newly added log messages.