1. Overview
| Warning |
|---|
This is a tech preview feature. The tech preview includes an ability to switch on (via a System Parameter) a mode that uses the custom log records. Currently, only Transactions page and Service Activity dashboard are tuned to work with the custom log records. |
The product has built-in capabilities based on the information it receives or samples from the monitored Gateways.
...
- A single MPGW that execute dynamically based on the input the relevant internal flow. Such customer use this method to write the actual service name and other information available.
- Other products that customer wishes to push their information into DPOD
DPOD v1.0.2+ includes a tech preview of this solution. The tech preview includes an ability to switch on (via a System Parameter) a new mode that uses the custom log records. Currently, only Transactions page and Service Activity dashboard are tuned to work with the new custom log records.
- input the relevant internal flow. Such customer use this method to write the actual service name and other information available.
- Other products that customer wishes to push their information into DPOD
2. Implementing the Solution
...
The XSLT file contains placeholders for custom fields that the customer can set to override the default values the product collects. For example, while the product sets the Client IP field to the actual IP address the request was sent from, the customer may override this value in case an X-Forwarded-For header exists.
Custom fields in the XSLT have the notation: <!-- User code goes here -->
All user code must be added only within these notations. For example, for the custom field "customServiceName":
2.3.2. List of Custom Fields in XSLT
Field | Type | Description |
customConsumer | String | A custom consumer name provided by the customer, based on the payload, headers, certificate etc. |
customServiceName | String | A custom service name provided by the customer, based on the payload, headers or just to have meaningful service names. |
customOperationName | String | A custom operation name provided by the customer, based on the payload, headers or just to have meaningful operation names. |
isCustomError | 0/1 | Indicates whether the transaction was considered erroneous by the customer. |
customErrorMessage | String | A custom error message provided by the customer. Trim this message after trimming technicalErrorMessage if total length of Syslog is still more than 1024 bytes. For future use. |
customErrorCode | String | A custom error code provided by the customer. For future use. |
customCompletionStatus | String | A custom completion status provided by the customer from the following list: STARTED, IN_PROGRESS, COMPLETED, ERROR, UNKNOWN, MISSING. For future use. |
customCompletionReason | String | A custom completion reason in case completion status has been provided and more explanation is required. For future use. |
customClientIp | String | A custom client IP provided by the customer (e.g. using X-Forwarded-For header). |
customUserAgent | String | A custom user agent provided by the customer. For future use. |
customNumber1-5 | Number | For future use |
customFloat1-5 | Number | For future use |
customBoolean1-5 | 0/1 | For future use |
customString1-5 | String | For future use |
2.3.3. Using Customized XSLT File
...
To turn off this feature and display technical details (the default mode of the product), in System Parameters page, set Transactions Source back to “syslog”.