Skip to content
This repository has been archived by the owner on Jan 7, 2020. It is now read-only.

Uchiwa not showing "Output" when check status is green (status 0) #404

Closed
samroy92 opened this issue Oct 29, 2015 · 8 comments
Closed

Uchiwa not showing "Output" when check status is green (status 0) #404

samroy92 opened this issue Oct 29, 2015 · 8 comments
Assignees
Labels
Milestone

Comments

@samroy92
Copy link

On the page /client/home/(servername) it shows a list of all the checks for that client. When an event is triggered it shows the output on this page's check. But when the status of the check is green, it does not show the output (probably by design). I would love to see the regular Output even when the checks are green. For example, if you have a check for memory use, it will say: "Memory use OK, 50% used". How can I pipe the output from the actual check page into this overall client "checks" page.

This is the page I am referring to:
http://thepracticalsysadmin.com/wp-content/uploads/2014/08/uchiwa41.jpg

@jbehrends
Copy link

Uchiwa will do this if your using a newer version of Sensu. From your screenshot it looks like your using v0.13.1 and I believe the ability to read the output for a check in an OK state was introduced in Sensu v0.18. So upgrade your Sensu install and you'll get what your looking for.

@samroy92
Copy link
Author

Thanks for the fast reply, this is not my screenshot - I just pulled it from a website. My sensu version is: v0.20.6 and my uchiwa version is v0.12.0. So should I downgrade my sensu to restore this functionality? Thanks!

@jbehrends
Copy link

Have you verified that both Sensu Server and Sensu Client are v0.20.6?
It sounds like you have versions of both Sensu and Uchiwa that should show you check results. I would start by reviewing the output of your Sensu server's "results" API for a specific client and see what's returned. Do you see the results output when you hit /results/ ?
https://sensuapp.org/docs/0.20/api-results
Ultimately if the data isn't being returned by the API, then you won't see it in Uchiwa.

@samroy92
Copy link
Author

Yeah I see all the outputs when I view /results/ . Also all of my sensu-client versions are on 0.20.6 as well. I've tried flushing redis also. Here is a screen shot of my actual setup:
http://i.imgur.com/37OdFTk.png
http://i.imgur.com/atnKPMl.png

When I drill into the check it shows me all information.

Thanks again for the help.

@samroy92
Copy link
Author

Edit: Scratch all that, I narrowed down the problem to uchiwa-web (/opt/uchiwa/src/public/bower_components/uchiwa-web). Something was committed that broke the output field in the client checks page. I am investigating what it might be.

I think I may have narrowed it down to my CentOS version as strange as it sounds. I did a clean install on CentOS 7.1 and it has the same issue. I did an upgrade of uchiwa from 11.2 to 12.0 on CentOS 6.7 and there is no issue. Is there anyone else running sensu+uchiwa on centos 7 that is having issues?

@samroy92
Copy link
Author

I found this in the uchiwa-web/partials/view/client.html
http://i.imgur.com/VFkvyPl.png

I believe this { check.output } is not returning any data. Maybe its a permissions issue? I don't know. I definitely need some help after this point - I don't know where to look next.

Edit: I have a working sensu+uchiwa build on latest versions that DOES output data for { check.output }. The build I am trying to fix does not output data. Note: everything else is working fine.

Thanks

@samroy92
Copy link
Author

Edit: I solved this issue by downgrading to 0.11.2, this problem is caused by 0.12.0

I couldn't find anything on this, any help is appreciated. Maybe there is a dependency i'm missing?

@palourde palourde added this to the 0.12.1 milestone Nov 4, 2015
@palourde palourde self-assigned this Nov 4, 2015
@palourde
Copy link
Contributor

palourde commented Nov 4, 2015

@pwn777 You are totally right, I completely missed it, sorry about that!

@palourde palourde closed this as completed Nov 4, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants