Through the function processing service, you can quickly complete complex log processing tasks such as execution log collection, ETL (extraction-transformation-loading), and message dumping for various Tencent Cloud services like CVM. Function processing is an async process. All data collected into CLS can be delivered to SCF for consumption and processing through configurations. You only need to complete simple configurations in the CLS console to connect CLS to SCF.
The source log data can be submitted to SCF through a CLS trigger, and then data processing and analysis, event triggering, and auto scaling can be implemented through function computing of Serverless Framework. The entire workflow requires no OPS and is pay-as-you-go as shown below:
Advantages of Function Processing
Data can be collected, stored, processed, analyzed, and displayed in a one-stop manner.
Log processing tasks are fully managed and can be triggered regularly and retried automatically.
More and more built-in function templates are added to reduce the development costs for log processing in popular use cases.
Data processing logic and custom code logic are provided based on SCF.
Computing power is provided based on SCF, with features such as auto scaling, OPS-free usage, and pay-as-you-go billing.
Multi-scenario Function Processing Practices
CLS can send data in a log topic to SCF for processing through a CLS trigger to satisfy the needs of various use cases such as log processing and log cleansing, as detailed below: |
| Log data is cleansed, processed, or transformed through SCF |
| Log data is cleansed and delivered to CKafka through SCF |
| Log data is cleansed and delivered to COS through SCF |
| Log data is delivered to ES through SCF |
Note:
Data is delivered to SCF, which incurs corresponding computation fees. For billing details, please see Billing Overview.
Was this page helpful?