-
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
Got empty metric-name for response on Ciena WaveServer #15286
Comments
@mohsin106 can you please test the latest version (or even a nightly build)? I cannot reproduce the issue with current master... |
@mohsin106 please test the binary in #15297, available once CI finished the tests, and post the "new" warning here. I've improved the output a bit to see where exactly the issue is in the response... |
When setting the sensor path to
When I set the sensor path to '/components/component/" I'm no longer getting Telegraf warning or error messages. My Telegraf Config:
|
@mohsin106 please use single-quotes around the path and try again with |
I noticed that when I change
My config:
I believe that setting |
getting same error when using single ticks:
My Config:
|
Ok I fixed the path issue. I had to use |
@mohsin106 does your config work now? |
|
@mohsin106 well the prefix in the response is |
@srebhan from the vendor I have the option to select different origins so that I can receive different data sets.
|
When I subscribe to the
My Config:
|
@mohsin106 your data in the log is not complete so I cannot debug what is going on... |
The output is very long and I cannot post it here. Where can I save the
output so you can see it?
…On Wed, May 8, 2024 at 8:22 AM Sven Rebhan ***@***.***> wrote:
@mohsin106 <https://github.com/mohsin106> your data in the log is not
complete so I cannot debug what is going on...
—
Reply to this email directly, view it on GitHub
<#15286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAURPGQ6FBTNTCTGSPGQIHDZBIKH3AVCNFSM6AAAAABHFTHY4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBQGQ2TIOJSGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I just need the |
@srebhan attaching log file. |
@srebhan I'm doing some more testing. I have the
I'm running the nightly Telegraf build. I'm still getting the
Should |
@mohsin106 please do not mix issues in here, let's first find out why you get the initial empty message in #15286 (comment). Can you please post your subscription section related to the debug in #15286 (comment)? |
Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Forums or provide additional details in this issue and reqeust that it be re-opened. Thank you! |
Relevant telegraf.conf
Logs from Telegraf
System info
telegraf:1.29.3
Docker
No response
Steps to reproduce
Expected behavior
Have Telegraf handle this error:
Actual behavior
We see the error message from above. Other data does continue to process through Telegraf
Additional info
Similar issue to #12831
The text was updated successfully, but these errors were encountered: