Log files location
Refer to the log files if there are issues with Avaya Engagement Designer. The following table describes the log files for troubleshooting ED and their location:
Log name |
Location |
Description |
EngagementDesigner |
var/log/Avaya/services/EngagementDesigner/EngagementDesigner.log |
This log file at FINE level contains all the information received and sent by Avaya Engagement Designer.
Note:
If more than one version of ED is installed, all logs are stored in the same file. Each line in the log file identifies the version of ED used to produce the log.
|
EventingConnector |
/var/log/Avaya/services/EventingConnector/EventingConnector.log |
This log file at FINEST level contains all the information on the events. |
You can use a publication ID to relate interactions between the EngagementDesigner.log file and the EventingConnector.log file. The same publication ID is highlighted in the following example of an event sent to ED through EventingConnector:
EventingConnector.log:
2018-01-23 16:54:44,653 [WebContainer : 2] EventingConnector FINEST - EventingConnector-3.4.0.0.340003 - servlet context is /events
2018-01-23 16:54:44,653 [WebContainer : 2] EventingConnector FINEST - EventingConnector-3.4.0.0.340003 - doPost ENTER
2018-01-23 16:54:44,656 [WebContainer : 2] EventingConnector FINEST - EventingConnector-3.4.0.0.340003 - EventAckServlet: populateEventMetadata metadata: EventMetaDataImpl [user=null, userAsMatched=null, serviceProfile=null, correlationId=18, producerName=null, producerVersion=null, valueMap={}, isImmutable=false]
2018-01-23 16:54:44,656 [WebContainer : 2] EventingConnector FINEST - EventingConnector-3.4.0.0.340003 - doPost eventBodyPart=com.ibm.ws.webcontainer.srt.SRTServletRequestPart@8b25414e
2018-01-23 16:54:44,656 [WebContainer : 2] EventingConnector FINEST - EventingConnector-3.4.0.0.340003 - doPost body : {"NewString1":"ABC", "NewString2":"EFG", "NewString3":"HJK"}
2018-01-23 16:54:44,656 [WebContainer : 2] EventingConnector FINER - EventingConnector-3.4.0.0.340003 - createEventProducer ENTER eventBody.length=62
2018-01-23 16:54:44,656 [WebContainer : 2] EventingConnector FINER - EventingConnector-3.4.0.0.340003 - createEventingService ENTER
2018-01-23 16:54:44,656 [WebContainer : 2] EventingConnector FINEST - EventingConnector-3.4.0.0.340003 - populateUserHandleAndDomain user=null
2018-01-23 16:54:44,656 [WebContainer : 2] EventingConnector FINER - EventingConnector-3.4.0.0.340003 - publish ENTER publication=PublicationImpl [family=EliFamily, type=EliType, eventMetaData=EventMetaDataImpl [user=null, userAsMatched=null, serviceProfile=null, correlationId=18, producerName=EventingConnector, producerVersion=3.4.0.0.340003, valueMap={}, isImmutable=true], effectiveUser=null, userMinusDefaultDomain=null, userHandle=null, userDomain=null, eventBody=<not shown>, eventVersion=1.0, actualProducerName=EventingConnector, actualProducerVersion=3.4.0.0.340003, publicationId=a1-EventingConnect-3.4.0.0.340003-e0a38e68-d678-40bd-a547-1a0cfa2b9b5d, publicationTimestamp=1516744484656, metaDataBitSet=CeBitSet [val=0x6], valueCount=0]
EngagementDesigner.log:
2018-01-23 16:54:44,666 [WorkManager.DefaultWorkManager : 3] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Received event: EliFamily:EliType Payload: EventImpl [family=EliFamily, type=EliType, payload=<not shown>, version=1.0, publicationId=a1-EventingConnect-3.4.0.0.340003-e0a38e68-d678-40bd-a547-1a0cfa2b9b5d, subscriptionId=EngagementDesig-3.4.0.0.32008-a07a3593a2bec8a323d5cb4438ec96d106abc000909a57307d33cc1f53c57137, consumerName=, consumerVersion=, metadata=EventMetaDataImpl [user=null, userAsMatched=null, serviceProfile=null, correlationId=18, producerName=EventingConnector, producerVersion=3.4.0.0.340003, valueMap={}, isImmutable=true], consumerPrivateData=<not shown>, style=ASYNC, publicationTimestamp=1516744484656]
Modify the log level for Avaya Engagement Designer snap-ins on the System Manager Avaya Breeze® platform Logging Configuration page. To turn the logs on to the FINE level, perform the following steps:
On the System Manager web console, click .
From the Service drop-down list, select EngagementDesigner.
Set the Log Level to FINE.
Select Avaya Oceana® Cluster 1.
Click Commit.
Repeat the steps above to turn the logs on to the FINEST level.
Warning:
Changing log levels can impact the performance of Avaya software. You must change log levels only when Avaya support teams recommend the change to troubleshoot issues.
