Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Surveillance view shows nodes in red when no services are down

Description

If you add nodes via Admin/Add interface which are behind a firewall, they exist in a state where they have no services attached to the node. If you subsequently classify them so that they appear on a surveillance view, then that section appears in red and they are on the page that appears when clinking the link in that section.
I presume the code shows them in red because the number of running services is zero rather than the fact that all services have failed. This case should not be flagged as a node requiring attention.

Environment

Operating System: Solaris Platform: Sun

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Ronny Trommer March 23, 2016 at 1:18 PM

Solved with please reopen if this issue still exist on the Vaadin based surveillance view.

Ondrej D. June 22, 2012 at 4:01 PM

We also have provisioned nodes with no managed services and have the same issue in surveillance view:

VMware ESXi servers, which are managed by vCenter DPM (Distributed Power Management). It dynamically powers on/off servers based on resources needed. So we added those servers with no managed services since we don't want hundreds of false positive alarms (server down), but we need to receive traps from them.

Antonio Russo May 18, 2012 at 2:02 AM

Consider a Service provider with lot of nodes. And consider that this service provider has a lot of wave points in
the mountains where there are a lot locations that are opened only during the summer.

Do you think you have to provide the nodes every summer? Or you prefere to provide the nodes once with the proper
categories (survelliance) then when the node is down no impact on services and no monitors. When the node comes up then the rescan will found the required services and it is monitored as it is rescanned.

Tarus Balog May 17, 2012 at 4:56 PM

We have a support customer with this issue. Not sure why they have provisioned a node with no managed services, but it results in a red cell with something like "0 of 32" as the text. Just be curious as to the effort to address this. The workaround, of course, would be to remove the zero service node from the category.

Benjamin Reed March 13, 2008 at 2:22 PM

maybe we should use the blue "indeterminate" color for cases where there's 0?

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created February 14, 2008 at 10:39 AM
Updated February 14, 2018 at 8:00 PM
Resolved March 23, 2016 at 1:18 PM