2022 Archive

2022 Archive of Sysdig Agent release notes.

12.10.1 December 20, 2022

This hotfix fixes the issues discovered in the YAML tab of Advisor in Sysdig Monitor. Clicking the YAML tab now works as expected and continues to display YAML configuration for pods.

12.10.0 December 15, 2022

Feature Enhancements

Support for Secure Light Modes

A new agent mode, secure_light, has been introduced to provide you with a limited set of secure features. The features supported in this mode are:

Runtime Policies
Activity Audit (only executed commands)
Captures

Sysdig agents running in secure_light mode consume fewer resources than those running in secure mode.

For more information, see Secure Light.

Add Agent Configuration to Prevent Container Operations

A new agent-level configuration, ignore_container_action, has been added to prevent Sysdig agent from taking potentially disruptive container operations, such as kill, pause, stop, regardless of the policy.

This configuration is disabled by default. To enable it, add the following to the dragent.yaml file:

security:
  ignore_container_action: true

When the configuration is enabled and a policy instructs the agent to perform a container operation, the agent ignores the policy and creates an Info log message explaining the agent did not perform the action because of the configuration.

Improved Scope Matching

The scope matching for runtime policies has been improved by using equivalent container labels when corresponding kubernetes labels are temporarily not available.

The following settings determine the behavior. The example shows the default values.

security:
  use-container-labels-mapping: true
  container_labels_map:
    - "kubernetes.pod.name: container.label.io.kubernetes.pod.name"
 - "kubernetes.namespace.name: container.label.io.kubernetes.pod.namespace"

IMDSv2 Support on AWS Deployments

A new agent-level .yaml configuration, imds_version, should be set to 2 on all the deployments that require token-based communication with the Amazon Web Service (AWS) metadata service IMDSv2:

imds_version: 2

To continue using the IMDSv1 style AWS metadata requests, leave the configuration unchanged or set it to 1.

imds_version: 1

Fix Vulnerabilities

Updated the Go version used for Promscrape to 1.18.7 to resolve Common Vulneratibilities and Exposure (CVEs).
Updated Jackson library to resolve CVE-2022-42003 and CVE-2022-42004.
Upgraded snakeyaml to 1.32 in sdjagent to address CVE-2022-38752.

Disabled Superfluous Memory Consumption Checks

Disabled the agent watchdog from checking memory consumption when running in Kubernetes since Kubernetes has its own resource management. If you wish to re-enable the agent watchdog to check memory consumption when running in Kubernetes, set the following config parameter:

watchdog:
   check_memory_for_k8s: true

Report Additional Labels for Cost Advisor

Modified the default Kubernetes label filters to allow the collection of additional labels to identify the instance, region, zone, and the operating system of the nodes. The additional labels help to calculate costs associated with your infrastructure.

Identify Delegated Agents

Added the statsd_dragent_subproc_cointerface_delegated metric to indicate whether the agent is delegated or not.

Improved Retrieval of Container Metadata

Improved fetching container metadata when both Docker and CRI runtimes are available. This reduces problems where runtime policy events have missing container information.

Known Issues

The YAML tab in Advisor in Sysdig Monitor that displays pod structure, similar to a kubectl describe operation, might not work as expected. Clicking the YAML tab can lead to an agent restart, and as a result, a temporary loss of metrics.

As a workaround, disable it in the dragent.yaml file as follows:


k8s_command:
    enabled: false

Defect Fixes

Report all Storage Classes

The agent now reports all storage classes instead of just one. Earlier, the agent only sent one storage class from global_kubernetes in the metrics protobuf even when multiple storage classes existed in the cluster.

Match Group Name and User Name Appropriately in Events

Events now reports group.name and user.name correctly. Previously, there was an issue where root ID got resolved as N/A for containers in some cases.

Container Terminal Shell No Longer Returns N/A

Implemented container password and group lookup to prevent terminal shell in container returning N/A for the user.name.

Generate Command Execution Records for ARM

