topic Re: PG ID when masking sensitive data from logs (MaskingRulePGIDScope) in Log Analytics

PG ID when masking sensitive data from logs (MaskingRulePGIDScope)

kalle_lahtinen — Mon, 17 Jun 2019 12:32:17 GMT

Hi,

I'm following these instructions for masking sensitive log data:

https://www.dynatrace.com/support/help/how-to-use-dynatrace/log-analytics/configuration/mask-sensitive-information-in-log-analytics/

I'm trying to define a MaskingRulePGIDScope like in the example:

MaskingRulePGIDScope=UsernameMask,0x6714946EC3018AB3

...However, the agent logs display that the used PG ID was "out of range". I've tested several different process group IDs (and PG instance IDs also), both in capitals and in lower case. What is the correct place to extract that Process Group ID? Can I basically navigate to the Process Group, and the copy the ID directly from the URL? E.g. /#processgroupdetails;id=PROCESS_GROUP-6714946EC3018AB3

Well, this is what I've tested so far, but no luck.

Re: PG ID when masking sensitive data from logs (MaskingRulePGIDScope)

kalle_lahtinen — Wed, 19 Jun 2019 05:48:28 GMT

Hi again,

Bumping this message in case someone with log masking experience would happen to see it... Has anyone been able to define the rule scope based on Process Group?

Re: PG ID when masking sensitive data from logs (MaskingRulePGIDScope)

kalle_lahtinen — Mon, 05 Aug 2019 06:48:15 GMT

This was fixed with the next OneAgent version 1.171:

https://www.dynatrace.com/support/help/whats-new/release-notes/oneagent/sprint-171/#resolved-issues

Logging module

Improved Log Monitoring PGID masking rules (APM-183827)