sysdig-inspect v0.8 releases: powerful opensource interface for container troubleshooting and security investigation
Sysdig Inspect is a powerful opensource interface for container troubleshooting and security investigation
Inspect’s user interface is designed to intuitively navigate the data-dense sysdig captures that contain granular system, network, and application activity of a Linux system. Sysdig Inspect helps you understand trends, correlate metrics and find the needle in the haystack. It comes packed with features designed to support both performance and security investigations, with deep container introspection.
To use Sysdig Inspect, you need capture files collected on Linux with sysdig.
Main Features
Instant highlights
The overview page offers an out of the box, at a glance summary of the content of the capture file. Content is organized in tiles, each of which shows the value of a relevant metric and its trend. Tiles are organized in categories to surface useful information more clearly and are starting point for investigation and drill down.
Sub-second microtrends and metric correlation
Once you click on a tile, you will see the sub-second trend of the metric shown by the tile. Yes, sub-second. You will be amazed at how different your system, containers and applications look at this level of granularity. Multiple tiles can be selected to see how metrics correlate to each other and identify hot spots.
Intuitive drill-down-oriented workflow
You can drill down into any tile to see the data behind it and start investigating. At this point you can either use the timeline to restrict what data you are seeing, or further drill down by double clicking on any line of data. You will be able to see processes, files, network connections and much more.
Payloads and system calls visualization
Every single byte of data that is read or written to a file (provided the appropriate --snaplen parameter is used while creating the capture), to a network connection to a pipe is recorded in the trace file and Sysdig Inspect makes it easy to observe it. Do you need to troubleshoot an intermittent network issue or determine what a malware wrote to the file system? All the data you need is there. And, of course, you can switch at any time into sysdig mode and look at every single system call.
Collecting & Loading Captures
Creating a capture file Sysdig Inspect works with capture files that have been collected by sysdig on a Linux system. The sysdig user guide contains a nice introduction to the tool and includes many examples that can guide you through the command line and filtering syntax.
As a very easy quick start, here’s how to capture all of the system events on a Linux box with sysdig:
sudo sysdig -w filename.scap
Changelog v0.8
- Keep Filter While Drilldown / Navigating by @aricallen in #89
- Include Sysdig version 0.27.1 by @drosen0 in #86
- Bump lodash from 4.17.14 to 4.17.20 in /ember-electron/backend by @dependabot in #84
- [Internal] Update dependencies to remove most vulnerabilities by @aricallen in #98
- Bump lodash from 4.17.14 to 4.17.20 in /lib/ui-toolkit by @dependabot in #83
- Bump lodash from 4.17.14 to 4.17.20 in /lib/wsd-core by @dependabot in #82
- Bump ini from 1.3.5 to 1.3.8 in /ember-electron/backend by @dependabot in #96
- Bump dot-prop from 4.2.0 to 4.2.1 in /ember-electron/backend by @dependabot in #99
- Bump mixin-deep from 1.3.1 to 1.3.2 in /ember-electron/backend by @dependabot in #61
- Bump websocket-extensions from 0.1.3 to 0.1.4 by @dependabot in #71
- Bump highlight.js from 9.12.0 to 9.18.5 by @dependabot in #92
- update: bump ember to 3.12 by @therealbobo in #155
- update(ci): move ci to GitHub Actions by @therealbobo in #164
- update: bump sysdig to 0.33.1 by @therealbobo in #166
- update(package.json): bump ember-cli-moment-shim to solve ci issues by @therealbobo in #168
Install & Use
Copyright (C) 2017
