🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

Missing log level in the remote syslog server log files

Manikanta
Manikanta Member Posts: 17 ✭
in PubSub+ Event Broker #1

On our solace appliances we have configured to send logs to our syslog servers. We are receiving them but in the log messages the log level and destination is missing. Do anyone have any idea why the logs not printing log level/destination on our remote syslog servers?
We can see log level/destination on the solace appliance.
Log example on our syslog server:
2020-12-07T15:18:24-06:00 appliance1 root[2222]: SEMP/mgmt xx.xx.xx.xx user 15:18:24 15:18:24 show queue name=* vpn-name=xxxxxxxxxx rates durable following queue-name-index-param=xxxxx vpn-id-index-param=10 count num-elements=500
Thank you

Tagged:

Comments

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    #2

    Probably because you are not printing the severity..?
    What syslog server are you using?
    What is your syslog configuration?
    What does your output format/template look like?

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #3

    Hi @Manikanta, that looks like a command log entry, for which the syslog docs are here. As Aaron says, we're almost certainly sending you the severity, for instance, but I suspect there's a configuration on your syslog server that is suppressing its output to the log.

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    #4

    Is related to this? Got raised at almost the exact same time: https://github.com/aaron-613/solace-logging-config/issues/4

  • Manikanta
    Manikanta Member Posts: 17 ✭
    #5

    Yes, same issue. It got resolved. Thank you @Aaron and @TomF .

Categories

This Month's Leaders

This Week's Leaders