Simple Log Service (SLS) and Cloud Parallel File Storage (CPFS) jointly provide the log analysis feature to collect CPFS for Lingjun access logs in real time. After collection, you can query, analyze, transform, and consume the logs. This topic describes the assets, billing, and limits of the log analysis feature.
Assets
-
Dedicated projects and dedicated Logstores
When you enable the log analysis feature, SLS automatically creates a project named nas-<Alibaba Cloud account ID>-<Region ID> in the same region as your CPFS for Lingjun file system, and creates a dedicated Logstore named nas-bmcpfs in that project.
-
Dedicated dashboards
Enabling the feature does not generate dedicated dashboards. To visualize query results, create a custom dashboard. For more information, see Create a dashboard.
Billing
If your Logstore uses the pay-by-feature billing mode, charges apply to storage, read traffic, the number of requests, data manipulation, and data shipping after logs are collected from CPFS for Lingjun to SLS. All fees appear in SLS bills. For more information, see Billable items for pay-by-feature.
If your Logstore uses the pay-by-ingested-data billing mode, charges apply to ingested raw data after logs are collected from CPFS for Lingjun to SLS. All fees appear in SLS bills. For more information, see Billable items of the pay-by-ingested-data mode.
Limits
Only CPFS for Lingjun V2.5.5 and later support the log analysis feature.
Audit logs are not generated in real time. After performing operations on the file system, wait 30 minutes before viewing the corresponding audit logs.
-
The full path in audit logs may be empty in the following scenarios. Run the
ls full pathcommand to resolve this issue.A directory or file was already open before the audit log feature was enabled and was not reopened after the feature was enabled.
After the audit log feature was enabled, files or directories were accessed using relative paths.
After a directory is renamed or moved to a different path, the parent path of files and subdirectories in that directory may still show the original path in audit logs. The file name and directory name remain correct. Run the preceding command to correct the full path.