The agents are blacked out, but according to the blackout schedule they are suppose to be active.
When checking the blackout setup via command line tool, you will find several schedules assigned to the blackout, while the Foglight UI displays only one schedule:
./fglcmd.sh -usr -pwd -srv -cmd agent:showschedule -agentid 2
ID: 2
Host: Foglight Agent Manager
Name:
Type: DB_Oracle
Status: Active/Collecting data
Blackout Schedules:
Test (id: 19bc1230-cf7d-4b48-bd13-0a61cd3797d0) [in effect at the moment]
Weekends (id: 94e5034b-42f1-448d-8b88-291915234109)
Hourly (id: 1e698670-f5e1-449e-94ba-942a76795602)
Three schedules have been assigned to this blackout and the first one is active, so the agent is blacked out.
When changing the schedule of a blackout, it is not possible to add more than one schedule to the blackout in the Foglight UI. So the UI is listing only the latest applied schedule of the blackout, but not all assigned blackouts.
In addition to the features available on the blackout management dashboards, topology and agent blackouts can also be configured using the command-line interface. However, the mechanism for creating blackouts from the command line is independent. It is not recommended to use both methods on the same Foglight Management Server.
The following command can be used to manage blackouts configured from the command-interface:
To get all configured blackouts
$FMS_HOME/bin/fglcmd.sh -usr -pwd -srv -cmd agent:showschedule
To remove a schedule from a blackout
$FMS_HOME/bin/fglcmd.sh -usr -pwd -srv -cmd agent:setschedule -agentid -remove -schedulename
To add a schedule to a blackout
$FMS_HOME/bin/fglcmd.sh -usr -pwd -srv -cmd agent:setschedule -agentid -schedulename
To get all options of "agent:setschedule"
$FMS_HOME/bin/fglcmd.sh -usr -pwd -srv -cmd agent:setschedule -?
