need help troubleshooting aggregate check

Sensu Classic (EOL)
1

Hi all,
Last week I needed to give our main Sensu server (the one running redis, rabbit, api, dashboard) more virtual resources which required a reboot. When we came back up, sensu-api wouldn’t stay up due to a Redis error (known issue with 0.10) so I did a flushdb on redis in order to keep it up and running. Suddenly my aggregate endpoints were returning no data.

I’m unclear whether the reboot itself or the flushdb may have caused this, but either way, even after upgrading from 0.10 to 0.12, I still can’t get aggregates working.

Here is a gist showing the info I’ve collected so far: https://gist.github.com/skymob/7262599f0f1bd5cc8866

I can see the check being triggered and the results being published, but then can find no record of the results actually appearing on the server side. Perhaps my aggregate checks are just misconfigured?

thanks!

Bethany

···

–
Bethany Erskine

Senior Technical Operations Engineer

http://www.paperlesspost.com

2

I believe this is a simple but confusing fix: remove the trailing slash, i.e. curl http://localhost:4567/aggregates

If people think this is confusing, we could update the API to be a little less strict.

Looking at the headers can sometimes help, i.e.

[nick@sensu1 ~]$ curl -I http://localhost:4567/aggregates

HTTP/1.1 200 OK

Content-Type: application/json;charset=utf-8

Content-Length: 265

Connection: keep-alive

Server: thin 1.5.0 codename Knife

[nick@sensu1 ~]$ curl -I http://localhost:4567/aggregates/

HTTP/1.1 404 Not Found

Content-Type: text/html;charset=utf-8

X-Cascade: pass

Content-Length: 0

Connection: keep-alive

Server: thin 1.5.0 codename Knife

···

On Thursday, November 14, 2013 11:53:55 AM UTC-8, Bethany Erskine wrote:

Hi all,
Last week I needed to give our main Sensu server (the one running redis, rabbit, api, dashboard) more virtual resources which required a reboot. When we came back up, sensu-api wouldn’t stay up due to a Redis error (known issue with 0.10) so I did a flushdb on redis in order to keep it up and running. Suddenly my aggregate endpoints were returning no data.

I’m unclear whether the reboot itself or the flushdb may have caused this, but either way, even after upgrading from 0.10 to 0.12, I still can’t get aggregates working.

Here is a gist showing the info I’ve collected so far: https://gist.github.com/skymob/7262599f0f1bd5cc8866

I can see the check being triggered and the results being published, but then can find no record of the results actually appearing on the server side. Perhaps my aggregate checks are just misconfigured?

thanks!

Bethany

Bethany Erskine

Senior Technical Operations Engineer

http://www.paperlesspost.com

3

THANK YOU Nick, now I can see the aggregate results. Glad it was something simple but also… d’oh! :slight_smile:

···

On Fri, Nov 15, 2013 at 12:33 PM, Nick Stielau nick.stielau@gmail.com wrote:

I believe this is a simple but confusing fix: remove the trailing slash, i.e. curl http://localhost:4567/aggregates

If people think this is confusing, we could update the API to be a little less strict.

Looking at the headers can sometimes help, i.e.

[nick@sensu1 ~]$ curl -I http://localhost:4567/aggregates

HTTP/1.1 200 OK

Content-Type: application/json;charset=utf-8

Content-Length: 265

Connection: keep-alive

Server: thin 1.5.0 codename Knife

[nick@sensu1 ~]$ curl -I http://localhost:4567/aggregates/

HTTP/1.1 404 Not Found

Content-Type: text/html;charset=utf-8

X-Cascade: pass

Content-Length: 0

Connection: keep-alive

Server: thin 1.5.0 codename Knife

On Thursday, November 14, 2013 11:53:55 AM UTC-8, Bethany Erskine wrote:

Hi all,
Last week I needed to give our main Sensu server (the one running redis, rabbit, api, dashboard) more virtual resources which required a reboot. When we came back up, sensu-api wouldn’t stay up due to a Redis error (known issue with 0.10) so I did a flushdb on redis in order to keep it up and running. Suddenly my aggregate endpoints were returning no data.

I’m unclear whether the reboot itself or the flushdb may have caused this, but either way, even after upgrading from 0.10 to 0.12, I still can’t get aggregates working.

Here is a gist showing the info I’ve collected so far: https://gist.github.com/skymob/7262599f0f1bd5cc8866

I can see the check being triggered and the results being published, but then can find no record of the results actually appearing on the server side. Perhaps my aggregate checks are just misconfigured?

thanks!

Bethany

Bethany Erskine

Senior Technical Operations Engineer

http://www.paperlesspost.com

–
Bethany Erskine

Senior Technical Operations Engineer

http://www.paperlesspost.com

4

Chatting a bit on IRC, this seems like a pedantic REST issue, and not worth any confusion. I’ve made an issue for it, it should be a good fix to get into sensu-core if anyone has some time this weekend.

···

On Thursday, November 14, 2013 11:53:55 AM UTC-8, Bethany Erskine wrote:

Hi all,
Last week I needed to give our main Sensu server (the one running redis, rabbit, api, dashboard) more virtual resources which required a reboot. When we came back up, sensu-api wouldn’t stay up due to a Redis error (known issue with 0.10) so I did a flushdb on redis in order to keep it up and running. Suddenly my aggregate endpoints were returning no data.

I’m unclear whether the reboot itself or the flushdb may have caused this, but either way, even after upgrading from 0.10 to 0.12, I still can’t get aggregates working.

Here is a gist showing the info I’ve collected so far: https://gist.github.com/skymob/7262599f0f1bd5cc8866

I can see the check being triggered and the results being published, but then can find no record of the results actually appearing on the server side. Perhaps my aggregate checks are just misconfigured?

thanks!

Bethany

Bethany Erskine

Senior Technical Operations Engineer

http://www.paperlesspost.com