> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/runtime-security/audit/annotate-audits.md).
# Annotate Audits
Prisma Cloud lets you surface and display designated labels in events and reports. For example, you might already use labels to classify resources according to team name or cost center. With *alert labels*, you can specify which of these key-value pairs are appended to events (audits, incidents, syslog, alerts) and reports.
Labels are key-value string pairs that can be attached to objects such as images, containers, or pods. In Console, specify a list of Docker and Kubernetes labels that contain the metadata you want to append to Prisma Cloud events. When an event fires, if the associated object has any of the specified labels, they are appended to the event.
## Specifying labels to append to Prisma Cloud events
Specify which labels to append to Prisma Cloud events.
1. Open Console.
2. Go to **Manage > Alerts > Alert Labels**.
3. Click **Add Label**.
4. Enter the name of the label to be appended to Prisma Cloud events.
5. Click **Create**.
## Email alerts
The contents of a label can be used as a dynamic target for email alerts. Specify the labels that contain a comma delimited list of email addresses, and when an event fires, the recipients will be notified.
Before setting up your email alerts, be sure you’ve specified a list of labels to be appended to Prisma Cloud events, where at least one label contains a comma-delimited list of email addresses.
Kubernetes labels don’t support special characters, such as `@`, which are required to specify email addresses. Therefore, only Docker labels can be used as a dynamic address list for email alerts.
[Configure email alerts](/content-collections/runtime-security/alerts/email.md)
## JIRA alerts
The contents of a label can be used to dynamically specify project keys, JIRA labels, and assignees for new JIRA issues.
Before setting up your JIRA alerts, be sure you’ve specified a list of labels to be appended to Prisma Cloud events, where the labels contain the type of information you need to dynamically route JIRA issues to the right team.
[Configure JIRA alerts](/content-collections/runtime-security/alerts/jira.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.prismacloud.io/content-collections/runtime-security/audit/annotate-audits.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.