Settings API - Transaction start filters schema table
Transaction start filters (builtin:mainframe.txstartfilters)
Dynatrace automatically traces CICS and IMS transactions when monitored services call them. Transactions that originate on the mainframe, on a terminal, or are called by unmonitored services must be explicitly listed to be monitored.
Add CICS and IMS transactions originating on a terminal (e.g., IBM 3270 green screen terminal) to the terminal transaction start filter. Add all other transactions to the transaction start filters.
Note that traces started using the transaction filters will never be linked to a previous trace, regardless of how the transaction was initiated.
builtin:mainframe.txstartfilters
group:mainframe
environment
GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:mainframe.txstartfilters |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:mainframe.txstartfilters | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:mainframe.txstartfilters |
Authentication
To execute this request, you need an access token with Read settings (settings.read
) scope. To learn how to obtain and use it, see Tokens and authentication.
Parameters
includedCicsTerminalTransactionIds
You can use * as wildcard. For example use A* to trace all transaction IDs that start with A.
includedCicsTransactionIds
You can use * as wildcard. For example use A* to trace all transaction IDs that start with A.
includedImsTerminalTransactionIds
You can use * as wildcard. For example use A* to trace all transaction IDs that start with A.
includedImsTransactionIds
You can use * as wildcard. For example use A* to trace all transaction IDs that start with A.