AWS CloudWatch metrics, diskStorage Capacity not seen

[amolari]

Environment

• Telemetry Streaming Version: 1.18
• BIG-IP Version: 14.1.3.1

Summary

In AWS CloudWatch, the metric F5_system_diskStorage_Capacity is not visible (but F5_system_diskStorage_1024-blocks is).

Steps To Reproduce

Expected Behavior

We can see the metric F5_system_diskStorage_Capacity, as it's configured in the properties.json:

f5-telemetry-streaming/src/lib/properties.json

Lines 226 to 234 in 52fadd4

	"diskStorage": {
	"structure": { "parentKey": "system" },
	"key": "diskStorage::commandResult",
	"normalization": [
	{
	"runFunctions": [{ "name": "formatAsJson", "args": { "type": "csv", "mapKey": "Mounted", "filterKeys": { "include": [ "/", "Capacity", "1024-blocks" ] } } }]
	}
	]
	},

Note: wouldn't it make sense to get metrics only for non tempfs/devtempfs devices? Replacing the command

f5-telemetry-streaming/src/lib/paths.json

Line 149 in 52fadd4

"utilCmdArgs": "-c \"/bin/df -P | /usr/bin/tr -s ' ' ','\""

with
/bin/df -P -x tmpfs -x devtmpfs | /usr/bin/tr -s ' ' ','

Actual Behavior

In AWS CloudWatch, only the metrics F5_system_diskStorage_1024-blocks are visible.

[amolari]

It seems to be an issue on the AWS CloudWatch consumer side: with the Generic_HTTP consumer I can see the metric.

[dstokesf5]

I believe this is occurring because most metrics only TS consumers filter out non-metrics data. In this case, the percent character in the capacity field is likely preventing it from being used. I have filed this bug in our internal product backlog as AUTOTOOL-2311.

[amolari]

@dstokesf5 You are right, if I change the path.json to be
"utilCmdArgs": "-c \"/bin/df -P -xdevtmpfs -xtmpfs | /usr/bin/tr -s ' ' ',' | /usr/bin/tr -d '%'\""
it works.
Would you agree to change it that way (including exclusion of devtmpfs and tmpfs)?

[dstokesf5]

This issue was resolved as part of the 1.20.0 release.