A credential alarm like this may be generated:
Or while reviewing the agent log at $FGLAM_HOME\logs\HostAgents\x.x.x.x\WindowsAgent\Monitor@server.com_YYYY-MM-DD_hhmmss_001.log, the following message can be observed:
YYYY-MM-DD hh:mm:ss.SSS ERROR [Quartz-5100] com.quest.remoteos.SystemMonitorImpl - The agent failed to collect data for server.com.
com.quest.glue.api.services.NoValidCredentialPolicyException: Unable to use any of the 1 credentials to connect to server.com because credential policy restricted their use.
As an example when adding a new OS monitor from the Infrastructure Dashboard and configuring a new credential, by default it will add a credential policy Failure Rate - Max Failure Count=3 and Time Period=1 hours so when the monitoring agent host connection is broken, after 3 times, the server will mark the credential as invalid and restrict its usage.
Note: When entering the database connection credentials, that configuration will be stored in the agent's properties. Only the OS credentials will be stored in the lock-box (Credentials Management Dashboard).
For additional information refer to the "Edit credential policies" section in the Foglight - Administration and Configuration Guide .
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center