#create
1 messages · Page 1 of 1 (latest)
tested adding - create_time => create_time" to the volume template but create_time are all 0
Hi jfong5040, can you try adding the following to your conf/zapi/cdot/9.8.0/volume.yaml template and see if this returns what you want?
Here's an example:
curl -s 'http://localhost:12990/metrics' | sort | rg -v '^#' | rg volume_create
volume_create_time{aggr="umeng_aff300_aggr1",cluster="umeng-aff300-05-06",datacenter="dc-1",node="umeng-aff300-06",style="flexvol",svm="vs_test4",volume="vs_test4_root"} 1623672370
ONTAP says this counter returns Creation time of the volume in seconds since January 1, 1970. IOW epoch seconds
we are currently using the REST volume template. Should I disable REST and only use Zapi?
The REST template can be updated similarly. REST returns a string instead of epoch seconds, but we have a modifier to convert the string to epoch seconds so the metrics published by ZAPI and REST are consistent. Try this
Hello, I was thinking if there is any metric for measure the time it takes to create a volume? Thanks.
Hi @open egret we are not aware of a metric that includes time to create a volume. Someone on the #1063542514780475493 channel knows more?
As another option, depending on use-case and I'm not certain how this would be integrated into harvest, but reviewing the start and end timestamps of the volume creation job may be an option. Also, if this were an ONTAP performance metric, it'd probably exist at the aggregate (storage pool) level.