Relevant telegraf.conf:
System info:
CentOS 7
Telegraf 1.17.2 but verified problem exists in Master
vSphere 7.0.2.00100
Steps to reproduce:
- Configure vSphere daily statistics interval to be anything other than default 5m
- Configure telegraf to query all statistics from the vSphere you just modified config on
- Start telegraf
Expected behavior:
Operate as normal pulling all statistics
Actual behavior:
For all historical statistics this error is thrown in the logs and no statistics are recorded.
2021-05-06T17:41:50Z D! [inputs.vsphere] Find(Datastore, /*/datastore/**) returned 17 objects
2021-05-06T17:41:50Z E! [inputs.vsphere] Getting metric metadata. Discovery will be incomplete. Error: ServerFaultCode: A specified parameter was not correct: interval
2021-05-06T17:41:50Z D! [inputs.vsphere] Found 0 metrics for xxxxxxx
Additional info:
Plan to add a config option for "HistoricalInterval" which defaults to 300 but can be overridden so that it matches the daily interval configured in vSphere. This will replace the currently hard coded value of 300.
Relevant telegraf.conf:
System info:
CentOS 7
Telegraf 1.17.2 but verified problem exists in Master
vSphere 7.0.2.00100
Steps to reproduce:
Expected behavior:
Operate as normal pulling all statistics
Actual behavior:
For all historical statistics this error is thrown in the logs and no statistics are recorded.
2021-05-06T17:41:50Z D! [inputs.vsphere] Find(Datastore, /*/datastore/**) returned 17 objects
2021-05-06T17:41:50Z E! [inputs.vsphere] Getting metric metadata. Discovery will be incomplete. Error: ServerFaultCode: A specified parameter was not correct: interval
2021-05-06T17:41:50Z D! [inputs.vsphere] Found 0 metrics for xxxxxxx
Additional info:
Plan to add a config option for "HistoricalInterval" which defaults to 300 but can be overridden so that it matches the daily interval configured in vSphere. This will replace the currently hard coded value of 300.