upload-log-events-file
¶
Description¶
Accepts log events for processing by Logging Analytics.
Required Parameters¶
-
--file
[text]
¶
Log data file. Example: --file /Users/me/myfile.txt
-
--log-group-id
[text]
¶
The log group OCID that gets mapped to the uploaded logs.
-
--namespace-name
,
--namespace
,
-ns
[text]
¶
The Logging Analytics namespace used for the request.
Optional Parameters¶
-
--content-type
[text]
¶
The content type of the log data.
-
--from-json
[text]
¶
Provide input to this command as a JSON document from a file using the file://path-to/file syntax.
The --generate-full-command-json-input
option can be used to generate a sample json file to be used with this command option. The key names are pre-populated and match the command option names (converted to camelCase format, e.g. compartment-id --> compartmentId), while the values of the keys need to be populated by the user before using the sample file as an input to this command. For any command option that accepts multiple values, the value of the key can be a JSON array.
Options can still be provided on the command line. If an option exists in both the JSON document and the command line then the command line specified value will be used.
For examples on usage of this option, please see our "using CLI with advanced JSON options" link: https://docs.cloud.oracle.com/iaas/Content/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
-
--log-set
[text]
¶
The log set that gets associated with the uploaded logs.
-
--payload-type
[text]
¶
Identifies the type of request payload.
Accepted values are:
GZIP, JSON, ZIP
Global Parameters¶
Use oci --help
for help on global parameters.
--auth-purpose
, --auth
, --cert-bundle
, --cli-rc-file
, --config-file
, --debug
, --defaults-file
, --endpoint
, --generate-full-command-json-input
, --generate-param-json-input
, --help
, --latest-version
, --no-retry
, --opc-client-request-id
, --opc-request-id
, --output
, --profile
, --query
, --raw-output
, --region
, --release-info
, --request-id
, --version
, -?
, -d
, -h
, -v