Fixed an issue with the activity audit where command execution records were not being generated on ARM processor systems, for top-level processes executed within a container, and with no associated TTY.

Reports Labels Correctly on Pod Redeployment

Fixed an issue with promscrape where the agent would report the old pod UID when a pod is redeployed. This led to having all the labels missing from the timeseries scraped from that pod.

Fix JMX Monitoring on Newer JRE Versions

Fixed an issue where JMX monitoring did not work correctly on newer JRE versions due to sdjagent exceptions

12.9.1 November 14, 2022

Defect Fixes

Fixed Legacy Proxy Connection Between Agent and Collector

The legacy mode of the proxy connection between the agent and the collector works as expected. You can continue to configure if need be.

Fix Enriching Prometheus Metrics with Labels Periodically

Fixed an issue where most labels would be dropped from Prometheus metrics every 5 minutes. This issue only affected the Kubelet jobs associated with Prometheus Integrations as well as the custom job configuration declared by the user.

Fix Vulnerabilities

Fixed the following vulnerabilities:

12.9.0 October 11, 2022

Feature Enhancements

Added New KSM Metrics

Sysdig agent now collects the following Kube-State-Metrics (KSM) ingress metrics:

kube_ingress_info
kube_ingress_labels
kube_ingress_created
kube_ingress_path
kube_ingress_tls

Also, the Sysdig agent collects the following KSM certificate signing request metrics:

kube_certificatesigningrequest_created
kube_certificatesigningrequest_condition
kube_certificatesigningrequest_labels
kube_certificatesigningrequest_cert_length

Expanded Node Resource Metrics

The Sysdig agent now sends all the Kubernetes node resource metrics to the Sysdig backend, rather than just CPU, memory, and pods. This allows you to query kube_node_status_capacity and kube_node_status_allocatable node metrics for the following resources.

cpu=<core>
ephemeral_storage=<byte>
pods=<integer>
attachable_volumes_*=<byte>
hugepages_*=<byte>
memory=<byte>

Additionally, the agent now supports a configuration to collect extended resource metrics on a node. To enable the agent to collect the extended resources, add the following to the dragent.yaml file:

k8s_node:
  extended_resources: true

Upgraded Vulnerable Go Packages in Promscrape v1

Upgraded Prometheus version and resolved vulnerabilities in Promscrape v1.

Retry CRI API Calls After Failed Async Attempts

The Sysdig agent now automatically retries querying the CRI API server after a failed attempt, with a backoff timeout strategy. This improves upon the former strategy of trying only once with a configurable delay value (cri:delay).

Added Error Traces when Open SSL Connection Fails

Added new error messages in the agent log to help identify the nature of connection problems in the collector, when they arise.

Report Taint Information for Kubernetes Nodes

The Sysdig agent will now send taint information associated with Kubernetes nodes. This enables you to query node taints using the kube_node_spec_taint metric in Sysdig Monitor.

Known Issues

The s390x architecture image is not available for v12.9.0; therefore, this version of the agent cannot be installed in zLinux. Note that using the latest tag for agent images on zLinux will not work until the next agent version is released.

Defect Fixes

Restarting Agent No Longer Causes Kernel Panic

Fixed an issue in the Sysdig agent’s kernel module that could cause a kernel panic when the agent was restarted.

Support Arbitrary Java Command Names

Added a configuration parameter to allow you to specify the command names to launch Java processes. This helps detect Java processes for JMX metric collection.

For example, if you want the agent to detect a process by the name of jsivm , while still detecting the other commands, add the following to dragent.yaml:

jmx:
  java_commands:
    - java
    - jsvc
    - jsivm

The values specified in dragent.yaml will override the default values, therefore, you need to include the defaults if you want to continue detecting them.

Captures No Longer Corrupted in Certain Hosts

Sysdig Monitor no longer produces corrupted Capture files in certain hosts in a cluster. Previously the Capture files were found corrupted when generated on a host selected from Explore > Hosts & Container.

