FHIR Performance Tracing
The FHIR Performance Tracing configuration category includes the following configurable options:
Capture Raw SQL or Equivalent
Trigger
Performance Tracing Enabled
Output to Response Headers
Output to System Log
Output to Transaction Log
|
|
Capture Raw SQL or Equivalent |
|
|
|
| BOOLEAN | |
| If this is enabled, the raw SQL commands issued to the database will be captured. In the case of non-SQL storage modules (e.g. MongoDB) the raw queries will be captured instead. Note that this can have a measurable impact on performance so this should be enabled only to troubleshoot specific issues. | |
|
|
true
|
|
|
|
|
Trigger |
|
|
|
| ENUM | |
| Values |
|
| Adjust this setting to determine which transactions are traced. | |
|
|
ALL_REQUESTS
|
|
|
|
|
Performance Tracing Enabled |
|
|
|
| BOOLEAN | |
| Enable this setting in order to enable detailed performance tracing. Note that this feature has an impact on performance itself, so it should be enabled with caution on production systems. The other settings in this category will have no effect if this is not enabled. See Performance Tracing for more information. If this setting is disabled, all other performance tracing settings will be ignored. | |
|
|
false
|
|
|
|
|
Output to Response Headers |
|
|
|
| BOOLEAN | |
| Should performance tracing logs be appended to the HTTP response headers? | |
|
|
true
|
|
|
|
|
Output to System Log |
|
|
|
| BOOLEAN | |
| Should performance tracing logs be appended to the System Logs? | |
|
|
false
|
|
|
|
|
Output to Transaction Log |
|
|
|
| BOOLEAN | |
| Should performance tracing messages be appended to the Transaction Log? | |
|
|
true
|
|
|