Simple Log Service (SLS) and Cloud Parallel File Storage (CPFS) jointly launch the log analysis feature. You can use the feature to collect CPFS for Lingjun access logs in real time. You can also query, analyze, transform, and consume the collected logs. This topic describes the assets, billing, and limits of the log analysis feature.
Assets
Dedicated projects and dedicated Logstores
After you enable the log analysis feature, SLS creates a project named in the nas-<Alibaba Cloud account ID>-<Region ID> format in the region in which your CPFS for Lingjun file system resides and then creates a dedicated Logstore named nas-bmcpfs in the project.
Dedicated dashboards
After you enable the feature, SLS does not generate dedicated dashboards. You can create a custom dashboard to visualize query results. For more information, see Create a dashboard.
Billing
If your Logstore uses the pay-by-feature billing mode, you are charged for storage, read traffic, the number of requests, data manipulation, and data shipping after the logs are collected from CPFS for Lingjun to SLS. The fees are included in the bills of SLS. For more information, see Billable items of pay-by-feature.
If your Logstore uses the pay-by-ingested-data billing mode, you are charged for ingested raw data after the logs are collected from CPFS for Lingjun to SLS. The fees are included in the bills of SLS. For more information, see Billable items of pay-by-ingested-data.
Limits
Only CPFS for Lingjun V2.5.5 and later support the log analysis feature.
Audit logs are not generated in real time. To view audit logs, you need to wait for 30 minutes after you perform operations on the file system.
Audit logs do not contain data flows.
In the following scenarios, the full path of audit logs may be empty. You can run the
ls full path
command to resolve this issue.The directory and file are already opened before the audit log feature is enabled and are not reopened after the feature is enabled.
After the audit log feature is enabled, files and directories that are opened from relative paths are always used.
After a directory is renamed or moved to another path, the parent path of the files and subdirectories in the directory may still be the original path in the audit log, but the file name and directory name are correct. In this case, you can correct the full path of the files and subdirectories by running the preceding command.