Your organization uses ServiceNow for ITSM. When Instana detects a degraded service, you need an incident automatically created in ServiceNow with category set to 'Application' and urgency set to 'High.' Which configuration approach correctly achieves this?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Instana's native ServiceNow integration (Alert Channel) creates incidents via the ServiceNow Table API. During Alert Channel configuration, administrators can specify the ServiceNow instance URL, authentication credentials, and field mappings including category, urgency, and priority, enabling precise control over incident attributes created from Instana alerts.
Full explanation below image
Full Explanation
Instana's native ServiceNow integration (Alert Channel) creates incidents via the ServiceNow Table API. During Alert Channel configuration, administrators can specify the ServiceNow instance URL, authentication credentials, and field mappings including category, urgency, and priority, enabling precise control over incident attributes created from Instana alerts. The correct answer is 'Configure Instana's ServiceNow Alert Channel with the instance URL, credentials, and field mappings for category and urgency'. The incorrect options — 'Set up a scheduled Instana export job that pushes alert data to ServiceNow every five minutes via SFTP', "Use Instana's Prometheus exporter to forward metrics to a ServiceNow event connector plugin", 'Deploy a ServiceNow agent adapter alongside the Instana agent on each monitored host' — 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.