1) Login to Foglight UI
2) Navigate to Administration | Tooling | Script Editor
3) In the Query Window scroll down to agent name | select it and click the List Instance button
In the Instance display you will now see the Instances listed by Unique ID number and agent@hostname, the Instance ID number will be used in the below fglcmd command
4 )Having a remote session to the Foglight Server and use the fglcmd command in the %FGLHOME%\bin directory to issue the command to blackout by instance ID
Enable the blackout
Windows
fglcmd.bat -usr foglight -pwd foglight -cmd topology:blackoutobject -object 66a799de-9158-43e1-91bc-a4d717575e1a -schedulename Always
Unix
./fglcmd.sh -usr foglight -pwd foglight -cmd topology:blackoutobject -object 66a799de-9158-43e1-91bc-a4d717575e1a -schedulename Always
Remove the blackout
Windows
fglcmd.bat -usr foglight -pwd foglight -cmd topology:blackoutobject -object 66a799de-9158-43e1-91bc-a4d717575e1a -schedulename Always -remove
Unix
./fglcmd.sh -usr foglight -pwd foglight -cmd topology:blackoutobject -object 66a799de-9158-43e1-91bc-a4d717575e1a -schedulename Always -remove
In this example a blackout was applied to the Windows agent, this is the output of the command when entered:
C:Quest_Software\Foglight\bin>fglcmd.bat -usr foglight -pwd foglight -cmd topology:blackoutobject -object 66a799de-9158-43e1-91bc-a4d717575e1a -schedulename Always
Updated the following topology objects:
66a799de-9158-43e1-91bc-a4d717575e1a: Windows_SystemAgent 'Windows_Win2008@hostname.domain.org
Note: You can also verify that the blackout is in place by selecting the Instance ID in the Script Editor and scrolling down to the " isBlackedOut " entry, False = not blacked out, True = is blacked out.
Any -schedulename can be used that is currently defined in the Manage Rules dashboard.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center