Troubleshooting
Where can I find the log files?
- The Following is the Integration Server log file location,
<InstallDir>/IntegrationServer/instances/default/logs
- The following is the Microservices Runtime log file location,
<InstallDir>/IntegrationServer/logs
- The following is the on-premises Integration Server transaction traces location,
e2etraces.log
How can I view traces information in the log files?
Note: The following steps are applicable only if you have already completed the configuration for
hybrid monitoring with IBM webMethods Integration Server or with IBM webMethods API Gateway.
-
Go to the file
e2ecustomlogback.xml
at the following location:- Integration
Server:
<INSTALL-DIR>\IntegrationServer\instances\default
- Microservices Runtime:
<INSTALL-DIR>\IntegrationServer
Note: If you cannot locate the filee2ecustomlogback.xml
in the installation, then install the latest fixes. - Integration
Server:
- Apply the DEBUG logging level to the following
properties:
"e2eAgentSummary" level="DEBUG" "e2eAgentSegments" level="DEBUG" "e2eagentFailedSegments" level="DEBUG"
- The following is a sample of the on-premises transaction
trace:
2021-08-06T19:49:50,328 DEBUG [e2eAgentAppender] - [ENTRY]SpanInfo [traceId=[26655816.49441.45841902585488], segmentId:26655969.276.162825958992328, spanId:0, serviceName=forTesting:javaAsyncService1, startTime=1628259589923, duration=4ms, component=ONPREMISEIS, tenant=VMWODEPLAT01:5555, status=Success, requestID=5745b59f-089a-4b13-9038-f82188d68a32, parentLandscape=WMIO]
Are there exception cases where hybrid transaction traces do not work?
- The trace cannot be guaranteed to be coherent if you have child services that are audited, but called from a parent service that is not audited.
Detailed step-by-step tutorial
For a detailed tutorial, see Hybrid Monitoring.