-
Titre
Alarm Failed to validate Policy of Type com.quest.forge.credentials.authFailureRate -
Description
A similar alarm like this may show up:
Alarm Message: Service CredentialService: Failed to validate Policy: 85z1938d-a66f-4n28-m526-2029e3086078 of Type: com.quest.forge.credentials.authFailureRateRule: Credential Management EventSeverity: Fatal Severity
Or while checking FGLAM\logs\HostAgents\x.x.x.x\WindowsAgent\Monitor@server.com_yyyy-mm-dd_hhmmss_001.log, the following message can be observed:2018-12-20 15:35:57.332 ERROR [Quartz[0]-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 -
Cause
Credential Policy configured prevents the agent to collect metrics. -
Résolution
As an example in Infrastructure Agent, when creating a credential, by default if the policy is enabled, it will add FailureRatePolicy(3 times/1hour) to each credential. So when the agentmonitor host connection is broken, after 3 times, it will mark the credential policy not valid, then the Fglam(Foglight Agent Manager) will mark the credential as unusable. The connection might be failure if you have too many agent instances connecting.
Suggestions:- Make sure the username has admin privileges in the OS server to monitor the OS metrics.- If working with database agents and Infrastructure also, always remember to save changes when validating or testing a database connection.- Also if working with database agents, always validate the database / OS connection using database dashboard.- Suggestion is to remove the Failure Rate, change to a better value, or create a lock-box without policies.
Then check the hosts dashboard or agent log again.Note: When you enter the database 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).
Reference Guide -
Informations supplémentaires
Also in Windows from command prompt the following command can be ran to check that the username is not locked at the domain level:
net user Usernamex /domain.com
Note: Change Usernamex for the username you use in Foglight.
Change domain.com for your domain.