Last updated:2020-12-28 14:55:42


LogPool is the minimum storage unit of KLog. KLog allows you to create LogPools and specify the number of partitions and the storage duration of log data for each LogPool. A LogPool can contain 2 to 64 partitions, and log data can be stored for 1 to 3,000 days. KLog also allows you to change the number of partitions in a LogPool based on the data traffic. KLog automatically deletes log data that expires. LogPools can store different types of data, including text, long, double, and date.

Create a LogPool

Log in to the KLog console and click Projects in the left navigation pane. The Projects page appears. Click the name of a project. The project details page appears. In the LogPool section, click Create LogPool.


  • Name: Enter a LogPool name in the specified format. The name cannot be changed after the LogPool is created.
  • Storage Duration: Enter a number that ranges from 1 to 3,000, in days. The storage duration can be changed after the LogPool is created.
  • Partitions: Enter a number that ranges from 2 to 64. The number of partitions can be changed after the LogPool is created. Click OK to create the LogPool.

Edit a LogPool

Find the LogPool that you want to edit and choose More > Edit in the Actions column. The LogPool panel appears, as shown in the following figure.


  • Storage Duration: After you change the storage duration, the change takes effect on the next day. For example, if you change the storage duration from 6 days to 2 days, the data that expires will not be immediately deleted. Instead, the expired data is deleted on the next day.
  • Partitions: After you change the number of partitions, the change immediately takes effect.

Delete a LogPool

After you delete a LogPool, all log data, associated charts, and alarm rules are also deleted and cannot be recovered. Exercise caution when you delete a LogPool.

Did you find the above information helpful?

Mostly Unhelpful
A little helpful
Very helpful

What might be the problems?

Unclear or awkward
Redundant or clumsy
Lack of context for the complex system or functionality

More suggestions


Please give us your feedback.


Thank you for your feedback.