TRACE-CMD-AGENT(1)

๐ŸŽ€ TRACE-CMD-AGENT(1) ๐ŸŽ€

okay so real quick, this page lives in the libtracefs Manual and honestly? it's giving "let my bestie drive your machine" energy. stay with me, it's gonna slay ๐Ÿ’…


โœจ NAME โœจ

trace-cmd-agent โ€” run as an agent on a machine, so another machine can control it ๐Ÿซถ


โœจ SYNOPSIS โœจ

trace-cmd agent [OPTIONS]

โœจ DESCRIPTION โœจ

so trace-cmd(1) has this agent mode, right? it literally just sits there and listens โ€” either over a vsocket (that's the virtual-machine vibe ๐Ÿงš) or a TCP port โ€” waiting for connections that wanna control tracing on this machine.

then when someone connects, the agent starts tracing on the local machine and passes the data over to that controlling connection. no cap, that's the whole job. ๐Ÿ‘‘


โœจ OPTIONS โœจ

  • -N client โ€” listen over TCP instead of a vsocket. you gotta pass in a client host name or IP address to allow the connection to, and it will only connect to that specified client. fair warning tho: any process on that client can control the agent.
โš ๏ธ This is a very insecure setting. Only use on a trusted network. โš ๏ธ Only use if the client machine is totally trusted. like, totally totally.
  • -p port โ€” specifies the port to listen to. that's it, that's the option ๐ŸŽ€
  • -D โ€” sends trace-cmd agent into daemon mode so it runs in the background. bye bestie, you're on your own now ๐Ÿ˜ญ
  • -P cid โ€” lets an agent also act as a proxy server, so it can run on a host and connect with a guest. cid is the context ID (peep vsock(7)) of the client (e.g. a guest VM) that it will allow to connect. very main character of it โœจ
  • --verbose[=level] โ€” sets the log level. supported log levels are "none", "critical", "error", "warning", "info", "debug", "all" โ€” or their identifiers "0", "1", "2", "3", "4", "5", "6". setting the log level to a specific value enables all logs from that level and all previous levels. if you don't specify one, the level defaults to "info".

example โ€” enable all critical, error and warning logs:

trace-cmd listen --verbose=warning

โœจ SEE ALSO โœจ

trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1), trace-cmd-split(1), trace-cmd-list(1)

like, the whole friend group fr fr ๐Ÿ’–


โœจ AUTHOR โœจ

written by Steven Rostedt, <rostedt@goodmis.org[1]> ๐ŸŒˆ


โœจ RESOURCES โœจ

https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/

go look, it's iconic ๐Ÿ‘‘


โœจ COPYING โœจ

Copyright (C) 2010 Red Hat, Inc. free use of this software is granted under the terms of the GNU Public License (GPL). periodt. ๐Ÿ’…


โœจ NOTES โœจ

  1. rostedt@goodmis.org mailto:rostedt@goodmis.org

and that's the whole page bestie!! ๐Ÿฆ‹ this beauty is from libtracefs, dated 03/09/2026 โ€” go forth and trace responsibly, mwah ๐Ÿ’œ๐ŸŒธ

๐Ÿ“ฆ where this page comes from