The current XSLogs from our AS do not have a Corelation-ID in the Call-Half Field, do I need to change the Logging level of an Input Channel to get this ID included? If so, which Channel and what's the minimum level? Our current logs look to be set at "Info"

BroadSoft-Xtended / BroadWorks-Dashboards-and-Discovery

This repository contains the BroadWorks Dashboards and Discovery components to extend BroadWorks data mining, reporting, and analysis capabilities.

23 stars 4 forks source link

The current XSLogs from our AS do not have a Corelation-ID in the Call-Half Field, do I need to change the Logging level of an Input Channel to get this ID included? If so, which Channel and what's the minimum level? Our current logs look to be set at "Info" #79

Open kporter5302 opened 5 years ago

natecriss commented 5 years ago

I am a coworker of Kevin's.. Here is the current version information of our stack:

Kibana version 6.6.2 Elastic Version 6.6.2 (Lucene_Version 7.6.0) Broadworks AS Release 21 SP1 Bwlogreceiver version 1021 (1204) would not process logs Bwlogcollector version 1021

log_template.pl and call_sequence.pl have been applied.

Here is an example of our output. nocorrelation_id

natecriss commented 5 years ago

Making this change to the application server solved the issue for us.

According to section 2.10 Provisioning Steps of Call Correlation Identifier FD, you can follow these to provision so it is visible in CallP-related logs: AS_CLI/System/CallP/CallCorrelation> get callCorrelationIDFormat = networkUnique AS_CLI/Interface/SIP> ... sendCallCorrelationIDAccess = true sendCallCorrelationIDNetwork = true