Displays a list of events or types of events.
event_log ‑list [‑details] { ‑eventTypes | [‑severity severity‑value [, severity‑value ]... ] [‑before date‑time [‑startingIndex starting‑event‑index]] [‑after date‑time] [‑eventType event‑type] [‑category category‑value [, category‑value]... ] [‑eventCount number‑of‑events] [‑internal] } [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}] [{‑outputformat | ‑o} { text | xml }] [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]
The event_log ‑list command returns a listing of Oracle FS System events.
You can list a block of events by specifying the index of the first log entry and the number of log entries following the first log entry that meet your selection criteria. Use -before with ‑startingIndex to specify the starting point to ensure that new events that are being generated do not effect the results. Then use ‑eventCount to specify the number of log entries. Combined, the values that you specify for the ‑startingIndex option and the ‑eventCount option determine the ending index.
Events by severity: informational, warning, or critical
Events that were logged after a start date
Events that were logged before an end date
Events of the specified type
Events by category: security, audit, or system
A limited number of events
Internal system events that are not generated by administrators
Category
Severity
Short Description
Long Description
Security
Audit
System
Displays the details of each event or event type.
Limits the number of events returned to the value specified. The most recent events are returned first.
Displays the events in the event log that match the specified event type.
Displays a list of all known event types. If used with the ‑details option, the ‑eventTypes option also displays a description of each event.
Displays internal system events.
Defines a position within the event log from which to start listing events. Set the position by counting backwards in time. The most recent event has the starting index value of 1. You must use ‑startingIndex with the ‑before option to avoid dropping events from an event log request while new events are being generated.
The following global options can be used for fully formed fscli commands:
The command completes successfully.
The command returns with an error.
The session times out.
Inspects the validity of the command syntax, not the semantics. Used to test the structure of a command without running the command. Does not determine whether errors would be produced if you issue a structurally correct command with the input provided.
Directs the CLI to prompt you to supply a session key when you issue the command. The CLI displays Sessionkey: as the prompt. To obtain a session key, log in with the ‑returnKey option specified. After the session is established, the session key is displayed in STDOUT. If you request a session key, the ‑sessionkey option is required syntax for all commands that are issued in a given session. In environments with more than one Oracle FS System, the session key is used to determine to which Oracle FS System to direct the command for validation. Session keys are also used to establish two or more CLI sessions when using a shared administrator account.
The severity of the event.
The timestamp of the event in Universal Coordinated Time (UTC).
The name of the event.
A short description of the cause of the event.
Local filename: Oracle_FS_events_2013.08.07
$ fscli event_log ‑list > Oracle_FS_events_2013.08.07