Statistics

the statistics module primarily shows you how litmus edge manager uses disk space it allows you to view user/archive data, view disk usage by period, view disk usage by projects, and archive or purge data from this sub module the statistics module includes the following sections primary partitions usage this section visualizes the current usage of primary partitions, including the total user data in gb, the percentage of user data used, and the percentage of free data space in gb all partitions this section displays all instance partitions along with their current usage, including the total user data in gb, the percentage of user data used, and the percentage of free data space in gb you can copy the path of a listed data object disk usage by data object includes a pie chart with data objects depicted where you can hover over sections of the chart to view the disk usage for each data object in gb data objects a list of data objects showing the data objects' size, usage in percentage format, and path along with object name data cumulative chart shows the periods amount of disk usage for each month in bar chart format top 10 projects chart shows the cumulative amount of disk usage for each project (up to 10 projects) in bar chart format stats by periods includes a data list grouped by company and project organized by month you can filter the list, and archive or purge a selected data item from the list stats by projects includes a data list grouped by projects you can only display the list and search/sort selected data items from the list access statistics ui to access the statistics ui log in to the litmus edge manager (lem) admin console at the following url https //\[lem ip address] 8446 from the navigation panel, select data lifecycle data lifecycle's statistics pane by default appears refer to the following actions you can take on the litmus edge manager admin console data lifecycle's statistics pane action details \[1] view data object disk usage docid\ gqogt szm8rz9udphl2nl \[2] data objects table lem upgrade storage of lem upgrade files see docid c0cof hliwthd8s3u2zp minio storage storage of le backup files, archived files and templates prometheus data storage of metrics data see docid\ xz4okukesfg7rdekrlhpu mpcs docker registry storage of lem docker registry files see docid\ fnot3p4u58 kh423wre8k and docid\ h5xzoqnak6ppcszhzi0g clickhouse data storage of clickhouse db see docid\ md6nfaz8rrs1p jwpaim this is data related to connected litmus edge instances this data is shown in more in details in stats by periods mysql data storage of mysql database kafka data data used by kafka service see docid\ m3iovmstpulhmjpupnllr for details dlm archive where archived data is stored see docid\ dsjzj4n3ksgiqliabm gy for details \[3] show filter / hide filter search by company , or project disk usage statistics by period include company the company name where the disk usage resides project the project name where the disk usage resides period the month the disk usage occurred disk space usage is partitioned in periods periods will always be one month see below for more details size the amount of disk usage for the selected period in kb action the menu that includes the ability to archive and purge and selected data \[4] action menu archive data when data is archived, the data is extracted from the clickhouse database server and stored as a csv gz file these files can be downloaded from docid\ dsjzj4n3ksgiqliabm gy note each csv gz file is up to ten times the size of the data size (the data size that is shown in stats by periods section is actually a compressed size) before you archive, ensure the litmus edge manager has enough disk space to contain all the csv gz files that it will archive insufficient disk space will prevent the data from being archived after archiving, review the list of archive files to ensure the archive operation was successful purge this will delete the data from the litmus edge manager purging data cannot be undone period explained litmus edge manager keeps track of disk usage in partitions of months the tracked disk usage is only for clickhouse data (hence all archive/purge operations are applicable for clickhouse data only) the disk usage amount is calculated either from the instance or each individual project each month of disk usage is defined as a period for example, your litmus edge manager has five projects to calculate disk usage, each project will be categorized as one period for the same month so litmus edge manager will generate five periods for the same month, each period including one project as an additional example, three months have passed for the five projects above, each of them experienced some disk usage in those three months so you will have 15 additional periods (five projects of disk usage 3 months) periods are also categorized as previous or current if the current system date is march 2023, then all disk usage by projects during march 2023 are current periods all periods from february 2023 and before are previous periods