Report Containers as Expected

Fixed an issue where containers would not be reported if the agent had issues communicating with the Kubernetes API server.

Upgraded psycopg2 Module

Upgraded psycopg2 module to v2.8.6 to fix issue where Postgres AppCheck fails to start due to missing libpq.

Build Kernel Modules on RHEL6

Fixed an issue preventing the kernel module from building on RHEL6 and other kernels of similar vintage.

Report Unschedulable Pods

Fixed an issue where unschedulable pods would not be reported by the agent.

Initialize Agent on Latest Kernels

Previously, the agent failed to initialize on the latest kernels, such as Ubuntu v22.04 and Fedora 35 and 36, with the following error:

gcc: error: unrecognized command-line option '-mharden-sls=all'

This has been fixed.

Disabled the Policy Scope Cache

The scope cache has been disabled by default to prevent it from getting stuck due to longer completion periods for Infra state.

Updated kube-bench and kubectl Binaries

Updated the Go version used for building kubectl and kube-bench binaries to address vulnerabilities.

Fixed Output Message in the Launch Sensitive Mount Container Rule

The Launch Sensitive Mount Container rule in the Suspicious Container Activity 2 policy no longer shows incorrect information in its output.

Fixed Output Fields in Custom Rules

Fixed an issue where not all the required secure event output fields were being generated by the agent.

12.8.1 August 29, 2022

Defect Fixes

Fix Vulnerabilities in Promscrape v1

Upgraded the Prometheus version and resolved vulnerabilities in Promscrape v1.

Removed Symbolic Link to /etc in the Agent Container

The agent can now read information on users and groups from /host/etc/passwd and /host/etc/group when the agent is running as a container.

Show Falco Events as Expected

Fixed a bug where the Falco output string for a rule would be cut on the first absent or empty field.

12.8.0 August 02, 2022

Feature Enhancements

Added a New Metric for Retrieving Kubernetes State

Added an internal metric, statsd_dragent_subproc_cointerface_ready, to indicate when the agent has pulled Kubernetes state from the API server.

Read Certificate Chain

Improved the agent’s handling of certificate chains. Previously, the agent would only accept the first certificate in a certificate chain and would attempt to verify all other certificates from the configured certificate store. This behavior is compliant with the TLS specification, but idiomatic usage in the wild requires the agent to accept intermediate certificates provided in the handshake as well. The agent will now accept these certificates when provided.

Falco Rules Optimizer

The optional feature Falco Rules Optimizer is now available. This feature increases the speed of syscalls evaluation against Falco rules by introducing indexing on the rules conditions and by caching partial rule condition evaluations. This feature is available in Sysdig agent, but not in open-source Falco.

To enable the feature:

Set falco_optimizer.enabled to true (default value is false).

New Falco Rules Parser

Starting from version 12.8.0, Sysdig agent will use a new Falco rules parser from OSS (open-source software) Falco. The new OSS Falco parser performs stricter grammar parsing and would fail on the following cases:

when \n is used instead of , in a list
when "[" is present in a rule definition
when \034 surrounded by " is present in a rule definition
when the or operation is used between lists instead of with the in operator. For example: condition: open_write and fd.filename is (list1 or list2)

When any of the above cases are present in a custom rules file, the agent fails to parse the respective rule and returns the following error:

Error, security_mgr:791: Could not load policies_v2 message:.

In such cases, edit the custom rules to correct or remove unparsable grammar.

Defect Fixes

Process Kubernetes Audit Events as Expected

Agent no longer throw errors while processing Kubernetes audit events when Kubernetes audit rules contain the endswith condition.

Upgraded Go Language Packages

Go language packages have been upgraded to fix vulnerabilities

Fix Vulnerabilities

Fixed the following vulnerabilities with Promscrape v2:

