Integrations, Extensibility, and Maintenance
Integrations push Turbonomic decisions into the tools operations already uses; maintenance keeps the platform and those integrations healthy across upgrades.
Common integrations
- ServiceNow: CMDB sync for business application context and change-request gating for automated actions.
- Ansible Tower/AWX and external orchestration: Turbonomic hands the action over instead of executing it.
- APM targets such as AppDynamics, Dynatrace, or New Relic enrich the supply chain so business applications and transactions sit above workloads.
- Webhook and chat integrations deliver action and alert notifications.
Extensibility
- The versioned REST API backs the UI; scripts should use a dedicated service account with least privilege.
- The kubectl turbo plugin manages the platform lifecycle on Kubernetes, including status, logs, and upgrades.
Maintenance
- Back up the database before upgrades; upgrade through the operator with a new image or custom resource, or deploy a fresh appliance and restore.
- Replace self-signed certificates with CA-signed ones and track expiry; renew the license before it lapses.
- Keep kubeturbo and target integration versions compatible with the platform release.
Worked example
Automated actions stop reaching ServiceNow after a password rotation. Reasoning: the integration authenticates with its own credential, separate from target credentials, so update the ServiceNow integration credential and re-test. Action History showing execution failures separates an integration fault from a policy change.
Traps
Upgrading without a database backup; using a personal admin account for API integrations; pointing webhooks at endpoints the platform cannot reach.