False Oracle alarm: "Listener status: Listener LISTENER is not available" (4252083)

Getting wrong listener alarms: "Listener status: Listener LISTENER is not available"

The default listener is not being used, a named listener is configured.

How can we configure Foglight to monitor a named listener instead of the default listener?

CAUSE 1

The default listener is not being used and named listener is configured, but the listeners monitoring configuration is set to the default "LISTENER".

CAUSE 2

The named listener is properly set in the Foglight, but addition spaces are present after the listener name.

Please follow the steps below:

1. Navigate to the Databases Overview dashboard
2. Select the problematic Oracle agent
3. Click on "Settings | Administration"
4. On the left hand select "Listeners Monitoring"
5. Use the "Add Listener", "Edit Listener" and "Delete Listener" to correct the listener names
6. Click the "Save changes" button to save the change

Alternatively:

1. Go to "Administration | Agents | Agent Status"
2. Mark the Oracle agent and click on "Edit Properties"
3. Go to "Listener name"
4. Click on "Edit" to modify the listener name List
5. In the popup window click on "Add new row" to add the named listener. Similar entries can be added and deleted.
6. Exit the popup window and click the "Back to Agent Status" button
7. Deactivate and activate the Agent

• Confirm Listener name on the instance by executing "lsnrctl status" command on the Instance host, being sure to note and specify the listener name and correct case in Foglight.
• After the listener names is corrected, the topology may need to be cleaned to remove the old listener. Topology object to look for is under: "All Agents[]-->usability-->listeners_status[]-->listener_status"; the last updated time can be used to confirm the listener object that is being used.