Hi all - I haven't been able to find anything around this. In AppMon on
the Dynatrace Github there is a container image for the collector but
there is nothing like this I can find for security gateways nor anything
around whether there could be any i...
Hi all,We're looking at setting up some application rules based around
HTTP request headers and the first attempt didn't succeed so wanted to
clarify a few things. Is the assumption correct that the 'custom
application rules' will override the domain...
Hi all,I would like to define some conditional statements with a plugin
to skip over any code that is not necessary if a measure is not
subscribed to (mainly to avoid sending requests to a system that does
not have a relevant feature which would gene...
Hello,We ran into a minor issue where a url monitor is getting a 403 and
redirecting to a different page, but the return code in the monitor is
only returning that 403. Is there anyway to use avoid this and return
only the final return code (I'm not ...
Hello,Looking for some wisdom around the best way to have some data
persistent across plugin executions. The case is I'm working on a plugin
that involves reading a value from a database that indicates an issue
has occurred but the record 'stacks' ev...
Technically both approaches are for Real User Monitoring (RUM) and
generate things like user actions and sessions, the only difference is
how we generate those. In short if you're monitoring a browser that
Those settings will do it but they are the global environment level
settings so apply to all applications using the environment global
settings. You can use those but you can also access application/service
level settings by navigating to that entity...
Those formats are subject to change to since they're internal to
Dynatrace. If you're interested in something to build off of I'd check
out trying W3C Trace Context support
You can actually combine these. You can define user action properties
that use a request attribute as their data source. So you define it as a
request attribute then use that in a user action property configuration.
This does require full stack monit...