telegraf: gNMI for Ciena SAOS 10.x devices fails path string validation

Relevant telegraf.conf

[[inputs.gnmi.subscription]]
     name = "ifcounters"
     origin = "openconfig-interfaces"
     path = "/oc-if:interfaces/oc-if:interface[name=7]/oc-if:state/oc-if:counters"
     subscription_mode = "sample"
     sample_interval = "10s"

Logs from Telegraf

[telegraf] Error running agent: starting input inputs.gnmi: invalid string path /o-if:interfaces/oc-if:interface[name=7]/oc-if:state/oc-if:counters: invalid node name: "o-if:interfaces"

System info

Telegraf 1.22.0+, Debian 11 (bullseye), Docker 20.10.5

Docker

telegraf: image: telegraf container_name: telegraf restart: always volumes: - /opt/TIGstack/telegraf/etc:/etc/telegraf:rw - /opt/TIGstack/telegraf.conf:/etc/telegraf/telegraf.conf:rw - /opt/TIGstack/var/lib/mibs/ietf:/var/lib/mibs:rw - /opt/TIGstack/var/lib/mibs/ietf:/usr/share/snmp/mibs:rw - /opt/TIGstack/telegraf/etc/ca.cert.pem:/etc/telegraf/ca.cert.pem - /opt/TIGstack/telegraf/etc/client.cert.pem:/etc/telegraf/client.cert.pem - /opt/TIGstack/telegraf/etc/client.key.pem:/etc/telegraf/client.key.pem depends_on: - influxdb links: - influxdb ports: - ‘8125:8125’

Steps to reproduce

1. Using telegraf v1.22 and up

Expected behavior

Successful gNMI subscription consistent with version 1.21 and lower

Actual behavior

Telegraf fails with “invalid string path” error and exits

Additional info

No response