-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
GNMI / Got empty metric-name for response / #14044
Comments
|
Hi @srebhan |
@jorisd please open a new issue if it's for a different metric/device. It would be also good to know the model and brand of the device if we need to enable some quirks to workaround stuff... |
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.28.1 / Cisco ASR 9922
Docker
No response
Steps to reproduce
Expected behavior
Telegraf doesn't create any error and we expect to get the desired data from the openconfig-interfaces.
Actual behavior
Telegraf display an error at startup, and we don't get the desired data from the openconfig-interfaces.
Moreover, we get lots of errors like this :
2023-10-03T09:08:09Z D! [outputs.file] Could not serialize metric: invalid name
2023-10-03T09:08:09Z D! [outputs.file] Could not serialize metric: invalid name
2023-10-03T09:08:09Z D! [outputs.file] Could not serialize metric: invalid name
2023-10-03T09:08:09Z D! [outputs.file] Could not serialize metric: invalid name
2023-10-03T09:08:09Z D! [outputs.file] Could not serialize metric: invalid name
2023-10-03T09:08:09Z D! [outputs.file] Could not serialize metric: invalid name
2023-10-03T09:08:09Z D! [outputs.file] Could not serialize metric: invalid name
Additional info
The workaround we use is define 2 inputs gnmi like this :
The text was updated successfully, but these errors were encountered: