Registered User m (Replaced content with "<noinclude> {{ArticleBasedOnModel|Trace and debug tools article model}} {{ArticleApprovedVersion | Jean-ChristopheT | Nobody | No previous approved version | Automatic...") Tag: Replaced |
Registered User mNo edit summary |
||
(12 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
<noinclude>{{ApplicableFor | |||
|MPUs list=STM32MP13x, STM32MP15x | |||
|MPUs checklist=STM32MP13x, STM32MP15x | |||
}}</noinclude> | |||
{{ReviewsComments| JPR 20Dec'18: Latest action:<br/> | |||
- Not possible with SDK, need to run with distribution.<br/> | |||
- With distrib, need to get latest version of sysdig because of kernel driver compatibility with 4.14/4.19<br/> | |||
- Need to have one recipe for sysdig application, and one for sysdig driver<br/> | |||
- Need to create a new recipe for libb64<br/> | |||
- All in /local/opt/st/stm32mp1/2.4-snapshot-openstlinux-4.14-rocko-mp1-18-11-02/<br/> | |||
- 2 gerrits pushed to integrate the recipes, then user have only to add sysdig and sysdig-driver in the weston image: https://gerrit.st.com/#/c/119920/ and https://gerrit.st.com/#/c/119921/ | |||
}} | |||
== Article purpose == | |||
This article provides basic information to start using the Linux tool: '''sysdig'''<ref name=sysdigdotorg/>. | |||
== Introduction == | |||
{{:Trace_and_debug_tools_assignment_table_template}} | |||
<onlyinclude> | |||
| [[Sysdig|sysdig]] | |||
| [[:Category:Monitoring tools|Monitoring tools]] | |||
| style="text-align:left;" | '''sysdig'''<ref name=sysdigdotorg>https://sysdig.com</ref> is a tool for system troubleshooting, analysis and exploration. It can be used to capture, filter and decode system calls and other OS events. | |||
| {{N}} || {{N}} || {{Y}} | |||
| {{N}} || {{N}} || {{N}} | |||
|- | |||
</onlyinclude> | |||
|} | |||
'''sysdig''' can be both used to inspect live systems or to generate trace files that can be analyzed at a later stage. | |||
It includes a powerul filtering language, has customizable output, and can be extended through [http://www.lua.org/ Lua] scripts, called chisels. | |||
'''sysdig''' aims to replace a collection of tools, as lsof, strace, iostat, ps, etc... | |||
== Installing the trace and debug tool on your target board == | |||
'''sysdig''' is a user space application {{highlight|which is not part of the standard STM32MPU Embedded Software distribution image and Packages}}. It has to be integrated as an external component. | |||
Linux kernel configuration must also enable '''CONFIG_TRACEPOINTS''' and '''CONFIG_HAVE_SYSCALL_TRACEPOINTS''': | |||
Symbol: '''TRACEPOINTS''' [{{green|=y}}] | |||
Selected by: {{highlight|TRACING [=y] || BLK_DEV_IO_TRACE [=n] && TRACING_SUPPORT [=y] && FTRACE [=y] && SYSFS [=y] && BLOCK [=y]}} | |||
Symbol: '''HAVE_SYSCALL_TRACEPOINTS''' [{{green|=y}}] | |||
Selected by: {{highlight|ARM [=y]}} | |||
=== Using STM32MPU Embedded Software distribution === | |||
On STM32MPU Embedded Software distribution(weston), Linux kernel configuration already enable the required configuration options. | |||
==== Developer Package ==== | |||
There are too many dependencies for building sysdig application and kernel driver, that's the reason why this is recommended to use the Distribution package to integrate this tool. | |||
==== Distribution Package ==== | |||
{{UpdateNeededForNewRelease|Below InteralInfo banner to be removed when integrated after MMDV}} | |||
{{InternalInfo|<br/> | |||
This is NOT present on MMDV}} | |||
Yocto recipes for building sysdig are part of the OpenSTLinux distribution. | |||
Following steps to be done to enable sysdig and add it to the st-image-weston image: | |||
* Add sysdig package install for the image | |||
{{PC$}} echo 'IMAGE_INSTALL_append += "sysdig-stm32mp"' >> layers/meta-st/meta-st-openstlinux/recipes-st/images/st-image-weston.bbappend | |||
{{PC$}} echo 'IMAGE_INSTALL_append += "sysdig-driver"' >> layers/meta-st/meta-st-openstlinux/recipes-st/images/st-image-weston.bbappend | |||
* Regenerate the image file: | |||
{{PC$}} bitbake st-image-weston | |||
* Update your board with the new image. See [[STM32MP1 Distribution Package#Flashing the built image|Flashing the built image]]. | |||
==Getting started== | |||
Below some basics commands extracted from official sysdig website<ref name=sysdigdotorg/>: | |||
[[File:sysdig_exemples.png|link=]] | |||
==To go further== | |||
{{UnderConstruction}} | |||
== References == | |||
<references /> | |||
{| | |||
|+ "External links" | |||
|- | |||
! scope=col | Document link | |||
! scope=col | Document Type | |||
! scope=col | Description | |||
|- | |||
| [https://github.com/draios/sysdig/blob/master/userspace/sysdig/man/sysdig.md sysdig manpage] | |||
| Standard | |||
| Man page from Official github | |||
|- | |||
| [https://github.com/draios/sysdig/wiki sysdig wiki documentation] | |||
| User Guide | |||
| Documentation from Official github | |||
|} | |||
<noinclude> | <noinclude> | ||
{{ArticleBasedOnModel| | {{ ArticleBasedOnModel | Trace and debug tools article model }} | ||
[[Category:Linux monitoring tools]] | [[Category:Linux monitoring tools]] | ||
{{PublicationRequestId | 24651 | 2022-09-26}} | |||
</noinclude> | </noinclude> | ||
Latest revision as of 11:43, 31 January 2023
1. Article purpose[edit source]
This article provides basic information to start using the Linux tool: sysdig[1].
2. Introduction[edit source]
The following table provides a brief description of the tool, as well as its availability depending on the software packages:
: this tool is either present (ready to use or to be activated), or can be integrated and activated on the software package.
: this tool is not present and cannot be integrated, or it is present but cannot be activated on the software package.
Tool | STM32MPU Embedded Software distribution | STM32MPU Embedded Software distribution for Android™ | ||||||
---|---|---|---|---|---|---|---|---|
Name | Category | Purpose | Starter Package | Developer Package | Distribution Package | Starter Package | Developer Package | Distribution Package |
sysdig | Monitoring tools | sysdig[1] is a tool for system troubleshooting, analysis and exploration. It can be used to capture, filter and decode system calls and other OS events. | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
sysdig can be both used to inspect live systems or to generate trace files that can be analyzed at a later stage.
It includes a powerul filtering language, has customizable output, and can be extended through Lua scripts, called chisels.
sysdig aims to replace a collection of tools, as lsof, strace, iostat, ps, etc...
3. Installing the trace and debug tool on your target board[edit source]
sysdig is a user space application which is not part of the standard STM32MPU Embedded Software distribution image and Packages. It has to be integrated as an external component.
Linux kernel configuration must also enable CONFIG_TRACEPOINTS and CONFIG_HAVE_SYSCALL_TRACEPOINTS:
=y] Selected by: TRACING [=y] || BLK_DEV_IO_TRACE [=n] && TRACING_SUPPORT [=y] && FTRACE [=y] && SYSFS [=y] && BLOCK [=y] Symbol: HAVE_SYSCALL_TRACEPOINTS [=y] Selected by: ARM [=y]Symbol: TRACEPOINTS [
3.1. Using STM32MPU Embedded Software distribution[edit source]
On STM32MPU Embedded Software distribution(weston), Linux kernel configuration already enable the required configuration options.
3.1.1. Developer Package[edit source]
There are too many dependencies for building sysdig application and kernel driver, that's the reason why this is recommended to use the Distribution package to integrate this tool.
3.1.2. Distribution Package[edit source]
Yocto recipes for building sysdig are part of the OpenSTLinux distribution.
Following steps to be done to enable sysdig and add it to the st-image-weston image:
- Add sysdig package install for the image
echo 'IMAGE_INSTALL_append += "sysdig-stm32mp"' >> layers/meta-st/meta-st-openstlinux/recipes-st/images/st-image-weston.bbappend
echo 'IMAGE_INSTALL_append += "sysdig-driver"' >> layers/meta-st/meta-st-openstlinux/recipes-st/images/st-image-weston.bbappend
- Regenerate the image file:
bitbake st-image-weston
- Update your board with the new image. See Flashing the built image.
4. Getting started[edit source]
Below some basics commands extracted from official sysdig website[1]:
5. To go further[edit source]
![]() |
Coming soon |
6. References[edit source]
Document link | Document Type | Description |
---|---|---|
sysdig manpage | Standard | Man page from Official github |
sysdig wiki documentation | User Guide | Documentation from Official github |