CVE-2015-3627
CVE-2021-3121
CVE-2020-14040
CVE-2014-6407
CVE-2014-9356
CVE-2014-9357
CVE-2022-23648
CVE-2022-27191
CVE-2021-41103
CVE-2020-15257
CVE-2014-9358
CVE-2021-21334
CVE-2020-13401
CVE-2014-5277
CVE-2020-13401
CVE-2020-8565
CVE-2021-32760
CVE-2021-20329
CVE-2019-11254
CVE-2021-4189
CVE-2020-8565
CVE-2021-4189
CVE-2021-3737
CVE-2021-3634
CVE-2021-3634
CVE-2021-3737
CVE-2022-1996

Detect Prometheus Targets Correctly

Fixed a problem that was causing new Prometheus targets to not be detected until an agent restart.

Intermittent Scraping Failure No Longer Causes Missing Metrics

Fixed an issue of missing metrics caused by intermittent metrics scraping failures.

Show Falco Events as Expected

Sysdig agent now throttles redundant secure events for compliance policies reducing the event noise.

Show Username Correctly in Policy Events

Fixed an agent build issue that rendered password and group functions unavailable. Linked the password and group from /host/etc inside the agent container so the username is correctly shown in policy events.

Fixed a Logging Issue in Promscrape v2

Fixed a logging issue with Promscrape v2. Log levels now take effect as expected when passed in with --log.level.

Fixed Agent Behaviour

Fixed an issue that might cause all the agents to behave as delegated.

12.7.1 July 06, 2022

Defect Fixes

Fixed memdump.size Issue

Fixed the memdump.size configuration, which was not accepted earlier.

Fixed Promscrape Crash Issue

Fixed an issue in Promscrape v2 where a node with a large number of pods and multiple containers per pod could crash.

Fixed Issue Affecting Two Agent Modes

Fixed a problem that caused agent subprocesses to be killed in nodriver mode. This affects the custom-metrics-only and monitor_light modes. For more information, see Configure Agent Modes.

12.7.0 June 28, 2022

Feature Enhancements

New Helm Chart

Sysdig released a unified Helm chart, sysdig-deploy with the following benefits:

Easier to deploy multiple components with one chart, rather than using multiple separate charts
Fewer errors by way of using common configuration for components
Auto-detection of certain configurations, including eBPF for Google Kubernetes Enginer (GKE) Contained-Optimized OS (COS) and endpoint region.

We will maintain the old version of Helm chart, sysdig chart for a period of six months. In this period, the Sysdig chart will be updated with new component versions and and defect fixes.

Live Logs

Sysdig Monitor displays Live Logs in Advisor to help you troubleshoot Kubernetes, which is the equivalent of running kubectl logs. Live logs are displayed on-demand and not stored by Sysdig.

Support Prometheus v2.32

Updated Prometheus scraper to version 2.32.

Metrics Collected in Custom Metrics Only Mode

When custom-metrics-only mode is used, no process metrics are collected. Additionally, only the metrics related to resources (for example, CPU and memory) are collected for containers and host.

Known Issues

While the agent is running, you might encounter an error similar to the following:

Error, security_rule:610: Could not parse rule xx from rules json array

The rule number in the error message might change depending on how many rules are defined.

This is a known issue related to failing to parse an experimental rule. The parser will skip this rule and will log the error message as above. The agent performance and policy evaluation will not be affected.

Defect Fixes

Remove Ceph App Checks

Fixed a problem where errors for obsoleted app checks would be shown when Ceph was running on the host.

Disable Timeseries Caching

Removed a configuration option that stopped Prometheus jobs reporting timeseries when the scrape failed temporarily.

Builds eBPF Probes in Bottlerocket

Fixed an issue that prevented eBPF probes from being built by the agent in Bottlerocket Environments.

Reports Infrastructure State Correctly

Fixed an issue where the Sysdig agent would opens a stream to Cointerface even when it is disabled. This resolves the issue of infrastructure state constantly resetting.

Send Only Supported Metrics in Nodriver Mode

