-
Notifications
You must be signed in to change notification settings - Fork 178
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
sensuctl event list tabular display bug #2099
Comments
Oh this is a fun one! Okay, I'm able to reproduce the issue! Yes, it has to do with the check output containing the return and newline characters:
So, we could render the check output last, which solves the immediate formatting problem. However, our resources that contain timestamps typically display those as the last column.
@annaplotkin I would love some product feedback on a direction here. I see a few different solutions.
|
Related: #3667 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Found a bug doing my Yolo demo.
Check the attached screenshot for config details.
Gut tells me its something specific with my podman based check command output.
It looks like the output parsing is all garbled..maybe due to line return characters at the end of the output?
sensuctl event info frodo_baggins docs.sensu.io looks okay though
sensuctl event list --format=json also looks fine.
see attached output of sensuctl event list --format=json
event_list.txt
Expected Behavior
docs.sensu.io and docs_sensu_io checks should display correctly in event list tabular view
Current Behavior
output for these checks are garbled.
Possible Solution
Steps to Reproduce (for bugs)
Not sure how to reproduce generally.. i've only seen this with my podman based check command.
Do we have a documented way for me to inject a check result via cmdline?
Context
Your Environment
rpm package sensu-backend-2.0.0~nightly+20180920-1.x86_64
Fedora
The text was updated successfully, but these errors were encountered: