Configure Default Integrations

Sysdig provides default integrations for a number of natively identified applications. For a full list of default integrations, see the Integrations Library. This page explains how to configure default integrations in Sysdig Monitor.

Prerequisites

Default Integrations

Sysdig provides default integrations for applications in the Integrations Library. For example: Application integrations, cloud integrations, and infrastructure integrations.

Default integrations collect metrics from a source and send them to Sysdig Monitor. The metrics Sysdig collects by default have been chosen for their value in building Dashboards and creating Alerts. To collect additional metrics or remove metrics from collection, see Customize a Default Job.

To limit metric collection to specific clusters, see Exlude Clusters from Collecton.

Supported Monitoring Integrations

Integrations can be:

  • Enabled by default: The integration will start reporting metrics as soon as the Sysdig Agent detects the application. You do not need to manually enable this type of integration. See Enable and Disable Integrations.
  • Out of the box: The integration requires no exporter or extra configuration to retrieve metrics from the application. See Configure an Integration.

Sysdig supports the following default integrations:

IntegrationOut of the BoxEnabled by defaultJob name in config file
Apacheapache-exporter-default, apache-grok-default
Calicocalico-node-default, calico-controller-default
Cassandracassandra-default
Cephceph-default
Consulconsul-server-default, consul-envoy-default
Elasticsearchelasticsearch-default
Fluentdfluentd-default, openshift-fluentd-default
HAProxy Ingresshaproxy-default
HAProxy Ingress OpenShifthaproxy-router
Harborharbor-exporter-default, harbor-core-default, harbor-registry-default, harbor-jobservice-default
IBM Kubernetes API Serveriks-apiservers-default
Istioistiod
Kubernetes API serverkubernetes-apiservers-default
K8s cAdvisork8s-cadvisor-default
Kubernetes controller managerkube-controller-manager-default
Kubernetes CoreDNSkube-dns-default
Kubernetes etcdetcd-default, etcd-legacy-default
Kubernetes kubeletk8s-kubelet-default
Kubernetes kube-proxykubernetes-kube-proxy-default
Kubernetes PVCk8s-pvc-default
Kubernetes Schedulerkube-scheduler-default
Kubernetes storagek8s-storage-default
Kafkakafka-exporter-default, kafka-jmx-default
KEDAkeda-default
Knativeknative-operator-default, knative-serving-controller-default, knative-serving-autoscaler-default, knative-serving-activator-default, knative-serving-webhook-default, knative-eventing-broker-filter-default, knative-eventing-broker-ingress-default, knative-eventing-controller-default, knative-eventing-imc-controller-default, knative-eventing-imc-dispatcher-default, knative-eventing-apiserver-source-default
Memcachedmemcached-default
MongoDBmongodb-default
MySQLmysql-default
NGINXnginx-default
NGINX Ingressnginx-ingress-default
NTPntp-default
OPAopa-default
OpenShift API-Serveropenshift-apiserver-default
OpenShift Controller Manageropenshift-controller-manager-default
OpenShift CoreDNSopenshift-dns-default
OpenShift Etcdopenshift-etcd-default
OpenShift Scheduleropenshift-scheduler-default
OpenShift State Metricsopenshift-state-metrics
OracleDBoracledb-exporter-default
PHP-FPMphp-fpm-default
Portworxportworx-default, portworx-openshift-default
PostgreSQLpostgres-default
Prometheus Default Jobk8s-pods
RabbitMQrabbitmq-default
Rancher RKE API Serverrancher-rke-api-server-default
Rancher RKE Controller Managerrancher-rke-controller-manager-default
Rancher RKE CoreDNSrancher-rke-coredns-default
Rancher RKE Kube Proxyrancher-rke-kube-proxy-default
Rancher RKE Schedulerrancher-rke-scheduler-default
Rancher RKE2 API Serverrancher-rke2-api-server-default
Rancher RKE2 Controller Managerrancher-rke2-controller-manager-default
Rancher RKE2 CoreDNSrancher-rke2-coredns-default
Rancher RKE2 Etcdrancher-rke2-etcd-default
Rancher RKE2 Kube Proxyrancher-rke2-kube-proxy-default
Rancher RKE2 Schedulerrancher-rke2-scheduler-default
Redisredis-default
Redis Enterpriseredis-enterprise-default
Sysdig Admission Controllersysdig-admission-controller-default

Enable and Disable Integrations

Some integrations are not enabled by default due to the potential high cardinality of their metrics. To enable or disable integrations:

StepsPreview
Navigate to the Monitoring Integrations page (Integrations > Monitoring Integrations).

Select any integration (here, it’s Kubernetes API server), and click Manage this integration.

Set the integration to enabled or disabled, as desired, and click Confirm. You can also add Exceptions to exclude specific clusters from the general rule.

Configure an Integration

Some default integrations require configuration, such as installing an exporter, to collect metrics. These workloads will appear under the Requires Configuration list. To configure:

  1. Click on one of the workloads listed under Requires Configuration.

    A wizard appears.

  2. Ensure the instance has been correctly identified. If you suspect Sysdig has misidentified the instance, click Configure another integration and choose the correct integration from the integration library. If your integration is not available, you may need to create a custom configuration, see Custom Integrations

  3. If it is correct, click Start Configuration.

  4. The wizard provides instructions, including code snippets and configuration details, for each type of default integration. Follow all the steps provided by the wizard, and once you’re finished, click Close.

Some configurations involve setting up an exporter. To customize an exporter, see Add Sysdig Annotations in Exporters.

Customize a Default Job

The default jobs offered by Sysdig for integrations are optimized to scrape the metrics for building dashboards and alerts in Sysdig Monitor. However, you may wish to manually configure which metrics are collected.

To overwrite a default job:

  1. Locate the prometheus.yaml file in the sysdig-agent ConfigMap in the sysdig-agent namespace.

  2. Consult the Integrations Library for the complete list of default integrations. Find the default agent job in the Agent Configuration section. See, for example, Cassandra Agent Configuration.

  3. Add a new job to the prometheus.yaml file with the same name as the default job you want to replace. For example, if you want to create a new job for the Cassandra integration, create a new job with the name cassandra-default.

    Jobs defined by the user have precedence over the default ones.

Annotate Exporters to Collect Metrics

Sysdig provides a set of Helm charts that helps you configure the exporters for the integrations. Helm charts are publicly available in the Sysdig Helm repository.

If exporters are already installed in your cluster, you can use the standard Prometheus annotations and the Sysdig agent will automatically scrape them.

To collect metrics from an exporter, add this annotation:

spec:
  template:
    metadata:
      annotations:
        prometheus.io/path: /metrics
        prometheus.io/port: '9100'
        prometheus.io/scrape: 'true'