Oracle Cloud Infrastructure Documentation

Understanding Autonomous Linux Events

Autonomous Linux provides instance monitoring that captures events to help quickly identify and debug anomalies, errors, and operational failures.

This topic gives an overview of the critical events detected by the Autonomous Linux service, describes what information is collected about events, and covers the following tasks:

  • Viewing events
  • Viewing event details, including the event report, collected files, and information about event recurrence
  • Creating a support request

Critical Events

Autonomous Linux triggers critical events for the issues shown in the following table.

Autonomous Linux 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.

About the Information Collected from an Instance

To monitor for critical events, the Autonomous Linux service collects and submits information from the instance.

The Oracle Autonomous Linux plugin gathers information from the following tools:

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

    SOSreport Module List
    • auditd
    • boot
    • cron
    • date
    • devicemapper
    • filesys
    • grub2
    • hardware
    • host
    • kernel
    • libraries
    • logs
    • lvm2
    • memory
    • networking
    • pam
    • pci
    • process
    • processor
    • rpm
    • sar
    • selinux
    • services
    • ssh
    • yum
    SOSreport Module Details
    SOSreport Module Information Type Included Files
    auditd Audit log files 
    /etc/audit/auditd.conf
/etc/audit/audit.rules
/var/log/audit/*
    boot Bootup details 
    /etc/milo.conf
/etc/silo.conf
/boot/efi/efi/redhat/elilo.conf
/etc/yaboot.conf
/boot/yaboot.conf
    cron Root cron commands 
    /etc/cron*
/etc/crontab
/var/log/cron
/var/spool/cron
    date Context data 
    /etc/localtime
    devicemapper Hardware details
    filesys List of all files in use 
    /proc/fs/*
/proc/mounts
/proc/filesystems
/proc/self/mounts
/proc/self/mountinfo
/proc/self/mountstats
/proc/[0-9]*/mountinfo
/etc/mtab
/etc/fstab
    grub2 Kernel setup and configuration 
    /boot/efi/EFI/*/grub.cfg
/boot/grub2/grub.cfg
/boot/grub2/grubenv
/boot/grub/grub.cfg
/boot/loader/entries
/etc/default/grub
/etc/grub2.cfg
/etc/grub.d/*
    hardware Hardware details 
    /proc/interrupts
/proc/irq
/proc/dma
/proc/devices
/proc/rtc
/var/log/mcelog
/sys/class/dmi/id/*
/sys/class/drm/*/edid
    host Host identification 
    /etc/sos.conf
/etc/hostid
    kernel System log files 
    /etc/conf.modules
/etc/modules.conf
/etc/modprobe.conf
/etc/modprobe.d
/etc/sysctl.conf
/etc/sysctl.d
/lib/modules/*/modules.dep
/lib/sysctl.d
/proc/cmdline
/proc/driver
/proc/kallsyms
/proc/lock*
/proc/buddyinfo
/proc/misc
/proc/modules
/proc/slabinfo
/proc/softirqs
/proc/sys/kernel/random/boot_id
/proc/sys/kernel/tainted
/proc/timer*
/proc/zoneinfo
/sys/firmware/acpi/*
/sys/kernel/debug/tracing/* 
/sys/kernel/livepatch/*
/sys/module/*/parameters
/sys/module/*/initstate
/sys/module/*/refcnt
/sys/module/*/taint
/sys/module/*/version
/sys/devices/system/clocksource/*/available_clocksource
/sys/devices/system/clocksource/*/current_clocksource
/sys/fs/pstore
/var/log/dmesg
    libraries List of shared libraries 
    /etc/ld.so.conf
