Open for Voting

Change the way (status) disabled components are displayed

Does this look misleading to you?  Upon further research, I realized this component was disabled.  Shouldn't the component status be a different color & the status be something other than UP?  I assume it would display whatever the status was at the time it was disabled.

Background:  I ran into this when testing an alert.  It triggered because the 'last time up' date was in the past.  When I clicked on the URL for the component I saw this, which concerned me.  Upon further investigation, I realized I forgot to check the disabled flag.

4-25-2013 4-29-06 PM.bmp

  • No points I'm afraid, but I am offering a hearty pat on the back and "Atta boy" for finding a very obscure bug. emoticons_happy.png

  • Thank you for looking into this so quickly.  emoticons_laugh.png  How many points do I get for finding a bug? lol

  • , after some investigation it would appear as though you've stumbled upon a bug. When a component is disabled in the template you should no longer be able to access the component details view through the webUI, though it will still exists in the database when performing a SQL query like the one you posted above. If you disable this component in the assigned application the component monitor detail page for that component should disappear from view in the webUI. That's the temporary workaround for now. We've logged this bug internally under FB239182.

  • Nope.  I don't think so.  I'm excluding 'Unmanaged' in the query.  It showed up via an custom SQL alert I took from thwart.  (I converted the sql code for a report in thwart into an alert.)

    5-1-2013 11-08-17 AM.bmp

    Here's the code if you want to try it:  Be sure to comment out the disabled condition ("-- AND ace.Disabled = 0").  Then disable a component.  When you get the alert, click on the URL in the message and you'll see the disabled component with an UP status.

     

    LEFT JOIN Nodes n on n.NodeId = APM_AlertsAndReportsData.NodeId

    where

    ( NOT (UPPER(n.Status) in ('2', '9', '11' )) -- 2=Down, 9 = Unmanaged & 11=External

    )

    AND

    ComponentID in(

    SELECT top 1 ard.ComponentID

    FROM APM_AlertsAndReportsData ard

    LEFT JOIN APM_ComponentExt ace on ard.ApplicationID = ace.ApplicationID and

    ard.ComponentID = ace.ID

    WHERE DateDiff(Minute, TimeStamp, GetDate()) > 15 AND

    ComponentStatus <> 'Unknown' AND

    ComponentStatus <> 'Unmanaged'

    AND ace.Disabled = 0

    ORDER BY Timestamp DESC

    )

    The trigger message needs to include the URL.  Here is mine:

    Alert: ${AlertName}
    Next_Poll: ${TimeStamp} <<Should be within the past 15 minutes.
    Application: ${ApplicationName}
    Component: ${ComponentName}
    URL:  ${APM:ComponentDetailsURL}
    Node: ${NodeName}
    Status: ${Status}${StatusOrErrorDescription}

    Triggered: ${AlertTriggerTime}

    p.s Alert name is:  Application Polling issue - stopped for App (>15 min)

  • If the component has been "disabled" in the application then it shouldn't appear at all in any context until/unless it's reenabled either in the application template, or the assigned application. Is it possible you're seeing this when the application is unmanaged, not disabled?