Fixed an issue where unused container and process metrics were sent while in nodriver mode.

Change Log Level to DEBUG When Excessive Log Level Occurs

The excessive logging level occurs under specific conditions, for example, a pod whose used memory results in zero. This case seems to be normal for small pods using very little memory. A fix has been provided so that, when these conditions are detected, the log level for the message that is polluting the logs is brought from INFO to DEBUG.

Report Container Resource Limits and Requests Correctly

Fixed an issue where container resource limits and requests would appear as zero when no limit or request was configured.

12.6.0 May 16, 2022

Defect Fixes

Reloading Promscrape v2 No Longer Causes Dropping Scrape Targets

Reloading Promscrape v2 no longer causes some scrape targets to be dropped from sending metrics.

Prevented Duplicate Node Events

Resolved an issue where duplicate events were generated when a Kubernetes node was lost.

Agents Connect to SaaS Backend Through HTTP Proxy on Older Hosts

Fixed an issue related to SSL certificate verification when connecting through an HTTP proxy on an older host OS, such as CentOS 7.

Agent Refreshes Service Account Token as Expected

Connection with the Kubernetes API Server now works as expected. The Kubernetes client is configured to refresh the bearer token.

12.5.0 May 02, 2022

Feature Enhancements

Default Availability of Slim Agent

The agent installation defaults to the slim agent. The slim agent reduces the surface area for potential vulnerabilities as compared to the full agent, which implies increased security for your monitoring environment. For more information, see Agent Installation.

To continue using the regular agent:

Set slim.enabled to false in your Helm chart.

Monitoring Kubernetes Resources

Sysdig agent v12.5.0 and above no longer collects the Horizontal Pod Autoscaling (HPA) kube state metrics by default. To enable the agent to collect HPA kube state metrics, you must edit the agent configuration file, dragent.yaml, and include it along with the other resources you would like to collect. For more information, see Enable Kube State Metrics.

Container DriftControl: Detect and Prevent Drift in Container Runtime

Sysdig agent can now detect when a new executable was added to a container after a container has started up. The agent collects when a file was downloaded and made executable. When using prevention mode, the agent can also deny the process from ever running. A policy can also be used to define binaries that should be denied/excluded from being denied if they have been added after the container has started.

Disable Syscalls for Secure Modes

Switch syscall events are disabled for secure and secure light modes.

Known issues

An error message is displayed when the agent detects Ceph and attempts to run an obsoleted app check.
The Sysdig agent for ARM can restart when multiple containers are started in rapid succession on the host.

Defect Fixes

Agent on zLinux No Longer Restarts Due to Incorrect Detection of tid Collisions

The agent on s390x architecture (zLinux) has been fixed so the agent does not restart needlessly due to incorrect detection of too many tid collisions.

Reports Correct CronJob Version When Adding CronJob Parents

Fixed an issue causing CronJobs not to be reported as the parents of Job objects.

Agent No Longer Crashes During Abnormal Termination

Fixed an issue causing the agent to crash with a stack backtrace during certain abnormal termination situations.

Slow-Starting JVMs are Terminated Correctly

An incorrect detection of too many tid collisions on s390x architecture (zLinux) will no Longer cause the agent to restart periodically.

Fixed Kubernetes Fetch Issue

Fixed an issue that could prevent Kubernetes events from being correctly fetched.

Disable Watching HorizontalPodAutoscaler

Watching Horizontal Pod Autoscalers has been disabled by default to decrease load on Kubernetes API server. For more information, see Enable Kube State Metrics.

False Positive CVEs for Go Packages No Longer Reported

The Go compiler version has been upgraded to prevent being flagged with false-positive CVEs associated with older Go versions.

Secure Events Reports Correct Cluster Information

Secure events no longer report Kubernetes cluster name default when no cluster exists in the environment.

12.4.0 April 04, 2022

Feature Enhancements

Support for New Architectures

Installing agent on the following architecture are supported:

