26 Feb 2024 10:09 PM
I’m looking to be able to find the logs of requests to the /communication endpoints on cluster ActiveGates and embedded cluster ActiveGates in a Dynatrace Managed solution so we can do some analytics on originating connections.
We can see in the nginx logs all the user interactions with the GUI (nginx access logs), and API (Audit logs), however, this doesn’t seem to capture anything going to the /communications endpoints that are initiated from the OneAgents and other ActiveGates.
Is there a log file that I can turn on that will capture this or is this hidden somewhere I can see today?
Thanks for any direction or advise.
Solved! Go to Solution.
27 Feb 2024 01:56 PM
You would hope right? But no, there are no logs in the log directory on the activegate that show where connections to the /communication endpoint originated that I can find. Just the rest API logs.
27 Feb 2024 02:10 PM
Hi,
If someone does not provide you a better answer than mine, I would suggest to raise a support ticket.
Just in case debug logs or similar can be generated.
Best regards
27 Feb 2024 06:28 PM
That's what I'm hoping is that we can enable a higher level of logging through some configuration setting. Hoping that someone in the commmunity would have needed this before.
I did notice that the managed cluster nginx log configuration explicitly disables logging on /communication endpoints.
but these logs also do not exist on activegates, only cluster nodes.
location /communication {
if ($local_tag = true) {
proxy_pass http://local_server_http;
}
if ($local_tag = false) {
proxy_pass http://local_ag;
}
access_log off;
error_page 500 502 503 504 /small_error_50x.html;
}
27 Feb 2024 09:28 PM
@Sean_Bridges As suggested by @AntonPineiro support ticket is the best option in this scenario.But one option I would suggest is to check OneAgent health, where you can see which OneAgent is connected to which ActiveGate. If this doesn't help, then the last resort would be a support ticket.
Thanks,
Tijust
05 Mar 2024 02:46 PM
After opening a support ticket, it appears the answer that there are not any system logs for this.