-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request for NAS connections and iscsi sessions counts metric #3136
Comments
Discord discussion here |
Update the request which needs two values mapping to the values shown in HWU as the description. |
Could you share the time taken and the number of records returned by the following commands in the relevant environment you want to track? Make sure to replace
Thanks. |
Thanks @summertony15 . So, if we export NFS and iSCSI connection counts at the cluster level, will that be good? |
I think node level is better, since the limitation is by node. |
Sure Thanks. |
ISCSI seems to be at svm level. I don't see any node information in API |
@summertony15 Could you also run the commands shared in this comment on an ONTAP system with a large number of connections? The reason for this request is that we want to measure the time taken for these calls. |
@summertony15 We currently do not plan to enable these metrics in Harvest by default. I have provided a document detailing the steps to enable these metrics manually. Please follow the instructions outlined here and let us know if they work for you. Thank you! |
@rahulguptajss These works, |
From the CLI, in diagnostic mode, we can get the node count by using "iscsi session show -fields node" |
Yes, That is correct. |
Thanks. Yes, That is correct. |
@rahulguptajss So we cannot have the iscsi session count by node level? |
We cannot as the API |
Thanks. In that case, Could you try below iscsi template and check metric name: ISCSISessions
query: api/private/cli/iscsi/session
object: iscsi_sessions
counters:
- ^^tsih => tsih
- ^^tpgroup => target_portal_group
- ^^initiator-name => initiator
- ^^isid => isid
- ^^node => node
- ^^vserver => svm
plugins:
- LabelAgent:
value_to_num_regex:
- count initiator .* .* `0`
- Aggregator:
# plugin will create summary/average for each object
# any names after the object names will be treated as
# label names that will be added to instances
- svm
- node
# only export node/aggr aggregations from plugin
# set this true or comment, to get data for each lock
export_data: false |
Since these two templates are added under 9.12, do we need ONTAP version 9.12 or above to support these metrics? |
It doesn't matter, the template will be invoked regardless by lower ONTAP versions as well. For more information, please refer to this documentation. The |
If user is using ONTAP 9.11, will the template in rest/9.12 be taken ? |
Yes |
Describe the solution you'd like
NetApp has the limitation of Maximum number of connection -- NAS per node,
Here is the HWU example: https://hwu.netapp.com/Controller/Index?platformTypeId=30310846&platform=29266985&os=34942206#none
And here is the description: Maximum number of NAS (SMB and NFS) TCP connections that a node can support
Also, we have a maximum number of iSCSI sessions,
We want to monitor these two value, in case they reach the limits.
I need both of them, thanks
Best to have both ZAPI and REST templates.
The text was updated successfully, but these errors were encountered: