Metrics Generated from Logs
This section describes the total rule quantity and restrictions of metrics generated based on logs in LTS.
Category |
Item |
Description |
Remarks |
---|---|---|---|
Metric generation |
Total number of metric generation rules allowed in an account |
By default, the maximum number of rules allowed for an account is 10, which is limited by the metadata at the software layer.
NOTE:
|
N/A |
Stable log rate of one metric generation rule |
≤ 40 MB/s (By default, one background task is assigned to one metric generation rule.) |
If your source log traffic exceeds the limit, submit a service ticket to increase background tasks for each rule. |
|
Peak log rate of one metric generation rule |
≤ 50 MB/s (By default, one background task is assigned to one metric generation rule.) |
If your source log traffic exceeds the limit, submit a service ticket to increase background tasks for each rule. |
|
Parameters for configuring metric generation rules |
|
N/A |
|
Log time |
The time difference between the log time and the LTS system time must be smaller than 1 hour. Otherwise, the task fails to be executed and metrics cannot be generated and reported to AOM. |
The log time must be in order. If the log time is out of order or times out, the log cannot be processed. Typical example: If the time of the host where the collector is located is not synchronized or log collection is severely delayed, the log time may not be in order, affecting the aggregation statistics for metrics generation. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot