Spotty Uchiwa behavior when silencing clients/checks

Sensu Classic (EOL)
1

Running Uchiwa 0.18.1 with Sensu 0.26.3
Production setup has just under 1,000 clients

Seeing a lot of spotty behavior with Uchiwa when nodes are silenced, as under:

Scenario-1

  1. Silenced all events (~9) for a client
  2. The “Silenced” page shows all expected entries for the events silenced
  3. The “Clients” page for that specific client shows the specific checks as silenced, as expected
  4. The “Events” page shows the silenced icon only against some events (i.e. icon near the checks). It takes several minutes for the silenced icon to show against all. It appears the icon typically changes when the check is next run on that client

Scenario-2

  1. Silenced a client via the “Clients” page
  2. Events for that client no longer appear on the “Events” page

The above behavior is not consistently seen but often enough for us to worry that what we are looking in Uchiwa at is not accurate. Anyone else seeing this behavior?

2

Hi Alex,

Regarding the scenario 1, this is caused by an expected behaviour in Sensu API but undesirable in Uchiwa. I just opened an issue about it: Validate silence & silenced_by attributes in Sensu events · Issue #602 · sensu/uchiwa · GitHub

About the second scenario, you should make sure you have nothing checked within the Hide dropdown in the events view; it looks like the Silenced Clients is currently active in your case.

Thanks,

Simon

···

On Friday, November 18, 2016 at 4:58:03 PM UTC-5, Alex Rodrigues wrote:

Running Uchiwa 0.18.1 with Sensu 0.26.3
Production setup has just under 1,000 clients

Seeing a lot of spotty behavior with Uchiwa when nodes are silenced, as under:

Scenario-1

  1. Silenced all events (~9) for a client
  2. The “Silenced” page shows all expected entries for the events silenced
  3. The “Clients” page for that specific client shows the specific checks as silenced, as expected
  4. The “Events” page shows the silenced icon only against some events (i.e. icon near the checks). It takes several minutes for the silenced icon to show against all. It appears the icon typically changes when the check is next run on that client

Scenario-2

  1. Silenced a client via the “Clients” page
  2. Events for that client no longer appear on the “Events” page

The above behavior is not consistently seen but often enough for us to worry that what we are looking in Uchiwa at is not accurate. Anyone else seeing this behavior?

3

Hi Simon,

Thanks for opening the issue for Scenario 1.

As for Scenario 2, I did not notice the “Hide” option till now which may quite possibly be the reason, but will keep an eye on it going forward. It is not obvious when the “Hide” filter is enabled, so I might raise a feature request for that

Alex

···

On Monday, November 21, 2016 at 5:57:52 PM UTC-5, Simon Plourde wrote:

Hi Alex,

Regarding the scenario 1, this is caused by an expected behaviour in Sensu API but undesirable in Uchiwa. I just opened an issue about it: https://github.com/sensu/uchiwa/issues/602

About the second scenario, you should make sure you have nothing checked within the Hide dropdown in the events view; it looks like the Silenced Clients is currently active in your case.

Thanks,

Simon

On Friday, November 18, 2016 at 4:58:03 PM UTC-5, Alex Rodrigues wrote:

Running Uchiwa 0.18.1 with Sensu 0.26.3
Production setup has just under 1,000 clients

Seeing a lot of spotty behavior with Uchiwa when nodes are silenced, as under:

Scenario-1

  1. Silenced all events (~9) for a client
  2. The “Silenced” page shows all expected entries for the events silenced
  3. The “Clients” page for that specific client shows the specific checks as silenced, as expected
  4. The “Events” page shows the silenced icon only against some events (i.e. icon near the checks). It takes several minutes for the silenced icon to show against all. It appears the icon typically changes when the check is next run on that client

Scenario-2

  1. Silenced a client via the “Clients” page
  2. Events for that client no longer appear on the “Events” page

The above behavior is not consistently seen but often enough for us to worry that what we are looking in Uchiwa at is not accurate. Anyone else seeing this behavior?