Autonomous Linux Events

Use Autonomous Linux events to monitor instances to help identify and debug errors, anomalies, operational failures, reboots, and changes made to instances.

About
Viewing Events
Configuring Events
Note

Autonomous Linux events are different from events emitted by Autonomous Linux resources for the OCI Events service. For events emitted by resources, see OCI Events for OS Management Hub.

Critical Event Types

Autonomous Linux records critical events for the following issues. See also: What information is collected for critical events?.

Critical Event Type Description
Fatal Kernel Error (Kernel Panic) A Fatal Kernel Error (Kernel Panic) event occurs when the kernel fails to load upon detecting a fatal internal error. This error prevents the system from booting up and triggers a reboot.
Kernel OOPS A Kernel OOPS event occurs when the kernel detects an exception and triggers a reboot.
Known exploit detection A known exploit detection event occurs if an attacker attempts to exploit a CVE that Autonomous Linux has patched.

General Event Types

Autonomous Linux records events for the following issues.

Event Type Description
Agent

An agent event occurs when the agent on the instance:

  • Provides the service with the instance's package inventory
  • Uploads diagnostic content to the service for a critical event (when event collection is enabled)

An agent event occurs when:

  • There were changes made to the event collection settings
Ksplice update

A Ksplice update events occurs when the service:

  • Applies a Ksplice kernel update
  • Applies a Ksplice userspace update
Reboot

When a system is rebooted using Autonomous Linux, the service generates an event to reflect the status of the reboot operation. Possible statuses include:

  • Started
  • Succeeded
  • Failed
  • Succeeded after the timeout
Software update

A software update event occurs when the service:

  • Installs or removes packages
  • Applies updates
System administration Autonomous Linux detects an error that requires DNF or YUM cache cleanup, removal of locks, or RPM database rebuild. The service automatically corrects the issue and reports the results.

What information is collected for critical events?

To monitor for critical events, the Autonomous Linux service collects specific information from the instance using the following tools:

SOSreport

This utility is automatically configured in Autonomous Linux to collect critical system information from the following modules.

Note

The module information is based on SOSreport Release 3.9 (sos-3.9).

Ksplice

The following information is collected and submitted to the service for debugging:

  • kernel symbols
  • kernel modules
  • Ksplice update details
  • Ksplice Uptrack logs
OSWatcher (Autonomous Linux 7 and 8)

OSWatcher is automatically configured in Autonomous Linux 7 and 8 to collect system information periodically (Autonomous Linux 9 doesn't use OSWatcher). This utility runs common OS commands at regular intervals and outputs the information to a log file collected by the service. The commands tracked by the service are as follows.