IBM Instana Observability integration

You can use IBM Instana® Observability to monitor your Content Cortex deployments. You must have access to an Instana server and install an Instana host agent on the same cluster where your Content Cortex deployment is installed.

IBM Instana Observability is a real-time monitoring tool for Kubernetes workloads, operators, and application components. Enabling Instana in Content Cortex provides proactive monitoring of operands and application flows, along with alerting, resource tracking, and incident management.

Assess your integration with Instana with the help of the following sections:

Things to take note of before you can use Instana

You must have the following prerequisites to use Instana with your Content Cortex deployment.

  1. Make sure that you have access to an Instana server, which can be an instance on SaaS or a stand-alone server. For more information, see IBM Instana Observability Planning External link opens a new window or tab.
  2. Install an Instana host agent on the same cluster that you intend to install your Content Cortex deployment. For more information, see IBM Instana Observability > Installing host agents > Installing on Red Hat Openshift External link opens a new window or tab.
  3. When you install your Content Cortex deployment, select to enable Instana monitoring.

    If you already installed a Content Cortex deployment, you can set the option in the custom resource file by setting the shared_configuration.sc_enable_instana_metric_collection parameter to true. For more information, see Shared configuration.

Important things to consider

  • IBM Instana AutoTrace webhook is not supported.
  • OpenTelemetry Integration for nodeJS applications is not supported.
  • Changing the value of the sc_enable_instana_metric_collection parameter in the custom resource causes the Content Cortex pods to restart. A restart is needed to apply the change to the pod configuration.
  • For more information about the current limitations for Instana integration, see Known issues for content services containers.