/etc/ld.so.conf.d/*
    logs System log files 
    /etc/syslog.conf
/etc/rsyslog.conf
/etc/rsyslog.d
/run/log/journal/*
/var/log/auth.log
/var/log/auth.log.1
/var/log/auth.log.2*
/var/log/boot.log
/var/log/dist-upgrade
/var/log/installer
/var/log/journal/*
/var/log/kern.log
/var/log/kern.log.1
/var/log/kern.log.2*
/var/log/messages*
/var/log/secure*
/var/log/syslog
/var/log/syslog.1
/var/log/syslog.2*
/var/log/udev
/var/log/unattended-upgrades
    lvm2 Hardware details
    memory Hardware details 
    /proc/pci
/proc/meminfo
/proc/vmstat
/proc/swaps
/proc/slabinfo
/proc/pagetypeinfo
/proc/vmallocinfo
/sys/kernel/mm/ksm
/sys/kernel/mm/transparent_hugepage/enabled
    networking Network Identification 
    /etc/dnsmasq*
/etc/host*
/etc/inetd.conf
/etc/iproute2
/etc/network*
/etc/nftables
/etc/nftables.conf
/etc/nsswitch.conf
/etc/resolv.conf
/etc/sysconfig/nftables.conf
/etc/xinetd.conf
/etc/xinetd.d
/etc/yp.conf
/proc/net/*
/sys/class/net/*/device/numa_node
/sys/class/net/*/flags
/sys/class/net/*/statistics/*
    pam Login security settings 
    /etc/pam.d/*
/etc/security
    pci Hardware details 
    /proc/bus/pci
/proc/iomem
/proc/ioports
    process All running process details 
    /proc/sched_debug
/proc/stat
/proc/[0-9]*/smaps
    processor Hardware details 
    /proc/cpuinfo
