Azure ActiveMQ (apmia) agents that reported on-prem are not reporting in Dx SaaS
search cancel

Azure ActiveMQ (apmia) agents that reported on-prem are not reporting in Dx SaaS

book

Article ID: 228226

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

We have APMIA agents installed in Azure servers that were reporting on-prem prior to the Dx SaaS conversion. Now, the servers appear in Dx SaaS, but no ActiveMQ metrics are reporting. Agent release is Release 20.9.0.13 ( 990013 ).

Environment

Release : 20.9

Component : Agent

Resolution

I looked at the logs and the Agent log is filled with these errors.  The python script is having an issue with the hostname.

[INFO] [IntroscopeAgent.EPAgent AMQ] The process started by plugin AMQ was [ERROR] [IntroscopeAgent.EPAgent AMQ] The stateful plugin 'AMQ' has unexpectedly quit.
[ERROR] [IntroscopeAgent.InfrastructureAgent] The stateful plugin 'AMQ' is being restarted.
[ERROR] [IntroscopeAgent.EPAgent AMQ] [ stderr ] Traceback (most recent call last):
[ERROR] [IntroscopeAgent.EPAgent AMQ] [ stderr ]   File "/opt/wily/apmia/epaplugins/activeMQ.py", line 307, in <module>
[ERROR] [IntroscopeAgent.EPAgent AMQ] [ stderr ]     main(sys.argv)
[ERROR] [IntroscopeAgent.EPAgent AMQ] [ stderr ]   File "/opt/wily/apmia/epaplugins/activeMQ.py", line 254, in main
[ERROR] [IntroscopeAgent.EPAgent AMQ] [ stderr ]     url = "http://{0}:{1}/apm/metricFeed".format(options.hostname,
[ERROR] [IntroscopeAgent.EPAgent AMQ] [ stderr ] AttributeError: Values instance has no attribute 'hostname'

After fixing the Python script, the issue was resolved.