Statistics

t he statistics module primarily shows you how belden horizon data 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 disk usage includes user data in gb, the percentage of user data usage, the archive data in gb, the percentage of archive data usage disk usage by data object includes a 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, and a list of objects showing the data objects' size, usage in percentage format, and path you can copy the path of a listed data object 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 by company and project organized by month you can filter the list, and archive or purge a selected data item from the list access statistics ui to access the statistics ui log in to the belden horizon data manager (bhdm) admin console at the following url https //\[bhdm ip address] 8446 from the navigation panel, select data lifecycle data lifecycle's statistics pane by default appears base dir contains all system data and logs the path location is / data dir contains user generated data such as backup data, archived data, update files, and docker images the path location is /var/lib/lem user data (subset of data dir ) contains data sent from belden horizon data operations instances archive data (subset of data dir ) contains data on generated archives (exported csv gz files) refer to the following actions you can take on the belden horizon data manager admin console data lifecycle's statistics pane \[1] view data object disk usage \[2] copy path to clipboard lem upgrade storage of bhdm upgrade files see docid\ f ptrgkf4xjpwipcqu1at minio storage storage of bhdo backup files, archived files and templates prometheus data storage of metrics data see docid 3k wsi2hscdg3vxc2ecvj mpcs docker registry storage of bhdm docker registry files see docid\ b4ra3q4ngdv9p czowku9 and docid ttuqf1alf6fcf1f3w gf clickhouse data storage of clickhouse db see docid\ zzhefwbfwq34losnuy8ld this is data related to connected belden horizon data operations instances this data is shown in more in details in stats by periods kafka data data used by kafka service see docid\ m1crq jhx6iijqbfxqrud for details dlm archive where arc hived data is stored see docid 56kjij6w iq2cstdazv2e for details 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 \[3] show filter / hide filter search by company , or project \[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 56kjij6w iq2cstdazv2e 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 belden horizon 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 belden horizon data manager purging data cannot be undone period explained belden horizon data manager keeps track of disk usage in partitions of months the tracked disk usage is only for clickhouse data (hence all archive/purge operations is applicable for only clickhouse data) 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 belden horizon data manager has five projects to calculate disk usage, each project will be categorized as one period for the same month so belden horizon data 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