You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I can't find a way to freeze template after the cluster reach some criteria, such us when the cluster size is large enough.
By adding the ability to freeze the template, we can adopt the template extraction incrementally. If so, we can keep the model trainning, choose the some templates, assign a meaningful name to templates variables for downstream analysis. Since the templates are freeze after reaching some citeria, our code that used to extract the varibles don't need to be changed. If some day we are interested in other templates newly added, we just need to write new code to provide data for downstream.
The text was updated successfully, but these errors were encountered:
Hi the template freezing functionality can be partially achieve by training drain3 offline and using it without add_log_message. If you want to implement some threshold to stop changing old templates on the fly, we should try to figure out what exact criteria shall be used and what parameters to expose for configuration. @lkyhfx
Some aspects to think about, e.g. what's a "large enough" cluster size? This seems highly unpredictable to me.
A better way might be that if ClusterX hasn't been changed for, say a period of time/count of logs ingested, we freeze this particular one. In the end, we freeze all of them.
@Superskyyy Thank you for your response. Actually, my request is to add a feature that allows freezing the cluster in training mode. The specific strategy and implementation details are not crucial. Additionally, the two approaches you mentioned are decent ways to achieve this goal.
Currently, I can't find a way to freeze template after the cluster reach some criteria, such us when the cluster size is large enough.
By adding the ability to freeze the template, we can adopt the template extraction incrementally. If so, we can keep the model trainning, choose the some templates, assign a meaningful name to templates variables for downstream analysis. Since the templates are freeze after reaching some citeria, our code that used to extract the varibles don't need to be changed. If some day we are interested in other templates newly added, we just need to write new code to provide data for downstream.
The text was updated successfully, but these errors were encountered: