I see that DMC is unable to give the right volume usage for a particular partition in the servers. It is showing the wrong partition value in every instance for that particular partition name.
Is there any specific permission that needs to be checked or how can this be fixed ?
| rest splunk_server_group=dmc_group_* /services/server/status/partitions-space
The above query results in false values than that of
df -h in the server
| rest splunk_server_group=dmc_group_* /services/server/status/partitions-space provide values in MB, if you run
df -BM the values are similar. If you want to convert those values to GB then you can use below query.
| rest splunk_server_group=dmc_group_* /services/server/status/partitions-space | eval available=round(available/1024,2), capacity=round(capacity/1024,2), free=round(free/1024,2)
I hope this helps.
Hi @harsmarvania57 ,
The DMC alert for the CRITICAL Disk usage uses the same query and calculation,
| rest splunk_server_group=dmc_group_* /services/server/status/partitions-space | eval free = if(isnotnull(available), available, free) | eval usage = capacity - free | eval pct_usage = floor(usage / capacity * 100) | where pct_usage > 80 | stats first(fs_type) as fs_type first(capacity) AS capacity first(usage) AS usage first(pct_usage) AS pct_usage by splunk_server, mount_point | eval usage = round(usage / 1024, 2) | eval capacity = round(capacity / 1024, 2) | rename splunk_server AS Instance mount_point as "Mount Point", fs_type as "File System Type", usage as "Usage (GB)", capacity as "Capacity (GB)", pct_usage as "Usage (%)"
I see almost a terabyte of difference in the values and even if the backend space in the partition gets changed, the query isn't showing the updated values.