Question 2

Explanation

https://docs.oracle.com/en-us/iaas/logging-analytics/doc/manage-source-entity-association.html

Manage Source-Entity Association

When you use Management Agents to continuously collect logs, you must configure a source-entity association to enable a source for specific entities to collect the log data.

Topics:

Configure New Source-Entity Association

Enable Auto-Association for a Source

Stop Log Collection from an Entity

Disable Auto-Association for a Source

Configure New Source-Entity Association

Configure new source-entity associations to enable continuous log collection after installing the Management Agent. To configure entity associations on a large scale, you can use the source-entity association APIs.

For more details about the source-entity association APIs, see Logging Analytics API.

Open the navigation menu and click Observability & Management. Under Logging Analytics, click Administration. The Administration Overview page opens.

The administration resources are listed in the left hand navigation pane under Resources. Click Sources.

The sources listing page will show all Oracle-defined and custom defined sources. You can search and identify one that you want to use.

Click the source name for which you want to create the source-entity association. The source details page opens. Locate the Resources section on the left side of the page.

Select the compartment on the left of the Source detail page. This will limit the entities visible to you based on the compartment you selected.

Click Unassociated Entities to view the entities that are eligible for association with this source. The entities listed are those which of the entity-type specified in the source definition and are available in the selected compartment.

The entities which are not eligible for association with this source are listed in the Ineligible Entities section. Typically, the reasons for ineligibility are the absence of Management Agent on the host, it not being ready for log collection, agent validation pending, or agent policy issues. After the Management Agent is installed successfully on the entity host and the entity is configured to use the Management Agent, the entity disappears from the Ineligible Entities list and appears in the Unassociated Entities list.

Select one or more unassociated entities to associate with this source and click Add Association.

The Add Association dialog box opens.

Select the compartment that contains the log group in which the log data should be located after it is collected and indexed.

Select the log group that you created earlier during the setup.

To create a new log group, select the compartment, and click Create Log Group. In the dialog box, enter the name and description. Click Create.

Click Submit.

The selected entity is now moved to the Associated Entities section where the status of the association is displayed. If the source-entity association task failed, then click Retry Association.

Collection instructions will be sent down to the agent that is monitoring this entity as defined earlier and the log collection will start. Go to Agent Collection Warnings section to view the warnings for log collection. Note that the list of warnings correspond to all the association entities for this source.

If you have any issues with the management agent collecting logs, ensure that the log files that are monitored are readable to the mgmt_agent user that the Management Agent runs as. Wait for a few minutes to view the logs in the Log Explorer. When collecting logs from the OS files, the older log files are collected first. Therefore, you may see older logs loaded before the newer logs. After the agent has collected the historic logs, you will start seeing only newer logs being collected.