Log-level sipd debug and potential crash

Hi guys

i've opened a ticket at TAC for a signaling problem referred to a notify sent to the SD , and it responds with a 503 internal server error , we think it could be a c-seq problem...for this reason TAC asked me to gather logs at debug level .

My worries are since my customer is very big i'm afraid that when i'll active logs in debug it could crash..i attached a txt file where i gathered some show included cpu and sessions active at around 11 am of the morning...of course task will be done in the late evening but my question is , based on the file attached there is a risk SD can crash? and is there a way to isolate debug to a particular class ? and which class of problem in this case ?