Prerequisites:
Support device type/policy:
Symptoms:
User name in agent property must be same user login to https://app.ninjarmm.com
2019-02-26 13:46:17.618 INFO [Quartz[0]-36738] com.quest.monitoring.agent.ninja.NMSAgentImpl - collectAlertData: reader.runWebService returned: NmsAlertDataReader: url = https://_your_NMS_agent _HOST:5053/aspx/FoglightWs/AgentService.asmx
2019-02-26 13:46:17.618 INFO [Quartz[0]-36738] com.quest.monitoring.agent.ninja.NMSAgentImpl - collectAlertData: reader.runWebService returned: NmsAlertDataReader: client.send completed
2019-02-26 13:46:17.618 INFO [Quartz[0]-36738] com.quest.monitoring.agent.ninja.NMSAgentImpl - collectAlertData: reader.runWebService returned: NmsAlertDataReader: loginResult = Success
2019-02-26 13:46:17.618 INFO [Quartz[0]-36738] com.quest.monitoring.agent.ninja.NMSAgentImpl - collectAlertData: reader.runWebService returned: NmsAlertDataReader: completed alertCount = 0
2019-02-26 13:46:17.618 INFO [Quartz[0]-36738] com.quest.monitoring.agent.ninja.NMSAgentImpl - collectAlertData: submitted 0 data points
2019-02-26 13:46:17.618 INFO [Quartz[0]-36738] com.quest.monitoring.agent.ninja.NMSAgentImpl - collectAlertData: filtered 6 data points
Make sure device have NMS-Firewall, NMS-Router or NMS-Switch policy assigned for your device and should not have NMS - Other policy
Make sure device are selected forward to Foglight at Ninja Network Management Studio
Make sure you can see full CPU and memory info from https://app.ninjarmm.com for your device. Foglight will not display devices which have no CPU or memory info from Ninja. one common issue here is have incorrect SNMP community setup during the network discovery
To rediscover network and add new SNMP credential for your device:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center