Hello Solace Community,
We are looking for a way to export the entries from the acl-log
and no-subscription-match-log
from our brokers so they can be centrally collected and analyzed.
We are offering “Solace-as-a-Service” within our company, deploying brokers in Kubernetes for various internal teams managebale via a self-service portal. To empower these teams to troubleshoot potential configuration errors themselves, providing them access to these specific logs would be incredibly helpful.
Currently, these logs are only available through the broker’s CLI, and for security and operational reasons, we cannot grant direct CLI access to all our users. Our goal is to forward these logs to our central logging platform, where we can then provide access through a dedicated API or a metrics dashboard.
We have already investigated the standard syslog events for ACLs. However, these seem to only provide a notification that a new entry has been added, without including the meaningful details of the log entry itself.
Our Question: Is there a recommended method to access these logs without using the CLI? We have considered two potential approaches:
-
Is it possible to configure the broker to publish these log entries as messages to a specific topic on the broker itself?
-
Alternatively, can the broker be forced to write these logs to
stdout
or a file path? This would allow a standard log collection agent in Kubernetes (like Fluent Bit) to pick them up and forward them.
Any guidance, best practices, or alternative suggestions on how to achieve this would be greatly appreciated.
E.g. here was a similar question regarding acl logs but the answer also points to the syslog.
Thank you!
Greetings,
JFG.
P.S. I assume that SEMPv1 works, but our no-subscription-match logs can rollate fast if multiple new teams are onboarding which means meaningful information is lost if we do not catch it between request intervals. AS we also use SEMP to scrape monitor metrics and there are regulations to not overload the broker I was hoping for a more “native” way through stdout / file / events.