Dynatrace Davis events can contain sensitive information such as email addresses. This document provides a step-by-step guide to setting up a pipeline in Dynatrace Davis events pipelines to mask email addresses from the event.description
field, helping you to stay compliant with data privacy standards.
This article is intended for administrators and app users.
In this article, you'll learn how to set up Davis events pipelines to mask email addresses in the event.description
field.
openpipeline:configurations:write
and openpipeline:configurations:read
permissions. To learn how to set up the permissions, see Permissions in Grail.MaskEmailPipeline
.On the Processing tab, select Processor and set the processor to DQL.
Provide a Name for your processor, for example, Mask event.description
.
Set the DQL processor definition field to the following DQL query:
parse event.description, "LD:content ([a-zA-Z0-9.!#$%&*+-/=?^_{|}~]+'@' LD '.' LD):email"| fieldsAdd event.description = replaceString(event.description, email,"xxx@xxx.xxx")| fieldsRemove email
This DQL query extracts email addresses from event.description
, replaces them with a placeholder, and removes the extracted email field.
{"event.description": "Test_email@dynatrace.com"}
Processing rules applied to the Davis event pipeline don't affect the Davis problem pipeline. To ensure masking is applied consistently, you need to configure the same masking rules for the Davis problems pipeline.
You have learned how to create Davis event pipelines, and can now mask emails from the event description.