eBPF
  • 29 Nov 2024
  • 3 Minutes to read
  • Dark
    Light
  • PDF

eBPF

  • Dark
    Light
  • PDF

Article summary

1.20.2 — 27th November

Traceable’s 1.20.2 eBPF agent release provides the following:

Updates

  • Support for Detecting mTLS Connections

    The eBPF agent now identifies whether a connection uses 1-way TLS or 2-way TLS (mTLS). This information is captured in spans as an attribute: tls.mtls: true/false.

  • Service Name Discovery for ECS Deployments

    • Added support for ECS service name discovery in eBPF deployments. Service names follow the format <container_name>.<ecs_cluster_name>.

    • Enabled by default in ECS CloudFormation templates with configurable ecs_agent_port through the EbpfECSAgentPort parameter.

  • Optional Single Tracer in Kubernetes

    • Introduced an optional configuration to allow the eBPF tracing agent to use a single tracer in Kubernetes deployments. Configuration:

      use_single_tracer: true/false

1.19.0 — 19th September

Traceable’s 1.19.0 eBPF agent release provides the following: /code

Update

  • Pod annotation — The 1.19.0 supports capturing pod annotations as span attributes. For more information, see the eBPF section in the Helm and Terraform values topic.


1.18.0 — 13th September

Update

  • Java TLS capture Traceable’s 1.18.0 eBPF agent release allows controlling Java TLS capture only from certified frameworks.


1.17.0 — 27th August

Traceable’s 1.17.0 eBPF agent release updates the agent with internal fixes.


1.16.0 — 12th August

Traceable’s 1.16.0 eBPF agent release provides the following:

Updates

  • Axway — The 1.16.0 eBPF release adds support for Axway instrumentation using eBPF.

  • Pod label — The 1.16.0 eBPF release enables logging pod labels.


1.15.2 — 17th July

Traceable’s 1.15.2 eBPF agent release provides the following:

  • Java TLS — The 1.15.2 release resolves the issue of Java TLS capture in RPM bundles.


1.15.1 — 9th July

Traceable’s 1.15.1 eBPF agent release provides the following:

Resolved issue

  • eBPF crash — The 1.15.1 release resolves the issue of eBPF crashing in some cases when it could not find the service name.


1.15.0 — 3rd July

Traceable’s 1.15.0 eBPF agent release provides the following:

Updates

  • Go TLS — The 1.15.0 eBPF release supports Go TLS for Go version 1.12 and later.

Resolved issue

  • BTF — The 1.15.0 eBPF release resolves an issue with the temporary filesystem mounting that affected the nearest matching BTF workflow. This problem arose in certain Kubernetes environments with specific Linux kernels and empty tmpfs mounts. The fix ensures that the workflow now operates correctly in these environments.


1.14.1 — 11th June

Traceable’s 1.14.1 eBPF agent release provides the following:

Updates

  • API usage — The 1.14.1 eBPF release optimizes Kubernetes watch API usage.


1.14.0 — 5th June

Traceable’s 1.14.0 eBPF agent release provides the following:

Updates

  • Configuration process — The 1.14.0 eBPF release exposes configurations for defining the processes you wish to instrument with process names and command-line variables.


1.13.3 — 14th May

Traceable’s 1.13.3 eBPF agent release provides the following:

Updates

  • Custom SSL address — The 1.13.3 eBPF release supports custom SSL address uprobes based on name and SHA256.

  • Java TLS agent — The 1.13.3 eBPF release limits the number of attach attempts for the Java TLS agent.

  • eBPF uprobe — The 1.13.3 eBPF release provides configuration options to exclude certain processes from attaching to uprobes.

Resolved issues

  • High CPU usage—The 1.13.3 eBPF release resolves high CPU usage caused by goroutine leaks in gotls, javatls, and http2.


1.12.2 — 29th April

Traceable’s 1.12.2 eBPF agent release updates the agent with internal fixes.


1.12.1 — 8th April

Traceable’s 1.12.1 eBPF agent release updates the agent with internal fixes.


1.12.0 — 25th March

Traceable’s 1.12.0 eBPF agent release provides the following updates:

  • Oracle RDB calls — The 1.12.0 eBPF release provides a simple configuration to capture Oracle RDB calls. Traceable captures the database name, connection string, IP address, and call latency. To configure, add/modify the following in the ebpf tracer config file:

    # capture mode should be ingress_and_egress
    mode: "ingress_and_egress"
    
    # backend port based data capture
    backends:
      oracle_db:
        port_list:
          - 49161 # replace with the port your Oracle DB is running on.
  • Process exclude list — The 1.12.0 eBPF release adds support to define regexes to exclude processes from monitoring. For regexes, use regex:<value>, for example, “regex:jav*”. For more information, see eBPF in the Traffic mirroring topic.

  • Signed docker images — Traceable’s 1.12.0 eBPF provides signed docker images.


1.11.3 — 13th March

Traceable’s 1.11.3 eBPF agent release updates the agent with internal fixes.


1.11.2 - 22nd February

Traceable’s 1.11.2 eBPF agent release updates the agent with internal fixes.


1.11.1 - 9th February

Traceable’s 1.11.1 eBPF agent release updates the agent with internal fixes.


1.11.0 - 29th January

Traceable’s 1.11.0 eBPF agent release comes with repository metadata signing.


1.10.7 - 10th January

Traceable’s 1.10.7 eBPF agent release updates the agent with internal fixes.


1.10.6 - 8th January

Traceable’s 1.10.6 eBPF agent release updates the agent with internal fixes.


1.10.5 - 2nd January

Traceable’s 1.10.5 eBPF agent release updates the agent with internal fixes.


Was this article helpful?

What's Next