Hi Jeff > Can you expand on the use case? Why is the number of events a useful > parameter? > > Thanks, > Jeff I am working on tying blktrace into a prometheus exporter so I can monitor block-level activity across a fleet of storage servers. I don't want to overload either the storage server CPUs or the exporter itself when the server is under high load so I want to avoid using the time-based argument for blktrace. If I have access to an events based option I can run this knowing that in high-load situations I will not be capturing many, many IO and perhaps slowing down the server in the process. Does that make sense? Cheers Stephen The 01/14/2025 09:29, Jeff Moyer wrote: > Hi, Stephen, > > Stephen Bates <sbates@xxxxxxxxxxxx> writes: > > > Hi > > > > I am exploring the idea of tying blktrace to a prometheus exporter to > > gather more precise block layer activity across a fleet of servers. As > > part of that I thought it might be useful to be able to run blktrace > > until a user-specified number of events are recorded. > > > > So the following patch adds a new option to do that. I also updated > > the relevant documentation. > > > > I'd appreciate feedback or comments on this! > > Can you expand on the use case? Why is the number of events a useful > parameter? > > Thanks, > Jeff > -- Cheers Stephen Bates, PhD.
