FAQs¶

Labels¶

When creating a TESTING task, associated labels are added to it. Later, a monitor is created for this TESTING task, and the {df_label} variable is added to the event content. However, in the final generated event, the content of this variable is displayed as empty.

The reason is that when creating a monitor, the event record will include a system field named df_label, which conflicts with the global label field originally included in the TESTING task. In this case, the global label field in the TESTING task will be discarded, and only the content of the df_label field in the event record will be displayed.

Specifically, the labels added to the TESTING task belong to global labels, while df_label is a system field inherent in the event (event). Therefore, when the monitor generates an event record, it will prioritize using the df_label field in the event, overwriting the originally associated label field in the TESTING task.