Your security team's incident platform is not natively supported by Instana. They require alert payloads in a specific JSON format that includes alert name, severity level, and a static custom tag 'team:security.' What should you configure in Instana to meet this requirement?

Instana's generic webhook Alert Channel accepts a fully customizable HTTP endpoint and payload template. Administrators use Instana-provided templating variables (such as alert name and severity) alongside static values like custom team tags in the JSON body. This flexibility accommodates any third-party incident platform not natively supported by Instana. The correct answer is 'A generic webhook Alert Channel in Instana with a custom payload template including Instana template variables and the static tag'. The incorrect options — 'An email Alert Channel configured with a JSON-formatted body and Base64-encoded custom headers', "A PagerDuty integration with a custom routing key dedicated to the security team's service", "The Instana agent configuration to emit custom events directly to the platform's ingest port" — are wrong because they do not align with IBM Instana's architecture or recommended practices for this scenario. Understanding this concept is essential for the Domain 4: Integration domain of the IBM Instana Observability certification.