A team using GitHub Actions for deployments wants Instana to receive a deployment notification each time a production workflow completes successfully. No native GitHub Actions connector exists in Instana. What is the recommended integration method?
Select an answer to reveal the explanation.
Short Explanation and Infographic
When no native plugin exists, Instana's Events API accepts HTTP POST requests from any tool capable of making HTTP calls. GitHub Actions workflows can include a curl step that sends a deployment event payload to the Instana Events API, authenticating with an API token stored as a GitHub Actions encrypted secret. This pattern works for any CI/CD platform that supports executing shell commands.
Full explanation below image
Full Explanation
When no native plugin exists, Instana's Events API accepts HTTP POST requests from any tool capable of making HTTP calls. GitHub Actions workflows can include a curl step that sends a deployment event payload to the Instana Events API, authenticating with an API token stored as a GitHub Actions encrypted secret. This pattern works for any CI/CD platform that supports executing shell commands. The correct answer is 'Add a workflow step that POSTs a deployment event to the Instana Events REST API using an API token stored as a GitHub Actions encrypted secret'. The incorrect options — "Configure a GitHub repository webhook pointing to the Instana host agent's local REST API on port 42699", 'Install the Instana agent as a GitHub Actions runner on self-hosted runner machines to enable automatic event detection', 'Enable GitHub Deployments API integration which Instana polls for deployment status updates automatically' — 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.