Transaction Log
The Transaction Log configuration category includes the following configurable options:
Transaction Log Broker Channel Name
Event Blacklist
Event Whitelist
Persist Transaction Bodies (Global)
Persist Transaction Bodies: Incoming Request
Persist Transaction Bodies: Incoming Response
Transaction Log Step Body Serialization Mode
Transaction Log Broker Enabled
Transaction Log Database Storage Enabled
Transaction Log Show Request Body Enabled
Truncate Transaction Bodies (bytes)
|
|
Transaction Log Broker Channel Name |
|
|
|
| STRING | |
| The transaction logs will be sent to the specified topic/queue name. Must be non-empty. | |
|
|
smilecdr-transaction
|
|
|
|
|
Event Blacklist |
|
|
|
| STRING | |
| This setting provides a blacklist of event Type/SubType codes that should not be stored in the Transaction Log. See Controlling Transaction Log Events for more information. | |
|
|
| (no default) | |
|
|
|
Event Whitelist |
|
|
|
| STRING | |
| This setting provides a whitelist of event Type/SubType codes to be stored in the Transaction Log. See Controlling Transaction Log Events for more information. | |
|
|
| (no default) | |
|
|
|
Persist Transaction Bodies (Global) |
|
|
|
| BOOLEAN | |
| If enabled, the bodies of transactions will be persisted in the transaction log. This can be useful for troubleshooting; however, it has database capacity and performance implications under heavy load. This configuration is enabled by default. Note that this is a master switch, and disabling it takes precedence over any more specific persistence switches. | |
|
|
true
|
|
|
|
|
Persist Transaction Bodies: Incoming Request |
|
|
|
| BOOLEAN | |
| If enabled, incoming request transaction bodies (e.g. the request body for a FHIR create request received by a FHIR Endpoint module) will be persisted in the transaction log. | |
|
|
true
|
|
|
|
|
Persist Transaction Bodies: Incoming Response |
|
|
|
| BOOLEAN | |
| If enabled, incoming response transaction bodies (e.g. the response body for a FHIR search request received by a FHIR Endpoint module) will be persisted in the transaction log. | |
|
|
true
|
|
|
|
|
Transaction Log Step Body Serialization Mode |
|
|
|
| ENUM | |
| Values |
|
| Controls whether the transaction log step body is serialized as formatted JSON or flattened(inline) | |
|
|
FHIR_JSON
|
|
|
|
|
Transaction Log Broker Enabled |
|
|
|
| BOOLEAN | |
| If enabled, the transaction log will submit events to the configured broker for use in realtime reporting. | |
|
|
false
|
|
|
|
|
Transaction Log Database Storage Enabled |
|
|
|
| BOOLEAN | |
| If disabled, no new entries will be written to the transaction log table in the database. Existing entries will remain available until the configured retention period has elapsed. | |
|
|
true
|
|
|
|
|
Transaction Log Show Request Body Enabled |
|
|
|
| BOOLEAN | |
| If enabled, the transaction log will show the body of the FHIR request events. | |
|
|
false
|
|
|
|
|
Truncate Transaction Bodies (bytes) |
|
|
|
| NON_NEGATIVE_INTEGER | |
| If set to a positive integer, transaction log payload bodies will be truncated before being stored in the transaction log. | |
|
|
10000
|
|
|