This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
We have both aix and linux agents. We had both agents successfully writing to our syslog for quite some time (> 9 months). Recently (perhaps 6 weeks ago), after we upgraded our agents, the aix agent no longer writes to the syslog. The linux agent however continues to write to the syslog as expected. Support Request 30210 was opened for this, but we are being told this was never a supported function so the fact that it is no longer working but used to is not something support can help with and we need to open up a features request.
This is a feature request to fully support syslog and FIX the issue with the current aix agent that is not writing to syslog.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thanks for the feedback, I will set this to "Functionality already exists" then.
Turns out, the issue was just that after a recent upgrade replaced the config file, we missed uncommenting out these two lines:
log4j2.rootLogger.appenderRef.Syslog.ref = Syslog
log4j2.rootLogger.appenderRef.Syslog.level = INFO
So the product does indeed support this and we have it working again.
This idea can be closed.