Hope this helps. Let me know if you have any other questions.
Hello @Diego M.
Thank you for providing me the requested information.
Maybe, I will come back with a few more questions, or to ask for more clarification after discussing it with the IBM MQ expert.
Right now, the only question coming from the top of my mind that our 80+% infrastructure based on SUN Solaris, and log monitoring not available at the moment.
In this case, perhaps a custom plugin that scrubs this data might be viable for you. If possible, you could develop it using the plugin SDK or have Dynatrace develop it. If the latter, please contact your account manager so that this effort can be scoped.
Hey @Babar Q. Log Monitoring Product Manager. We plan to deliver more generic log ingest later this year (Q2 this calendar year) so our customers can easily ship log data with standard drivers (fluentd, syslog etc.), cloud service logs and through API. I know that this is not an answer for your current needs but wanted to give you perspective on upcoming enhancements.
I'm not an MQ expert by any means, but from what I understand, the audit queues are referred to auditing configuration changes or authentication failures or command failures for example. These are configured on your queue manager depending on what sort of events you want to create an audit trail for. Some of them for example are SYSTEM.ADMIN.CONFIG.EVENT, SYSTEM.ADMIN.COMMAND.EVENT, SYSTEM.ADMIN.QMGR.EVENT, SYSTEM.ADMIN.CHANNEL.EVENT.
Just to clarify, the plugin does not place anything directly in these queues. This is all handled by MQ automatically. However, the user you are using to connect may want to write to these on the MQ server side because MQ does other admin tasks when executing PCF commands, so that's why.