/sys/class/cpuid
/sys/devices/system/cpu
    rpm Installed software 
    /var/lib/rpm/*
/var/log/rpmpkgs
    sar Resource and usage data 
    /var/log/sa/*
    selinux Security settings 
    /etc/sestatus.conf
/etc/selinux
/var/lib/selinux
    services All defined services 
    /etc/inittab
/etc/rc.d/*
/etc/rc.local
    ssh SSH configuration 
    /etc/ssh/ssh_config
/etc/ssh/sshd_config
    yum Installed software 
    /etc/pki/consumer/cert.pem
/etc/pki/entitlement/*.pem
/etc/pki/product/*.pem
/etc/yum/*
/etc/yum.repos.d/*
/etc/yum/pluginconf.d/*
/var/log/yum.log
    Note

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

  • OSWatcher: This utility is used to run 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.
    OSWatcher Commands
    • buddyinfo
    • cpuinfo
    • ifconfig
    • iostat
    • lscpu
    • mpstat
    • netst
    • pagetype
    • slabinfo
    • top
    • vmstat
    • zoneinfo

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

    • kernel symbols
    • kernel modules
    • Ksplice update details
    • Ksplice Uptrack logs

Viewing Events

To view a summary of events

  1. Open the navigation menu, click Compute, and then click Instances.
  2. Find the instance and click its name.
  3. On the Instance Details page, under Resources, click OS Management.
    In the OS Management section, the number of events (if any) that have been triggered on the instance are displayed under Events Summary.
  4. Click the number of events to view a summary of the events on the Managed Instance Details page.
    On the Managed Instance Details page, a summary of the events that occurred on the instance, including the event type and time of occurrence is displayed in the Events table.

Viewing Event Details

To view an event report

  1. Open the navigation menu, click Compute, and then click Instances.

  2. Find the instance and click its name.

  3. On the Instance Details page, under Resources, click OS Management.

    In the OS Management section, the number of events (if any) that have been triggered on the instance are displayed under Events Summary.

  4. Click the number of events to view a summary of the events on the Managed Instance Details page.

  5. In the Events table, click the event in the Summary column to display details about the event.

  6. On the Events Details page, under General Information, review the following information displayed about the event:

    • Reason: Provides additional information about the conditions that triggered the event.
    • Event Time: Time at which the event occurred.
    • Event Recurrence: Number of times the events reoccurred on instances managed by Autonomous Linux.
    • Operating System: Operating system running on the instance.
    • Kernel: Kernel boot version installed on disk.
    • Effective Kernel: Effective kernel version in memory based on the Ksplice updates applied to the kernel.

    On the Events Details page, you also have options to view a detailed event report, to view and download the collected files for the event, and to view information about event recurrence.

  7. Under Resources, click Report.

  8. Review the details in the Report table. The Report table displays additional information collected when the event occurred:

    • Stack Traces
    • Log Files
To view the collected files for the event

  1. Open the navigation menu, click Compute, and then click Instances.

  2. Find the instance and click its name.

  3. On the Instance Details page, under Resources, click OS Management.

    In the OS Management section, the number of events (if any) that have been triggered on the instance are displayed under Events Summary.

  4. Click the number of events to view a summary of the events on the Managed Instance Details page.

  5. In the Events table, click the event in the Summary column to display details about the event.

  6. On the Events Details page, under General Information, review the following information displayed about the event:

    • Reason: Provides additional information about the conditions that triggered the event.
    • Event Time: Time at which the event occurred.
    • Event Recurrence: Number of times the events reoccurred on instances managed by Autonomous Linux.
    • Operating System: Operating system running on the instance.
    • Kernel: Kernel boot version installed on disk.
    • Effective Kernel: Effective kernel version in memory based on the Ksplice updates applied to the kernel.

    On the Events Details page, you also have options to view a detailed event report, to view and download the collected files for the event, and to view information about event recurrence.

  7. Under Resources, click Collected Files.

  8. Review the details in the Collected Files table.

    The Collected Files table displays the following information:

    • Filename: Filename of zip bundle.
    • State: Possible states are as follows:
      • Available on instance and service: Indicates that the zip bundle is available both on the instance and by the Autonomous Linux service (default state for event collection).
      • Available on instance: Indicates that the zip bundle is available only on the instance. You see this state when event collection is disabled on the Autonomous Linux instance.
    • Location: File path to zip bundle on instance.
    • Size: File size of zip bundle.
    To download the collected files
    1. Click the Action icon (three dots).
    2. Select Download.
    To remove the collected files from the instance
    1. Click the Action icon (three dots).
    2. Select Remove from the instance.
    3. In the Remove collected files dialog box, click Delete.
      Note

      The collected files are removed for Autonomous Linux instance in the Console but is still available on the instance.
To view event recurrence

  1. Open the navigation menu, click Compute, and then click Instances.

  2. Find the instance and click its name.

  3. On the Instance Details page, under Resources, click OS Management.

    In the OS Management section, the number of events (if any) that have been triggered on the instance are displayed under Events Summary.

  4. Click the number of events to view a summary of the events on the Managed Instance Details page.

  5. In the Events table, click the event in the Summary column to display details about the event.

  6. On the Events Details page, under General Information, review the following information displayed about the event:

    • Reason: Provides additional information about the conditions that triggered the event.
    • Event Time: Time at which the event occurred.
    • Event Recurrence: Number of times the event recurred on instances managed by .
    • Operating System: Operating system running on the instance.
    • Kernel: Kernel boot version installed on disk.
    • Effective Kernel: Effective kernel version in memory based on the Ksplice updates applied to the kernel.

    On the Events Details page, you also have options to view a detailed event report, to view and download the collected files for the event, and to view information about event recurrence.

  7. Under Resources, click Event Recurrences.

  8. Review the details in the Event Recurrences table.

    The Event Recurrences table displays the following information:

    • Instances: Lists the instances that experienced the event.
    • Number of Events: Lists the numbers of times the instances experienced the event.
    • Location: File path to zip bundle on instance.
    • Size: File size of zip bundle.
  9. Click the row for an instance to see more details about event reoccurrence, including the event time associated with the first and last occurrence of the event.

Creating a Support Request

To create a customer support ticket

To track the status of a critical event, open a support ticket.

  1. On the Events Details page, click Create Support Request.

  2. Enter the following:

    • Issue Summary: Enter a title that summarizes your issue. Avoid entering confidential information.
    • Describe Your Issue: Provide the following information in the description field.
      • Tenancy OCID
      • Compartment OCID
      • Instance OCID
      • Log path
    • Select the severity level for this request.

  3. Click Create Request.

    Note

    For more information about creating support tickets, see Open a Support Ticket.

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use the following API operations to view details about Autonomous Linux events:

Use the following API operations to manage the information collected by the Autonomous Linux service for the Autonomous Linux instance:

For a full list of API operations available for Autonomous Linux, see OS Management API.