I also relaized it in this week from a log at a clinet. It was a oneagent extension not an active gate extension. I have not found any settings on the GUI for the restrictions.
I suggest to raise a support ticket or turn to the extension team. Maybe @diego_morales could provide a contact for you.
Hi @kiranraju ,
Thanks for reaching out. The OneAgent extension only collects queues/channels/listener metrics from those that were specified. However, it attempts to get availability status from the other ones on the same host. If it is not able to connect to check their availability, it just skips them.
No. It goes by running process on the host and checks for status on queue managers according to running process. It does not determine which QM to connect by access to MQM folders.
Are you experiencing performance or issues with this availability check? Could you explain? Perhaps we can enhance the extension for this.
The customer is seeing more logs in their MQ debug log file for the queue managers as it is writing the log every minute as mentioned below.
"AMQ8077W: Entity 'dtuser' has insufficient authority to access object EPED1
It is causing the problem to Analyse the logs for application specific errors and consuming log size.
Let me understand your question better. You inform that you configured 2 endpoints in the plugin (extension) and that when checking the log, you verify that it tries to connect other endpoints? Regardless of the user, the truth is that it makes no sense to search for a connection in unconfigured locations. It would be nice if you post the version of your IBM MQ extension, the snippet of the log which could be the output of the command: #tailf -100 /var/lib/dynatrace/remotepluginmodule/log/remoteplugin/custom.remote.python.ibmmq_java/IBM_MQ_Java_Plugin.log. Also images of the endpoints that are configured in the extension's UI.
With this information it is easier to help you.
From what I see is a clear error in user permissions. I was talking to the MQ specialist here at my institution. It informs that in this situation the user "dtuser" must be placed in the "mqm" group of the server where the agent runs.
Can you do this test?