Miss Matching alerts between client prognosis server and management server

Highlighted
10 Guide

Miss Matching alerts between client prognosis server and management server

Hi All,

 

Any one can answer this question ASAP. We are intergated client prognosis server to our managment server. we see some alerts in managment server. However we are unable to found those alerts in our actual client prognosis server. Can anyone help me on this how can we remove this alerts in prognosis managment server.

 

 

Thanks,

Venkatesh

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Miss Matching alerts between client prognosis server and management server

Hi Venkatesh, you questions is not clear on what you are trying to accomplish or are specifically experiencing with no example or screenshot.  Part of it may be mixed use of terminology so I will first define standard terminology and then answer based on a best guess of what you are talking about.  If it is not please clarify using standard terminology.

 

I understand you have a Monitoring Node (the system being monitored) attached to a top level Managing Node (the server which hosts the WebUI and all Monitoring Nodes attach too, sometimes there are multiple tiers of these).  With the Prognosis IRGUI Windows Client (Desktop windows client )  you can connect to either the Managing Node or the Monitoring Node and is usually installed on desktop workstations and on each Prognosis node and the WebUI (is a user interface extension of a the Managing Node) that can see "All Nodes" views and downstream 'managed' entities of the Managing Node. 

 

The relationship and visibility of Managing Node and Monitoring nodes is establised via MANAGED-NODE and MANAGING-NODE statements in the NETWORK configuraiton. This can make it a bit confusing as a Monitoring node of a upper tier MANAGING NODE could also be playing the role of a lower tier Monitoring Node. In Payment PCI deployment architecture this is common. 

image.png

 

The Managing node will see see all of these downstream entities in its "Entire Network"  view but a individual display like Alert Central will display Alerts for how the display is configured.  There are multiple iterations of the Alerts Central Display and at a high level there is "All Nodes" (which will display all monitoring nodes AS WELL as the Managing Node generated Alerts) version (See Screenshot below in Option 1). The default one in the WebUI is the All Nodes version unless a specific node is drilled down onto... so you will see Alerts for Monitoring and Managing Nodes within that display. 

 

The alert itself when you click on it will show you witch alert the node was generated on.

 

If you want to just see alerts for a single Monitor node, your options are:

1) In the WebUI or IRGUI Go to the main Alert Central, then click on the Node Name you want to see the filtered name for.. 

2) In the WebUI:  Go to the main Alert Central, then click on the Node Name and it should show you just alerts from it.  Copy the URL from this Display and Add it as a Key Display so it can be directly accessed. 

image.png

3) In the Client Create Hard Coded Custom Copy of the Alert Display showing only specific nodes and removing the Managing Node. 

     A) Go to Knowledge->Common->Alerts->Alerts by Node and make a copy of it to "My Displays & Configurations".

    image.png

     B) Then Open it, Drag the specific Monitoring Node or Node Group (a logical definition of a group of Monitoring Nodes) to it, and then save it OR enter every single windows properties and change it manually to reflect the node you want to see alerts for.. it is also a way of verifying it.  It would say a specific node or Node Group here vs. #DefaultNode or #EntireNetwork that would explicitly excluding the Managing Node. 

image.png

     C) Then rename it to that node name.

     D) Publish it to the Web.

     E) Add it as a Key Display. 

 

If you are only wanting to view a single server, then the first two option makes the most sense since you can very quickly do it.  If you want to see a group of Monitoring Nodes (more than one) it makes sense to use a logical Node Group and then have the Alert Central display the content of those Monitoring Nodes only. 

 

Note: You cannot easily change the link for clicking on the "Alerts" menu on the WebUI. 

 

If this doesn't address your question, please clarify your question and provide some specific details / illustrations please using standard terminology for us to be able to further assist.  We are quite happy to see your active engagement in the community but sounds like you could use a bit of administrative training to solidify your base knowledge of Prognosis. 

 

Thanks.

Christopher

 


If my answer helped you today, please be sure to mark the resolved button to assist others.

