-
Problem report
-
Resolution: Duplicate
-
Minor
-
None
-
3.0.10
I want to monitor NFS client statistics on Linux hosts. As NFSv3 and NFSv4 do not have the same counter values and I solved this using a LLD. The discovery result is like this:
{ "data": [
{ "{#NFS_VERSION}":"3"},
{ "{#NFS_VERSION}":"4"}
] }
So I have two discoveries for each version which filter like follows:
{#NFS_VERSION} matches ^3$
{#NFS_VERSION} matches ^4${noformat}
So each discovery will create items/triggers/graphs only for the corresponding NFS version. But actually this doesn't work for the graphs. On each discovery I get the following error:
graph with the same name "NFS Client v4" already exists
The graphs are named "NFS Client v3" respectively "NFS Client v4". As each discovery results in one instance there cannot be any duplicates.
If the graph ist named *NFS Client v\{#NFS_VERSION\}* the discovery works fine. But this cannot be changed on both graph prototypes because then I get another error:
Graph with name "NFS Client v
{#NFS_VERSION}" already exists in graphs or graph prototypes
So I think there is a bug within the discovery as I cannot result in duplicate graph names.
- duplicates
-
-
- Closed
-