sysdig is an open-source system visibility tool that captures Linux kernel system calls and OS events, with native support for inspecting containers without instrumenting them. It runs as a command-line tool, either installed as a deb or rpm package or run directly from a container image, and ships with an optional curses-based UI called csysdig for interactive browsing of the same data. It suits engineers and SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts troubleshooting or investigating activity on Linux hosts and containers who currently rely on a patchwork of older, inconsistent command-line utilities that the README says breaks down in containerized environments; sysdig aims to replace that toolkit with one consistent interface. First committed in 2014, it has drawn 227 contributors, though activity has slowed to 39 commits and one release in the past year, the latest arriving 204 days ago.
Sysdig is a universal system visibility tool with native container support that captures system calls and OS events to enable deep inspection.
Which process on this host is actually driving the disk or network activity right now?
streams live kernel system-call and event data per process and lets it be sorted by resource use, in place of separately running several classic utilities
What was a container doing right before it crashed, without a shell inside it?
reads system calls and events from outside the container through the kernel, so activity is visible even after the container itself is gone
Which files, connections, or commands did a specific process touch during its life on this host?
filters the captured event stream by process and shows every call it made, in place of piecing the story together from several separate logs
What actually happened on this host in the minutes before an alert fired?
records or replays a trace of system calls and events so the sequence can be scrolled and filtered after the fact instead of reconstructed from memory
Which container on a shared host is responsible for a spike in network or disk activity?
breaks down captured kernel events by container without needing agents inside them, attributing the load to the right one
Who is connecting to this host, and over which ports and processes?
shows live and historical connection events tied to the process that opened them, standing in for running several network tools by hand
Built from sysdig's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
sysdig covers 1 of the 11 endpoint investigation and controls capabilities we track.
sysdig covers 1 of the 3 runtime security capabilities we track.
What sysdig offers you
Command-line interface5
Plugin API support1
Plugin system1
No capabilities match.
+Process telemetry3 featuresEndpoint investigation and controlssince 2014▸
+System visibilityshippedCaptures OS-level system calls and events with native container support, combining strace, tcpdump, htop, and lsof capabilities.14 releases · 4 other sources · first seen May 2014▸
Shared capability: Process telemetry
Also counts toward: Command-line interface
release
14 total
Reduce inactive container scan time from 20 minutes to 30 seconds
0.20.0 · Jan 2018
· source
· release history
Add per-cpu counters when a tracepoint is hit
0.19.0 · Oct 2017
· source
· release history
Changes process vpid retrieval to use /proc/<pid>/status for kernels >= 4.1
0.15.0 · Feb 2017
· source
· release history
Adds spectro_all (System call latency spectrogram) and spectro_file (File I/O latency spectrogram) views to csysdig
0.7.0 · Jan 2016
· source
· release history
System visibility tool that captures OS-level system calls and events with native container support, combining strace, tcpdump, htop, and lsof capabilities.
example
Capture the executable command name for fork/exec events instead of relying on argv.$ sysdig -c fdtime_by comm evt.type in (clone, execve, fork, vfork)
0.1.94 · Jan 2015
· source
Trace memory mapping events like mmap and munmap to monitor how processes allocate and free virtual memory.$ sysdig -p '%evt.time %proc.name %evt.arg.addr %evt.arg.len' evt.type in (mmap, munmap)
0.1.83 · May 2014
· source
Run sysdig for system visibility$ sysdig
+Event timing and context filteringshippedOffers advanced filtering capabilities to isolate events around specific command executions, filter by time ranges relative to matches, and access detailed process environment variables.10 releases · 5 other sources · first seen Apr 2014▸
Shared capability: Process telemetry
release
10 total
Adds a new filter matching open+create or create events with exec permissions.
0.27.0 · Aug 2020
· source
· release history
Adds parent PID (ppid) field to the v_procs chisel.
0.27.0 · Aug 2020
· source
· release history
Make executable path filterable and displayable with new proc.exepath field
0.18.0 · Sep 2017
· source
· release history
New filter proc.pcmdline exposes the full parent process command line
0.14.0 · Jan 2017
· source
· release history
Adds exists clause for filters, e.g. sysdig proc.name exists
0.1.99 · Mar 2015
· source
· release history
Adds in clause for filters, e.g. sysdig "evt.type in ( 'select', 'poll' )"
0.1.99 · Mar 2015
· source
· release history
example
Filter events by checking if the event type is one of several specific system calls.$ sysdig "evt.type in ( 'select', 'poll' )"
0.1.99 · Mar 2015
· source
Check if a field has a value before acting on it to avoid false positives.$ sysdig proc.name exists
0.1.99 · Mar 2015
· source
Filter system calls by their buffer length using the new field.$ sysdig evt.buflen > 1024
0.1.94 · Jan 2015
· source
Capture events but only print timing deltas relative to the last matching event for faster filtering analysis.$ sysdig -tD evt.type=connect
0.1.88 · Aug 2014
· source
Capture events around a specific command execution to debug startup issues$ sysdig -s 2048 -w output.fatfile --fatfile 'proc.name=bash'
0.1.87 · Aug 2014
· source
+Userspace instrumentation supportshippedProvides visibility and instrumentation of userspace events via specialized tooling surfaces.1 release · first seen Aug 2020▸
Shared capability: Process telemetry
release
Adds Userspace instrumentation support via the pdig tooling surface.
0.27.0 · Aug 2020
· source
· release history
+Minimal build configurationshippedEnables building a reduced-size binary for constrained environments by excluding heavy dependencies like eBPF, kernel modules, and container support.1 release · 1 other source · first seen Oct 2020▸
Shared capability: eBPF-based runtime detection
release
Adds MINIMAL_BUILD CMake option to exclude kubernetes, kernel module, eBPF, and container support from the build
0.27.1 · Oct 2020
· source
· release history
example
Build a minimal Sysdig binary that excludes heavy dependencies like eBPF and container support for constrained environments.$ cmake -DMINIMAL_BUILD=On ..
0.27.1 · Oct 2020
· source
+Other / not yet classified19 featuresFeatures we have not matched to a capability yet. A suggested match is marked.▸
+Event analysisshippedOffers tools like chisels for filtering and analyzing system events.26 releases · 8 other sources · first seen Apr 2014▸
release
26 total
Adds the chisels feature for event filtering and analysis
0.36.1 · Apr 2024
· source
· release history
Adds MUSL_OPTIMIZED_BUILD CMake option to enable static linking with musl on Alpine Linux
0.27.1 · Oct 2020
· source
· release history
Adds loginuid support with new fields user.loginuid & user.loginname
0.24.0 · Oct 2018
· source
· release history
Adds fd.name_changed filtercheck that is true when an event changes the connection information for a connection fd
0.21.0 · Mar 2018
· source
· release history
evtin.* fields can be used also for displaying now
0.13.0 · Dec 2016
· source
· release history
example
8 total
Compile Sysdig with static musl linking optimized for Alpine Linux deployment.$ cmake -DMUSL_OPTIMIZED_BUILD=On ..
0.27.1 · Oct 2020
· source
Filter sysdig output for connections resolved by domain name, which was not previously possible.$ sysdig -s2048 fd.ip.name=example.com
0.24.0 · Oct 2018
· source
Track the original login user across sudo/su sessions using the new loginuid field.$ sysdig -s2048 user.loginuid=1000
0.24.0 · Oct 2018
· source
Filter only network connections that are actively bound to a remote endpoint, excluding unconnected UDP sockets.$ sysdig fd.connected=true
0.21.0 · Mar 2018
· source
Monitor file writes only for processes belonging to a specific session leader name.$ sysdig evt.type=open and proc.sname=bash
0.10.0 · Jun 2016
· source
Filter events by the process session ID to isolate a specific session's activity.$ sysdig proc.sid=<session_id>
0.10.0 · Jun 2016
· source
+Container supportshippedsuggestedAdds explicit support for Podman containers in the libscap layer alongside existing Docker/OCI container visibility.10 releases · 5 other sources · first seen Mar 2015▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
10 total
Applies patch to enable podman on SCAP files
0.37.0 · May 2024
· source
· release history
Adds support for Podman containers in libscap
0.29.0 · Mar 2022
· source
· release history
Adds parsing and storage of repository, tag, and digest fields in container_info
0.22.0 · Jul 2018
· source
· release history
Add container start/stop events to capture files via new container event type
0.18.0 · Sep 2017
· source
· release history
Adds container.mount.* filter to match container mount points
0.12.0 · Oct 2016
· source
· release history
Adds container.privileged filter to match containers running in privileged mode
0.12.0 · Oct 2016
· source
· release history
example
Run sysdig to monitor container events, filtering specifically for those managed by the rkt runtime.$ sysdig -l "container.type=rkt"
0.8.0 · Feb 2016
· source
When running sysdig inside a Docker container to monitor rkt hosts, mount the rkt library directory.$ docker run -v /var/lib/rkt:/host/var/lib/rkt:ro ... sysdig
0.8.0 · Feb 2016
· source
Filter events using the new container-related filter fields$ sysdig container.name=nginx and thread.cgroup.cpuacct > 0
0.1.98 · Mar 2015
· source
Use the new environment variable to point sysdig to the host's /proc inside a container$ SYSDIG_HOST_ROOT=/host/proc sysdig -pcontainer
0.1.98 · Mar 2015
· source
Get container-aware output for events using the new flag$ sysdig -pc proc.name=bash
0.1.98 · Mar 2015
· source
+Network connectivity analysisshippedProvides chisels and filter operators to monitor active network connections, ports, and syslog traffic for debugging and security auditing.8 releases · 3 other sources · first seen Apr 2014▸
release
8 total
Track connections by domain name via new fields fd.*ip.name
0.24.0 · Oct 2018
· source
· release history
Adds fd.connected filtercheck to determine if a network fd is bound to a remote endpoint
0.21.0 · Mar 2018
· source
· release history
Adds the fd.net, fd.cnet, fd.snet, fd.lnet, and fd.rnet network filter fields supporting CIDR notation (e.g. 127.0.0.1/24) for precise network scope filtering
0.9.0 · Apr 2016
· source
· release history
Adds fd.proto, fd.cproto, fd.sproto, fd.lproto, and fd.rproto filter fields for matching TCP/UDP client, server, local, and remote protocols
0.2.0 · Sep 2015
· source
· release history
Adds netstat chisel to print system network connections similar to standard netstat
0.1.88 · Aug 2014
· source
· release history
Enables <, <=, > and >= operators for network port comparison in filters
0.1.88 · Aug 2014
· source
· release history
example
Detect events where the connection information for an existing file descriptor changes, such as UDP connect() calls.$ sysdig fd.name_changed=true
0.21.0 · Mar 2018
· source
Capture only TCP connections from the local process to an external server$ sysdig fd.lproto=tcp
0.2.0 · Sep 2015
· source
Filter events specifically to syslog messages with facility and severity details$ sysdig -c spy_syslog evt.is_syslog=true syslog.facility.str=kern
0.1.87 · Aug 2014
· source
+Kubernetes metadata integrationshippedProvides fields, API server connectivity, and output formats for filtering and displaying Kubernetes-specific metadata such as pod names, labels, services, and namespaces.7 releases · 3 other sources · first seen Nov 2015▸
Also counts toward: Command-line interface
release
7 total
Supports Kubernetes liveness/readiness probes
0.26.2 · Aug 2019
· source
· release history
Adds k8s.deployment.* and k8s.rs.* filters for Kubernetes support
0.12.0 · Oct 2016
· source
· release history
Adds -K support for SSL based authentication and bearer token authentication against the Kubernetes API server, enabling secure cluster monitoring
0.9.0 · Apr 2016
· source
· release history
Adds -K <file_name> / --k8s-api-cert=<file_name> CLI flags and SYSDIG_K8S_API_CERT environment variable for Kubernetes API server certificate authentication
0.7.0 · Jan 2016
· source
· release history
Introduces the -pk command-line option for Kubernetes-friendly output format in sysdig's capture output.
0.5.0 · Nov 2015
· source
· release history
Adds new display/filter fields k8s.pod.name, k8s.pod.id, k8s.pod.label, k8s.pod.labels, k8s.rc.name, k8s.rc.id, k8s.rc.label, k8s.rc.labels, k8s.svc.name, k8s.svc.id, k8s.svc.label, k8s.svc.labels, k8s.ns.name, k8s.ns.id, k8s.ns.label, and k8s.ns.labels for granular Kubernetes metadata…
0.5.0 · Nov 2015
· source
· release history
example
Authenticate to Kubernetes using a client certificate without interactive prompts.$ sysdig -K /path/to/client.crt --k8s-api-cert=/path/to/ca.crt
0.7.0 · Jan 2016
· source
Filter sysdig output to show only events from pods with a specific label in the production namespace.$ sysdig 'k8s.ns.name=production and k8s.pod.label.env=prod'
0.5.0 · Nov 2015
· source
Connect sysdig to a managed K8s API server and output pod-level details in a format optimized for Kubernetes clusters.$ sysdig --k8s-api https://cluster-api.example.com -pk
0.5.0 · Nov 2015
· source
+Console coloringshippedProvides colored output formatting for events and plugins with support for ANSI escape codes, NO_COLOR environment variable, and plain text fallback.7 releases · 2 other sources · first seen Oct 2015▸
release
7 total
Adds NO_COLOR environment variable support to disable colored output
0.38.0 · Jun 2024
· source
· release history
Adds colored output formatting for plugins
0.29.0 · Mar 2022
· source
· release history
event string formatting now supports colors by default via ANSI escape codes when the terminal allows it
0.28.0 · Dec 2021
· source
· release history
Adds CRI (Container Runtime Interface) support for detecting pod sandbox containers and integrating with containerd and CRI-O
0.25 · Apr 2019
· source
· release history
Brings new csysdig views: Kubernetes Controllers, Kubernetes Namespaces, Kubernetes Pods, and Kubernetes Services.
0.5.0 · Nov 2015
· source
· release history
Adds the backlog csysdig view for monitoring queue utilization per process
0.3.0 · Oct 2015
· source
· release history
example
Run sysdig with plain text output for piping to log viewers that don't support ANSI codes$ NO_COLOR=1 sysdig proc.name==bash
0.38.0 · Jun 2024
· source
Launch csysdig and switch to the new backlog view to monitor process queue depths.$ csysdig --view backlog
0.3.0 · Oct 2015
· source
+Platform supportshippedProvides compatibility with ARM64 architecture through multiarch packages, container images, and prebuilt drivers.9 releases · first seen Apr 2014▸
release
9 total
Support for ARM64: multiarch packages, container images, and prebuilt-drivers (to be used with scap-driver-loader)
0.30.0 · Oct 2022
· source
· release history
Adds s390x architecture support to the sysdig probe builder.
0.26.6 · Mar 2020
· source
· release history
--json output is now a stream of single JSON objects per event separated by newlines instead of a single JSON array
0.14.0 · Jan 2017
· source
· release history
--json output format changes from a JSON array to newline-delimited objects, breaking parsers expecting an array wrapper
0.14.0 · Jan 2017
· source
· release history
Adds rkt support for capturing containers managed by rkt when sysdig runs in a container
0.8.0 · Feb 2016
· source
· release history
Adds automatic sysdig-probe build for boot2docker releases
0.6.0 · Dec 2015
· source
· release history
+Plugin architectureshippedAllows loading and registering source and input plugins via CLI flags, configuration files, or API version 2.0.0.7 releases · 2 other sources · first seen Aug 2014▸
Also counts toward: Command-line interface, Plugin API support, Plugin system
release
7 total
Updated plugin API support to latest 2.0.0 version
0.30.0 · Oct 2022
· source
· release history
More expressive plugin loading experience: detailed info, suggestions on which plugins to be loaded
0.30.0 · Oct 2022
· source
· release history
Adds -I <input_plugin_config> CLI option to use an input plugin as the event source
0.29.0 · Mar 2022
· source
· release history
Adds -H <source_plugin_config> CLI option to load and register a source plugin with init config
0.29.0 · Mar 2022
· source
· release history
Adds --plugin-config-file CLI argument to load plugins via a Falco plugin configuration file
0.29.0 · Mar 2022
· source
· release history
Adds get_terminal_info to the chisel API function set.
0.1.94 · Jan 2015
· source
· release history
example
Register source and input plugins via their respective CLI flags with init/open params.$ sysdig -H dummy:'{"jitter":50}' -I dummy:'{"start":1,"maxEvents":10}'
0.29.0 · Mar 2022
· source
Retrieve the process table within a chisel script to analyze process hierarchy or state programmatically.$ local threads = sysdig.get_thread_table() for id, thread in pairs(threads) do print(id .. ' ' .. thread.name) end
0.1.88 · Aug 2014
· source
+Trace data managementshippedsuggestedSupports capturing, saving, and reading trace files with compression and simultaneous multi-file access.5 releases · 4 other sources · first seen Apr 2014▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
Also counts toward: Command-line interface
release
Ability to open concatenated capture files
0.13.0 · Dec 2016
· source
· release history
Adds -C, -e, -W, and -G flags to rotate tracing files when capturing
0.1.102 · Jul 2015
· source
· release history
sysdig can now be concurrently opened multiple times
0.1.99 · Mar 2015
· source
· release history
Adds -z flag to write compressed trace files
0.1.81 · Apr 2014
· source
· release history
Enables -r to open multiple files simultaneously
0.1.81 · Apr 2014
· source
· release history
example
Read a series of sysdig capture files (e.g., from a segmented disk or pipeline) as a single stream.$ sysdig -r part1.scap part2.scap
0.13.0 · Dec 2016
· source
Capture events with automatic file rotation every 100MB, 10 files max, with gzip compression and 5-second interval.$ sysdig -C 100 -e 10 -W -G 5
0.1.102 · Jul 2015
· source
Capture and save a trace file in compressed format to save disk space.$ sysdig -z -w output.trace
0.1.81 · Apr 2014
· source
Read multiple trace files in a single sysdig session.$ sysdig -r trace1.trace -r trace2.trace
0.1.81 · Apr 2014
· source
+Kernel probe supportshippedsuggestedSupports multiple kernel backend methods including the modern eBPF probe and specific syscalls like mprotect, execveat, copy_file_range, and clone3.7 releases · first seen Aug 2019▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
7 total
Changes the build default to always enable modern BPF via CMake
0.38.0 · Jun 2024
· source
· release history
Adds driver configs for kernel version 7.1.0
0.37.0 · May 2024
· source
· release history
The modern BPF probe is no longer an experimental feature
0.32.0 · Jul 2023
· source
· release history
Addition of the modern ebpf probe as a new userspace backend
0.31.3 · Mar 2023
· source
· release history
Adds mprotect, execveat, copy_file_range, and clone3 syscalls to the kernel driver
0.29.0 · Mar 2022
· source
· release history
Adds renameat2 syscall instrumentation.
0.27.0 · Aug 2020
· source
· release history
+Network connection decoding controlshippedAllows toggling the visibility of server-side port information in network event logs.2 releases · 1 other source · first seen May 2017▸
Also counts toward: Command-line interface
release
Server port decoding is now disabled by default; use the -R flag to restore previous behavior where server ports were decoded
0.16.0 · May 2017
· source
· release history
Changes default network port decoding behavior; server ports are now hidden by default requiring -R to re-enable
0.16.0 · May 2017
· source
· release history
example
Enable server port decoding to see which ports are being connected to from the server side$ sysdig -R
0.16.0 · May 2017
· source
+Storage device identificationshippedAllows inspecting major and minor device numbers for file descriptors to identify specific disk partitions or block devices.1 release · 1 other source · first seen May 2019▸
release
Support major/minor device numbers for file descriptor events
0.26.0 · May 2019
· source
· release history
example
Inspect the major and minor device numbers for file descriptors in a capture to identify specific disk partitions or block devices.$ sysdig -p '%fd.num,%fd.typeinfo.major,%fd.typeinfo.minor' 'fd.type=file'
0.26.0 · May 2019
· source
+Advanced login attributionshippedProvides visibility into the original authenticated user across privilege escalation events via login UID tracking.1 release · 1 other source · first seen Oct 2018▸
release
Adds loginuid support with new fields user.loginuid & user.loginname
0.24.0 · Oct 2018
· source
· release history
example
Track the original login user across sudo/su sessions using the new loginuid field.$ sysdig -s2048 user.loginuid=1000
0.24.0 · Oct 2018
· source
+Custom probe URL loadingshippedAllows the cyber tooling to load kernel probes from a custom HTTP/HTTPS source rather than default repositories.1 release · 1 other source · first seen Jul 2018▸
release
Introduces -e SYSDIG_PROBE_URL=<url> argument to sysdig-probe-loader for custom kernel module URLs
0.22.0 · Jul 2018
· source
· release history
example
Run sysdig-probe-loader to load a kernel module from a custom HTTP source instead of the default location.$ sysdig-probe-loader -e SYSDIG_PROBE_URL=http://custom-server.com/module.ko
0.22.0 · Jul 2018
· source
+Network socket type supportshippedEnables the capture and analysis of network events specifically from netlink sockets.2 releases · first seen Jul 2017▸
release
Add the ability to parse and represent RAW sockets
0.20.0 · Jan 2018
· source
· release history
+Console UIshippedLaunches a curses-based interactive user interface for monitoring and analysis.1 release · 1 other source · first seen Dec 2014▸
release
Buffer rendering on screen is now limited to 80 bytes unless -v is used
0.1.93 · Dec 2014
· source
· release history
example
Launch curses UI for sysdig$ csysdig
+Library linkingshippedSupports linking to shared falcosecurity libraries for integration into other cyber toolchains.1 release · first seen Feb 2025▸
release
Adds support for linking to shared falcosecurity libraries
0.40.0 · Feb 2025
· source
· release history
+Container resource isolation visibilityshippedProvides visibility into CPU usage per Docker cpuset to isolate and monitor resource consumption by container groups.1 release · first seen Aug 2019▸
release
Added support for reporting CPU usage per Docker cpuset to isolate resource consumption by container group
0.26.3 · Aug 2019
· source
· release history
+Time format supportshippedSupports outputting time fields in ISO 8601 UTC format.1 release · first seen May 2019▸
release
Support time field in ISO 8601 UTC format
0.26.0 · May 2019
· source
· release history
+Custom container type supportshippedEnables the cyber tool to integrate and identify custom container runtimes beyond standard Docker/OCI definitions.1 release · first seen Jul 2018▸
release
Enables custom container types alongside Docker on the sinsp level
0.22.0 · Jul 2018
· source
· release history
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for sysdig, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail sysdig puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Sysdig's home and pricing pages and 22 more pages as they looked each month from September 2021 to October 2026: 35 renders, 6 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
Show
57 entries
No entries match these filters.
February 20251
June 20241
May 20241
April 20241
July 20231
March 20231
October 20221
March 20221
December 20211
October 20201
August 20201
March 20201
August 20192
May 20191
April 20191
December 20181
October 20181
August 20181
July 20181
March 20181
January 20181
October 20171
September 20171
July 20171
May 20171
February 20171
January 20171
December 20161
October 20161
July 20161
June 20161
April 20161
February 20161
January 20161
December 20151
November 20151
October 20151
September 20151
August 20151
July 20151
May 20151
March 20152
February 20151
January 20151
December 20141
September 20141
August 20142
July 20142
June 20141
May 20142
April 20142
Project health
Issue, contributor and maintainer activity in draios/sysdig, 2023-10 – 2026-09,
as of 2026-09-25. Twelve-month figures first; the trend lines run
the whole window.
Contributors4±0 vs prior 12 months
Maintainers1+0 joined · −0 left, last 12 months
Bus factor1committers behind half the commits
Community-filed100%of issues opened, last 12 months
Median time to close128 daysfirst maintainer reply 69 days
Open backlog108of 813 issues ever filed
Issues opened / month0 · 0communitymaintainers
Open backlog108
Contributors / month0
Commits / month0
Stars8,293
Issue themes, last 12 months
other 100%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.
None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.