Christopher R Souser - Solution Architect – MSci. PA, CISSP, ITIL.

View solution in original post

1 REPLY 1
Highlighted

Re: Miss Matching alerts between client prognosis server and management server

Hi Venkatesh, you questions is not clear on what you are trying to accomplish or are specifically experiencing with no example or screenshot.  Part of it may be mixed use of terminology so I will first define standard terminology and then answer based on a best guess of what you are talking about.  If it is not please clarify using standard terminology.

 

I understand you have a Monitoring Node (the system being monitored) attached to a top level Managing Node (the server which hosts the WebUI and all Monitoring Nodes attach too, sometimes there are multiple tiers of these).  With the Prognosis IRGUI Windows Client (Desktop windows client )  you can connect to either the Managing Node or the Monitoring Node and is usually installed on desktop workstations and on each Prognosis node and the WebUI (is a user interface extension of a the Managing Node) that can see "All Nodes" views and downstream 'managed' entities of the Managing Node. 

 

The relationship and visibility of Managing Node and Monitoring nodes is establised via MANAGED-NODE and MANAGING-NODE statements in the NETWORK configuraiton. This can make it a bit confusing as a Monitoring node of a upper tier MANAGING NODE could also be playing the role of a lower tier Monitoring Node. In Payment PCI deployment architecture this is common. 

image.png

 

The Managing node will see see all of these downstream entities in its "Entire Network"  view but a individual display like Alert Central will display Alerts for how the display is configured.  There are multiple iterations of the Alerts Central Display and at a high level there is "All Nodes" (which will display all monitoring nodes AS WELL as the Managing Node generated Alerts) version (See Screenshot below in Option 1). The default one in the WebUI is the All Nodes version unless a specific node is drilled down onto... so you will see Alerts for Monitoring and Managing Nodes within that display. 

 

The alert itself when you click on it will show you witch alert the node was generated on.

 

If you want to just see alerts for a single Monitor node, your options are:

1) In the WebUI or IRGUI Go to the main Alert Central, then click on the Node Name you want to see the filtered name for.. 

2) In the WebUI:  Go to the main Alert Central, then click on the Node Name and it should show you just alerts from it.  Copy the URL from this Display and Add it as a Key Display so it can be directly accessed. 

image.png

3) In the Client Create Hard Coded Custom Copy of the Alert Display showing only specific nodes and removing the Managing Node. 

     A) Go to Knowledge->Common->Alerts->Alerts by Node and make a copy of it to "My Displays & Configurations".

    image.png

     B) Then Open it, Drag the specific Monitoring Node or Node Group (a logical definition of a group of Monitoring Nodes) to it, and then save it OR enter every single windows properties and change it manually to reflect the node you want to see alerts for.. it is also a way of verifying it.  It would say a specific node or Node Group here vs. #DefaultNode or #EntireNetwork that would explicitly excluding the Managing Node. 

image.png

     C) Then rename it to that node name.

     D) Publish it to the Web.

     E) Add it as a Key Display. 

 

If you are only wanting to view a single server, then the first two option makes the most sense since you can very quickly do it.  If you want to see a group of Monitoring Nodes (more than one) it makes sense to use a logical Node Group and then have the Alert Central display the content of those Monitoring Nodes only. 

 

Note: You cannot easily change the link for clicking on the "Alerts" menu on the WebUI. 

 

If this doesn't address your question, please clarify your question and provide some specific details / illustrations please using standard terminology for us to be able to further assist.  We are quite happy to see your active engagement in the community but sounds like you could use a bit of administrative training to solidify your base knowledge of Prognosis. 

 

Thanks.

Christopher

 


If my answer helped you today, please be sure to mark the resolved button to assist others.

Christopher R Souser - Solution Architect – MSci. PA, CISSP, ITIL.

View solution in original post

Blog: What Optimal Transaction Performance Means

A number of our customers use Prognosis to monitor the health of their payment systems. As part of this, they monitor the transactions flowing through the system ...

Read blog
Top Liked Members