StackState.comDownloadSupportExplore playground

Advanced Agent configuration

StackState Self-hosted v5.0.x

This page describes StackState version 5.0.

Go to the documentation for the latest StackState release.

Overview

A number of advanced configuration options are available for StackState Agent V2. These can be set either in the stackstate.yaml configuration file (Linux and Windows) or using environment variables (Docker, Kubernetes and OpenShift).

Reduce data production

The StackState Agent collection interval can be configured. This will reduce the amount of data produced by the Agent.

To configure the collection interval of the Kubernetes and system level integrations, create a values.yaml file with the below contents and specify this when you install/upgrade the StackState Agent. In this values.yaml example, the min_collection_interval has been set to double the default setting. This should result in a noticeable drop in the amount of data produced. If required, you can increase the interval further, however, the aim should be to find a balance between the frequency of data collection and the amount of data received by StackState:

Note that the values.yaml example below includes configuration to enable clusterChecks and run the Kubernetes_state check as a cluster check.

clusterChecks:
# clusterChecks.enabled -- Enables the cluster checks functionality _and_ the clustercheck pods.
  enabled: true
agent:
  config:
    override:
    - name: conf.yaml
      path: /etc/stackstate-agent/conf.d/kubelet.d
      data: |
        init_config:        
        instances:
          - min_collection_interval: 60
    - name: conf.yaml
      path: /etc/stackstate-agent/conf.d/memory.d
      data: |
        init_config:        
        instances:
          - min_collection_interval: 30
    - name: conf.yaml
      path: /etc/stackstate-agent/conf.d/cpu.d
      data: |
        init_config:        
        instances:
          - min_collection_interval: 30
    - name: conf.yaml
      path: /etc/stackstate-agent/conf.d/disk.d
      data: |
        init_config:        
        instances:
          - min_collection_interval: 30
            use_mount: false
            excluded_filesystems:
              - tmpfs
              - squashfs
    - name: conf.yaml
      path: /etc/stackstate-agent/conf.d/io.d
      data: |
        init_config:        
        instances:
          - min_collection_interval: 30
    - name: conf.yaml
      path: /etc/stackstate-agent/conf.d/load.d
      data: |
        init_config:        
        instances:
          - min_collection_interval: 30
    - name: conf.yaml
      path: /etc/stackstate-agent/conf.d/docker.d
      data: |
        init_config:        
        instances:
          - min_collection_interval: 30
    - name: conf.yaml
      path: /etc/stackstate-agent/conf.d/file_handle.d
      data: |
        init_config:        
        instances:
          - min_collection_interval: 30
    - name: auto_conf.yaml
      path: /etc/stackstate-agent/conf.d/kubernetes_state.d
      data: |
    - name: stackstate.yaml
      path: /etc/stackstate-agent
      data: |
        ## Provides autodetected defaults, for kubernetes environments,
        ## please see stackstate.yaml.example for all supported options

        # Autodiscovery for Kubernetes
        listeners:
          - name: kubelet
        config_providers:
          - name: kubelet
            polling: true
        
        process_config:
          intervals:
            container: 40
            process: 30
            connections: 30

        apm_config:
          apm_non_local_traffic: true
          max_memory: 0
          max_cpu_percent: 0

        # Use java container support

clusterAgent:
  config:
    override:
    - name: conf.yaml
      path: /etc/stackstate-agent/conf.d/kubernetes_state.d
      data: |
        cluster_check: true
        init_config:
        instances:
          - kube_state_url: http://YOUR_KUBE_STATE_METRICS_SERVICE_NAME:8080/metrics
            min_collection_interval: 60

Specify the values.yaml file during installation / upgrade of the StackState Agent with the --values argument:

helm upgrade --install \
--namespace stackstate \
--create-namespace \
--set-string 'stackstate.apiKey=<STACKSTATE_RECEIVER_API_KEY>' \
... (set all custom fields)
--values values.yaml
stackstate-cluster-agent stackstate/cluster-agent

Use a proxy for HTTP/HTTPS

The Agent can be configured to use a proxy for HTTP and HTTPS requests. For details, see use an HTTP/HTTPS proxy.

Blacklist and inclusions

Processes reported by StackState Agent V2 can optionally be filtered using a blacklist. Using this in conjunction with inclusion rules will allow otherwise excluded processes to be included.

The blacklist is specified as a list of regex patterns. Inclusions override the blacklist patterns, these are used to include processes that consume a lot of resources. Each inclusion type specifies an amount of processes to report as the top resource using processes. For top_cpu and top_mem a threshold must first be met, meaning that a process needs to consume a higher percentage of resources than the specified threshold before it is reported.

To specify a blacklist and/or inclusions, set the associated environment variables and restart StackState Agent V2.

Environment variable
Description

STS_PROCESS_BLACKLIST_PATTERNS

A list of regex patterns that will exclude a process if matched. Default patterns (github.com).

STS_PROCESS_BLACKLIST_INCLUSIONS_CPU_THRESHOLD

Threshold that enables the reporting of high CPU usage processes.

STS_PROCESS_BLACKLIST_INCLUSIONS_TOP_CPU

The number of processes to report that have a high CPU usage. Default 0.

STS_PROCESS_BLACKLIST_INCLUSIONS_TOP_IO_READ

The number of processes to report that have a high IO read usage. Default 0.

STS_PROCESS_BLACKLIST_INCLUSIONS_TOP_IO_WRITE

The number of processes to report that have a high IO write usage. Default 0.

STS_PROCESS_BLACKLIST_INCLUSIONS_MEM_THRESHOLD

Threshold that enables the reporting of high memory usage processes.

STS_PROCESS_BLACKLIST_INCLUSIONS_TOP_MEM

The number of processes to report that have a high memory usage. Default 0.

Enable traces

The trace Agent will be enabled by default when StackState Agent is installed. It is required to receive traces in StackState. In case it has been disabled, you can enable it again using the instructions below.

To enable tracing on StackState Agent running on Docker, edd the following parameters to your docker run command:

  • -e STS_APM_URL="https://stackstate-ip:receiver-port/stsAgent"

    • The default StackState Receiver port is 7077.

  • -e STS_APM_ENABLED="true"

    • Allows the StackState Trace Agent to capture traces.

Disable Agent features

Certain features of the Agent can optionally be turned off if they are not needed.

To disable a feature, set the associated environment variable and restart StackState Agent V2.

Environment variable
Description

STS_PROCESS_AGENT_ENABLED

Default true (collects containers and processes). Set to false to collect only containers, or disabled to disable the process Agent.

STS_APM_ENABLED

Default true. Set to "false" to disable the APM Agent.

STS_NETWORK_TRACING_ENABLED

Default true. Set to false to disable the network tracer.

PreviousWindowsNextUse an HTTP/HTTPS proxy

Last updated

Logo

Legal notices

PrivacyCookiesResponsible disclosureSOC 2/SOC 3