<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000'>Yes, if you look at the options available, you can split the trace in smaller files and even limit the total size accumulated.<br><br><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div class="__aliyun_email_body_block"><div style="color:#333333;font-size:14px;font-family:Tahoma,Arial,STHeiti,SimSun;;">Hi,</div><div style="color:#333333;font-size:14px;font-family:Tahoma,Arial,STHeiti,SimSun;;"> It's well known that tracing can produce huge data easily.So if we keep tracing on a production system for a while(hour/day/week) ,we may get a huge CTF file. It's very inefficient to analysis a huge CTF file ,especially the interested events are in some narrow time window.Is there any way to change the situation?Can we split a huge ctf file into several small ctf file? Or can lttng produce a list of small time-sequence ctf filles just like some loggers do?</div><div style="color:#333333;font-size:14px;font-family:Tahoma,Arial,STHeiti,SimSun;;"><br></div></div></blockquote></div></body></html>