ARM (aarch64)
aarch64 environments support AWS Graviton.
s390x (zLinux)

For more information, see Host Requirements for Agent Installation.

ARM support includes AWS EC2 Graviton platform

Custom-Metrics-Only Mode

A new agent mode, custom-metrics-only, has been introduced. It enables all custom metrics and Kubernetes state metrics but disables all the driver-based metrics.

Prevented Unnecessary Messages

Fixed a case where a message would be sent to reduce CPU usage when no changes were required.

Known Issues

Configure Node Lease to Decrease Resource Consumption

Incorrect configuration of Kubernetes lease can result in elevated memory usage in the Sysdig agent pods as well as increased load on the Kubernetes API server due to multiple agents querying for more information simultaneously. This also results in a significant amount of additional and unnecessary load on the Sysdig backend.

To decrease resource consumption:

Upgrade to Sysdig agent 12.5.0 which adapts to the non-optimal Kubernetes configuration.
Configure the Kubernetes lease functionality.
- If you are using Helm, the latest versions of the Sysdig Agent Helm chart defaults to configuring the lease functionality automatically.
- If you do not use Helm, the DaemonSet and ClusterRole YAML files are available in our gitbub repository.

For further assistance, contact Sysdig Support.

Prevent Periodic Agent Restarts on zLinux

An incorrect detection of too many tid collisions on s390x architecture (zLinux) can cause the agent to restart periodically.

To workaround this issue, set the following configuration option:

watchdog:
  analyzer_tid_collision_check_interval_s: 86400

This reduces the number of restarts to once a day instead of every ten minutes, which is the default value for the above configuration option. The value is in seconds; there are 86,400 seconds in a day.

This issue has been fixed in Sysdig agent v12.5.0.

Defect Fixes

Validate Promscrape Scrape Jobs

Fixed an issue causing errors with scrape jobs. Scrape jobs associated with Promscrape are now validated before scraping the endpoints.

Removed Irrelevant Warning Messages about App Checks

Removed unnecessary warning messages about app checks limits when app checks are disabled.

Slow-Starting JVMs Are No Longer Terminated

Slow starting JVMs can be terminated by sdjagent. For example, -XX:+AlwaysPreTouch with large heaps. This fix introduces additional configuration options to tune the delay between sdjagent detecting a started JVM process and an attempt to connect.

jmx:
  monitor_connect_timeout_ms: 5000
  management_agent_connect_delay_ms: 0

EVE Connector Works as Expected in Kubernetes

Fixed metadata incompatibility in profiling with Kubernetes versions above 1.20.

Name Change to Configuration Parameter

The falcobasline.max_drops_buffer_rate_percentage parameter has been corrected to falcobaseline.max_drops_buffer_rate_percentage. Notice the missing e in falcobasline in falcobasline.max_drops_buffer_rate_percentage. However, backward compatibility is ensured, and therefore, falcobasline.max_drops_buffer_rate_percentage can still be used.

12.3.1 March 03, 2022

Defect Fixes

Noisy Messages Silenced

Removed a kernel message from the driver that could generate spam when the syscall event buffer is full.

12.3.0 February 17, 2022

Feature Enhancements

Binaries Category for Falco Baseline

Added a new category, binaries, to the Falco baselines feature.

Support for Workload Information in Falco Baseline

Added workload information to Kubernetes context for Falco baselines.

Default Monitoring of Kubernetes Resources

The following Kubernetes resources are now monitored by default:

- persistentvolumeclaims
- persistentvolumes
- storageclasses
- horizontalpodautoscalers

Known Issues

IPv6 Addresses Are Saved Incorrectly When Adding Rules

Adding a new rule causes problem saving IPv6 address for both fd.net and fd.ip.

Defect Fixes

Fix Truncated Capture Files

Fixed a problem which caused the agent to generate truncated capture files.

Container Action Pause Work on Kops/GKE Clusters

Fixed the logic that determines the cgroup path for a container in containerd and made the freezer subsystem available to the agent in order to be able to pause and unpause it.

