- Releases Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- SQL Developer Guide
- Python Developer Guide
- ETL Developer Guide
- FAQ
- Contact Us
- Releases Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- SQL Developer Guide
- Python Developer Guide
- ETL Developer Guide
- FAQ
- Contact Us
Configuring Running Log Collection for a Job
Last updated: 2023-11-07 17:13:06
You can set one or more CLS log topics for a Stream Compute Service cluster, so that you can view and search for logs on the log page of a job and select them for use by running logs of different jobs. You can also store job running logs of a Stream Compute Service cluster in COS, which, compared with CLS, costs less, but does not allow you to view and search for logs in real time.
Associating CLS with a cluster
On the details page of a cluster, you can configure CLS logsets and topics (3 at most) for the cluster.
Creating logsets and log topics
In the Stream Compute Service console, you can create your dedicated logsets and log topics (all prefixed with "Oceanus_"). When you need to select a logset, you can select an existing logset or create one.
Log topics created in the Stream Compute Service console contain special system settings and are not recommended for other products.
Selecting an existing log topic
When associating a log topic with a Stream Compute Service cluster, you can select an existing log topic, but it must be one created in the Stream Compute Service console.
Setting a default log collection method for a cluster
You can set a default log collection method for a cluster to simplify the setting of job parameters. A new job created after the default method is set will use the logset and log topic in the default configurations.
Setting a running log collection method for a job
For log collection with CLS, since multiple CLS log topics can be associated with a cluster, the parameter configurations of a new job need to specify the log topic to which the running logs of this job will be reported, or specify a default log collection method.
For log collection with COS, job logs will be stored in the COS bucket you associate with the cluster during its creation, and the log storage path is
job-running-log/.Setting a running log level for a job
You can set the log level of a job on its parameters page. Four log level options are available:
DEBUG, INFO, WARN, and ERROR. After a log level is set, the logs of the job will be output at this level. If no log level is available for selection, submit a ticket to upgrade your cluster first.Batch changing log levels of jobs
To batch changing the log levels of multiple jobs, select Jobs > Batch > Change log level in the console, select a log level (options:
DEBUG, INFO, WARN, and ERROR), and click Confirm. After this change, the logs of these jobs will be output at the new level. If no log level is available for selection, submit a ticket to upgrade your cluster first.
Yes
No
Was this page helpful?