question

Michael L. avatar image
Michael L. asked ·

Can you obfuscate a part of a server-side outbound URL?

Hello,

Is it possible to hide a part of a URL? See the blue parts of the below screenshot for an example:

I was considering the Resource URL cleanup rules, but I don't know if that would apply here as it was created for another use case (I cannot test it due to that functionality not being available yet in the cluster).

Kind regards,
Mike

configurationmonitoringservicesgui
sensitive-urls.png (135.0 KiB)
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Alexander S. avatar image
Alexander S. answered ·

Hi Mike,

The resource cleanup rules are only available for real user monitoring data.

Alex

1 comment Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Thanks, I thought as much but I hoped that it could be (mis)-used for this goal :)

0 Likes 0 · ·
Michael K. avatar image
Michael K. answered ·

is this a cleanup question or security related one?

3 comments Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Hi Michael, It is a security question.

0 Likes 0 · ·
@Michael L.,

GET parameters are obfuscated (replaced by '?') unless you have the "view confidential data" role assigned. POST parameters are never there. Hiding the URLs (or parts of them) would certainly lower value of using Dynatrace as problem solving tool. I can only imagine some cleanup rules (regex), that would mark parts of this URLs as confidential. I don't think this is available in Dynatrace at this time.

0 Likes 0 · ·

A regex rule that either removes it or at least marks it as confidential would be great. In this case the url's contain usernames of which user owns a bucket (look at it like an S3 bucket). The usernames are never to be linked back to a user action due to regulations.

0 Likes 0 · ·