The Foglight console is slow, overload messages are reported, the CPU usage on the FMS host is high, and a script associated with the Event Log rule is taking a lot of invocation time. (4257801)

Tchater maintenant avec le support

Obtenir une aide instantanée
Terminer l’enregistrement

Se connecter

Demander les tarifs

Contacter le service des ventes

Retour

Commentaire envoyé

Cet article vous a-t-il à résoudre un problème ?

Sélectionner une évaluation

Titre

The Foglight console is slow, overload messages are reported, the CPU usage on the FMS host is high, and a script associated with the Event Log rule is taking a lot of invocation time.
Description

The Foglight console is slow.

The CPU usage on the FMS host has increased markedly. The CPU usage varies from about 100% - 400% on the Linux host.

The problem was noted after deploying WindowsAgents.

"overload" messages like the following are reported in the Management server logs.
2016-04-25 20:38:12.919 WARN    [QuartzScheduler.Monitor_Worker-4] com.quest.nitro.service.data.DataService - The server has reached an overload state. 4,717 batches of data have been discarded.

The "Total Top Script Invocation Time" graph in the Performance Report indicates a script associated with the Event Log rule is taking a lot of invocation time (on the order of days):

    Cartridge_Infrastructure_Rule_Event_Log_Severity_Fire_Expression_message_script

Thread dumps collected list many threads that reference the same script:

   Cartridge_Infrastructure_Rule_Event_Log_Severity_Fire_Expression_message_script

Following is an excerpt of an example thread that references the script:
"Data-3-thread-1285184" #2442783 prio=5 os_prio=0 tid=0x00007f93c400f800 nid=0x4ef2 runnable [0x00007f93a587a000]
   java.lang.Thread.State: RUNNABLE
   at java.util.Arrays.copyOfRange(Arrays.java:3664)
   at java.lang.String.<init>(String.java:201)
   at java.lang.StringBuilder.toString(StringBuilder.java:407)
   at org.codehaus.groovy.runtime.StringGroovyMethods.plus(StringGroovyMethods.java:2450)
   at org.codehaus.groovy.runtime.dgm$1009.invoke(Unknown Source)
   at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
   at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
   at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
   at Cartridge_Infrastructure_Rule_Event_Log_Severity_Fire_Expression_message_script_b61c2769d4cf9e50be08bff5058d766e.run(Cartridge_Infrastructure_Rule_Event_Log_Severity_Fire_Expression_message_script_b61c2769d4cf9e50be08bff5058d766e.groovy:18)
   at com.quest.nitro.service.scripting.groovy.GroovyScript.exec(GroovyScript.java:149)
...
Cause

The "Event Log" rule caused the overload. All the data processing threads were invoking the Groovy script for the "message" expression on the rule. All the threads were concatenating strings to assemble the message.

It could be that there were a lot of events, or events with a lot of text, which then caused the rule to generate a very large message which was expensive to assemble.
Résolution

RESOLUTION 1: Disable the Event Log rule.

RESOLUTION 2: Filter the events collected by the WindowAgent so that only information on Events of interest is collected.

Commentaire envoyé

Cet article vous a-t-il à résoudre un problème ?

Sélectionner une évaluation

Demander un article de la base de connaissances

Contenu recommandé

Produit(s) :: Foglight
6.1.0, 6.0.0, 5.9.8, 5.9.7, 5.9.5, 5.9.4, 5.9.3, 5.9.2, 5.7.5, 5.7.1; Foglight for Databases
6.1.0, 6.0.0, 5.9.7, 5.9.5, 5.9.4, 5.9.3, 5.9.2; Foglight for Virtualization Enterprise Edition
8.4, 8.3, 8.2, 8.0.1, 8.0

Sujet(s) :: Troubleshooting

Historique de l’article :: Créé le : 6/17/2016
Dernière mise à jour le : 5/7/2023

Rechercher tous les articles

Veuillez sélectionner votre produit

Afin de mieux répondre à vos besoins, précisez l'objet du tchat:

Solutions recommandées pour votre problème

The Foglight console is slow, overload messages are reported, the CPU usage on the FMS host is high, and a script associated with the Event Log rule is taking a lot of invocation time. (4257801)

Titre

Description

Cause

Résolution

Leave a Comment