Agent Profiling Works as Expected

High CPU load no longer prevents CPU and memory profiles from being generated in the agent.

Agents Are Not Reset with Signal 11

Large and negative file descriptors are handled correctly so agents are no longer reset with signal 11.

12.2.1 February 07, 2022

Feature Enhancements

Manage Collecting Metadata from Individual Container Engines

Access to individual container engines from within the agent for fetching metadata can now be disabled via agent configuration.

For example, to disable docker, use the following configuration:

container_engines:
  docker: false

Known Issues

The Pause policy action is not working as expected in GKE, Elastic Kubernetes Service (EKS), and Openshift4 environments.

Defect Fixes

Policy Action “Kill” Is Correctly Triggered in GKE Environments

Policy action on GKE with containerd works as expected:

The container is stopped if HTTP proxy is enabled.
The status of the container is checked upon stop requests. If the status is not CONTAINER_EXITING, termination of the container is attempted with exponential backoff.

Agents Assign Username Correctly for Container Events

Fixed an issue that prevented the proc.name field from extracting the right user from the container started events. This issue was found in agent versions 12.2.0 and above.

12.2.0 January 25, 2022

Feature Enhancements

Improve Install Script to Support eBPF

A new option, bpf or -b is added to the native install script of Sysdig agent to support eBPF.

Enable 10s Flush by Default

By default, the agent collects metrics at 1-second granularity, then aggregates and sends them to the backend in 10-seconds intervals. If you want to use agent versions 12.2.0 or above with the on-prem Sysdig Platform versions below 3.5.0, set the 10s_flush_enable configuration to false to prevent compatibility issues.

The backend in our SaaS deployments continues to enable 10-second flush automatically for all agent versions 10.0.0 or above.

Improved Log Messages

Improved the log messages to report the errors encountered while configuring subprocess_resource_limits.

Handling Incorrect Metric Format

When scraping Prometheus metrics, the agent will set the type to PROMETHEUS_TYPE_INVALID if the metric is exported in an incorrect format or without a specified type. The metric will still be ingested by Sysdig and the query will fallback to gauge.

Known Issues

Processing Secure policy updates in the agent can take longer than it did in the previous releases, and, in some rare scenarios, it causes agent restarts.

Defect Fixes

Fix CVE-2020-29652 in Cointerface

Updated crypto go module to fix CVE-2020-29652.

Promscrape V2 No Longer Crashes on Pods with Multiple Containers

Prevent promscrape_v2 from crashing when a pod has multiple containers.

skip_events_by_type Works as Expected

Fixed an issue in the kernel probe, which prevented the skip_events_by_type feature from correctly filtering events by system call type.

Kubernetes State Is Transmitted as Expected

Fixed an issue where Kubernetes information and metrics would not be sent from the agent. This scenario arose when the agent was deployed in a namespace other than sysdig-agent, and the agent daemonset did not include the podinfo volume.

Agent Successfully Connects to JMX

Fixed an issue where agent wouldn’t connect to JMX on some applications/JVMs. This issue was originally observed on the WebSphere application and Liberty JVM.

Agent Updates Container Status as Expected

Fixed an issue where the agent would not update the container status it first received from the API server. The agent now updates the container statuses as it receives them from the API server.

Check for Invalid Log Level in sdjagent

Fixed an issue where using a log level of none caused sdjagent to crash.

App Checks Run as Expected on Non-Containerized Agent Installations

Fixed an issue preventing app checks running on non-containerized agent installation.

Native Install Doesn’t Support eBPF

Native install prevents insertion of Sysdig probe kernel module when the agent is installed with eBPF by using rpm or deb package.

Prevents Connection Attempts When Agent Encounters Errors

Connection attempts are prevented when the agent encounters errors while handling handshake messages.

Feedback

Was this page helpful?

Glad to hear it! Please tell us how we can improve.

Sorry to hear that. Please tell us how we can improve.