cancel
Showing results for 
Search instead for 
Did you mean: 

Log file format details?

Advisor

Log file format details?

Hello. I'm looking for detail regarding the log files a VVX produces. This article:

http://community.polycom.com/t5/VoIP/FAQ-How-can-change-Logging-Levels-or-use-Syslog/m-p/4741/highli...

Gets the closest to what I'm after. Specifcally the part that breaks down the fields in an event as:

 

  • Time Stamp
  • ID
  • Event Class
  • Missed Events
  • Text

Using this event as an example:

 

0901024537|cfg  |5|00|Prm|Parameter feature.validate.peer.cert requested type 0 but is of type 7

 

That would suggest we have the following:

 

  • Time Stamp: 0901024537
  • ID: cfg  
  • Event Class: 5
  • Missed Events: 00
  • Text: Prm|Parameter feature.validate.peer.cert requested type 0 but is of type 7

However, that leaves some questions, like:

 

  1. Are the possible IDs documented anywhere?
  2. Are event classes documented anywhere?
  3. What does Missed Events mean?
  4. It also looks like Prm may be another field that exists before the Text field because of the "|" character. Is that accurate? If so, what is that field called?

Anyway, I think all of this comes down to are the log file formats documented anywhere? I've searched, but certainly may have missed it. Anyone have any input/pointers?

 

 

Message 1 of 7
6 REPLIES
Polycom Employee & Community Manager

Re: Log file format details?

Hello AcousTech,

welcome back to the Polycom Community.

Your understanding is correct and missed events happens when the phone is to busy. The Event Class is the logging Level and the ID is the logging module. In this example the Configuration module.

 

Polycom does not provide more details to End Users.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

Please be aware:

The purpose of these forums is to allow community members collaborate and help each other.
Questions posted here do not follow Polycom’s SLA guidelines.
If you require assistance from Polycom technical support, please open a
web service request or call us .

The above is necessary in order to track issue internally within Polycom.

You are welcome to post more questions or configuration or logs for other community members to look at but if your issue requires a fix via Polycom you must go via the official support structure.

Please ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

Please remember, if you see a post that helped you , and it answers your question, please mark it as an "Accept as Solution".

This forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer.
Polycom employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and may be answered on weekends, bank holidays or personal holidays.
Message 2 of 7
Advisor

Re: Log file format details?

As always, Steffen, thanks for your input.

 

Now, trying to respect the limited information shared with End Users, could you confirm what may be at least available via observation? For example, the the VVX web browser, under Settings, Module Log Level Limits, there is quite a list of modules. Configuration is one of those. Is it fair to assume that these map, via some 5 letter code, to the ID portion? So Configuration, for example, might map to "cfg", as in this example?

 

Similarly, if Event Class is 5, from that same example, would it be accurate to infer that:

  • Debug = 1
  • Event 1 = 2
  • Event 2 = 3
  • Event 3 = 4
  • Minor Error = 5
  • Major Error = 6
  • Fatal Error = 7

I understand there is likely no more data about the field occupied by PRM, but if what I have listed is on target, that goes a long way to helping understand this log files!

Message 3 of 7
Polycom Employee & Community Manager

Re: Log file format details?

Hello AcousTech

Yes CFG is configuration and others follow a similar shorter version

We do not have a complete overview for End Users. We are also in the process of clearing these up so check future versions.

Your assumption about the mapping my of levels is also correct. Once I am back from my holidays I will update the FAQ post to make it a bit more detailed

Replied via a mobile device
Please be aware:

The purpose of these forums is to allow community members collaborate and help each other.
Questions posted here do not follow Polycom’s SLA guidelines.
If you require assistance from Polycom technical support, please open a
web service request or call us .

The above is necessary in order to track issue internally within Polycom.

You are welcome to post more questions or configuration or logs for other community members to look at but if your issue requires a fix via Polycom you must go via the official support structure.

Please ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

Please remember, if you see a post that helped you , and it answers your question, please mark it as an "Accept as Solution".

This forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer.
Polycom employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and may be answered on weekends, bank holidays or personal holidays.
Message 4 of 7
Advisor

Re: Log file format details?

Steffen,

 

Were you ever able to update the FAQ document? I can't tell if the date in the top right is the original posting date, or the last modified date, so I wasn't sure.

 

Thanks.

Message 5 of 7
Highlighted
Polycom Employee & Community Manager

Re: Log file format details?

Hello AcousTech,

 

I did not have a chance to update anything and looking over it now I believe End Customers should be OK with what is documented.

 

Again the logs are there for Polycom to analyze and not really for end users to look at as they can be miss interpreted by an untrained or inexperienced person.

 

Best Regards

 

Steffen Baier

Please be aware:

The purpose of these forums is to allow community members collaborate and help each other.
Questions posted here do not follow Polycom’s SLA guidelines.
If you require assistance from Polycom technical support, please open a
web service request or call us .

The above is necessary in order to track issue internally within Polycom.

You are welcome to post more questions or configuration or logs for other community members to look at but if your issue requires a fix via Polycom you must go via the official support structure.

Please ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

Please remember, if you see a post that helped you , and it answers your question, please mark it as an "Accept as Solution".

This forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer.
Polycom employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and may be answered on weekends, bank holidays or personal holidays.
Message 6 of 7
Advisor

Re: Log file format details?

OK. Makes sense. One question related to this. Apart from the format, one other challenge is that the option for forwarding to a syslog server are somewhat limited. We can define the IP, and the protocol, but not the port. For example, when building a log aggregator, we have lots of syslog stuff destined to the same IP. Being able to change the destination port makes building parsers easier because you can definitively know what the sender is based on the port the event came in on. Then, we don't have to try to interpret multiple events and messages strings from different devices all coming in on the same port. We could put another IP on the aggregator itself, and send one device to port 514 on one IP, and another device(which also may not allow defining the port, such as Avaya phones) to 514 on another IP, but it's so much more elegant to be able to just change the destination port. Is it possible to put that in as a feature request, perhaps?

 

Thanks!

Message 7 of 7