×

Join the Conversation

Without signing in, you're just watching from the sidelines. Sign in or Register to connect, share, and be part of the Splunk Community.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Ask a Question
xzou_splunk
Splunk Employee
Member since: ‎09-14-2019
‎05-06-2025
Community Statistics
Posts 4
Solutions 0
Karma Given 1
Karma Received 0
Member Since ‎09-14-2019
Activity Feed
View All

Re: Monitoring Polycom syslog with Splunk

by Splunk Employee in Getting Data In
‎03-11-2020 08:39 PM
‎03-11-2020 08:39 PM
Yes, you may be right. We need vendor's help with the content. ... View more

Re: Monitoring Polycom syslog with Splunk

by Splunk Employee in Getting Data In
‎03-11-2020 06:27 AM
‎03-11-2020 06:27 AM
Yes, normally. But this time, there's no any detail in Polycom's manual or maybe I didn't find the right one. Here's some sample event from server.log. 020-03-10T12:00:04.647+0800|DEBUG|RegistrationMgr-ScheduledTasks:3552:|347|com.polycom.proximo.callserver.registration.RegistrationsMgr| Removed HighAvailabilityRegistrationKey commObject=3d1d6e75-f200-46c1-80bb-962a0ba8c771 2020-03-10T12:00:04.647+0800|DEBUG|RegistrationMgr-ScheduledTasks:3552:|347|com.polycom.proximo.callserver.registration.ManagedRegistrationImpl| cancel all timer tasks for registration:com.polycom.proximo.callserver.registration.H323ManagedRegistration@c96e659b:commObject ID[3d1d6e75-f200-46c1-80bb-962a0ba8c771] expireTask[com.polycom.rpp.commons.util.RppScheduledExecutor@5dd9c0de[Running, pool size = 1, active threads = 1, queued tasks = 270, completed tasks = 37689]] expireTasks[{}] idKey[3d1d6e75-f200-46c1-80bb-962a0ba8c771] lastContact[null] lastContactExpires[null] expiredReg[true] responseTerritory[PN:DMA:TER-A] rasAddress[/99.46.23.40:1719] allow LRRQ[true] remoteAddress[/99.46.23.40:1719] 2020-03-10T12:00:04.647+0800|DEBUG|RegistrationMgr-ScheduledTasks:3552:|347|com.polycom.proximo.callserver.registration.RegistrationsMgr| removed registration:3d1d6e75-f200-46c1-80bb-962a0ba8c771 because:UNREGISTERED key:3d1d6e75-f200-46c1-80bb-962a0ba8c771 2020-03-10T12:00:04.647+0800|DEBUG|RegistrationMgr-ScheduledTasks:3552:|347|com.polycom.proximo.callserver.registration.RegistrationsMgr| registration[com.polycom.proximo.callserver.registration.H323ManagedRegistration@c96e659b:commObject ID[3d1d6e75-f200-46c1-80bb-962a0ba8c771] expireTask[com.polycom.rpp.commons.util.RppScheduledExecutor@5dd9c0de[Running, pool size = 1, active threads = 1, queued tasks = 270, completed tasks = 37689]] expireTasks[{}] idKey[3d1d6e75-f200-46c1-80bb-962a0ba8c771] lastContact[null] lastContactExpires[null] expiredReg[true] responseTerritory[PN:DMA:TER-A] rasAddress[/99.46.23.40:1719] allow LRRQ[true] remoteAddress[/99.46.23.40:1719]] deactivate notify watcher:com.polycom.proximo.callserver.registration.GatekeeperRegistrationPolicyImpl@576af8c5 2020-03-10T12:00:04.647+0800|WARN |MsMonSup-Poll-MCU-99.38.80.100-ScheduledTasks:8480:|347|com.polycom.proximo.videoms.driver.util.XmlMcuExecutorBase| slow response 1013ms from 99.38.80.100 0Status OK ... View more

Monitoring Polycom syslog with Splunk

by Splunk Employee in Getting Data In
‎03-11-2020 04:03 AM
‎03-11-2020 04:03 AM
Hi all, We are trying to analyze the Syslog from Polycom, such as server.log, access.log, etc. However, we don't understand the content of those logs. Is there any place we can get a detailed description of those logs? ... View more

Failed to receive logs from Docker with Splunk Log...

by Splunk Employee in Getting Data In
‎09-14-2019 08:01 PM
‎09-14-2019 08:01 PM
Hi all, I followed the instruction in https://github.com/splunk/docker-logging-plugin to install the log driver, and also setup the HEC in Splunk. Tried following: 1. docker run --publish 4000:80 --log-driver=splunk-logging-plugin --log-opt splunk-token=xxxxx --log-opt splunk-url=https://127.0.0.1:8088 xxxx; No logs in Splunk 2. Change docker daemon as { "debug" : true, "experimental" : false, "log-driver": "splunk-logging-plugin", "log-opts": { "splunk-token": "xxxxxx", "splunk-url": "https://127.0.0.1:8088", "splunk-insecureskipverify": "true" } } No logs in Splunk 3. curl -k https://127.0.0.1:8088/services/collector/event -H "Authorization: Splunk xxxxxx" -d '{"event": "hello world"}' Receive return meg: {"text": "Success", "code": 0}, and got logs in Splunk Any advice where is the problem or how should I debug this? Thanks. ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎05-06-2025 05:25 PM
Karma given to
View All