Closed whizkidTRW closed 1 year ago
FWIW, here's what the interfaces "sensor" looks like in the Ciena SAOS 10.8 UI, along with the existing subscription (that is currently working" to our production Telegraf 1.26.1 instance:
+-------+---------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 11 | Sensor Path Name | /oc-if:interfaces/oc-if:interface/oc-if:state/oc-if:counters |
| | Sensor Sub Mode | sample |
| | Sensor ID | 3071242026345933326 |
+-------+---------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+-------+---------------------------------+----------------------------------------------------------------------------------------------------------+
| 2 | Subscription: | |
| | Subscription-ID | bc8795b3-b373-4c34-b9c3-234b73a33153 |
| | Subscription State | |
| | User Name | XXXXXXXXXXXXXXXX |
| | Subscription Mode | stream |
| | Update Only | True |
| | Sample Interval | 30000000000 |
| | Subscription Message | |
| | Telemetry Sensor Paths | |
| | Telemetry Sensor Path | /oc-if:interfaces/oc-if:interface/oc-if:state/oc-if:counters |
| | Telemetry Sensor ID | 6958060735294400085 |
| | Telemetry Sensor Sub-Mode | sample |
| | Telemetry Sensor Svc-Mode | sample |
+-------+---------------------------------+----------------------------------------------------------------------------------------------------------+
@whizkidTRW can you please test the binary in PR #14091 and let me know if that fixes your issue!?
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.28.2, Debian 11, Docker 20.10.5
Docker
No response
Steps to reproduce
...
Expected behavior
It was working fine under 1.26.2 once this message was made a warning (instead of an error). But, now anything newer than 1.26.2 fails.
Actual behavior
The data just isn't output, presumable because it isn't parseable. Removing the origin parameter in the config yields the erorr message but still no data output.
Additional info
I've opened a previous issue on this and it was fixed in 1.25 but now it's broken again . . .