Exporting/creating report of monitoring configuration

[Anon]

Hi,

We have been asked to provide Managers with a report/list with every element being currently monitored by Prognosis (thresholds) in our Cisco UC infrastructure.

Is there a way to create such a report/extraction? Basicly we need to provide a detailed list (for example, Excel file) with the different elements that would raise an alert in our Prognosis system should an issue occur.

Prognosis version: 10.4.0

Thanks in advance and best regards.

[Adam_Annen]

Hi Sergio,

That is a great request and I do see how it would be helpful. How much detail are you looking for in the report?

Just the Condition Names in every threshold?
The Conditions names and the message output format?

I can think of one or two approaches depending on the detail required. I could also check to see if we have an existing generic doc on the standard thresholds.

Maybe if you reply with a mocked up sample of what you need?

[Anon]

Hi Adam,

Thanks a lot for your quick reply.

Condition names in every threshold would already be a great help, so if this info is easier/faster to get that could be OK for us. If we could additionally have message output and perhaps associated "where clauses" then it would be perfect. Also, a generic doc on standard thresholds would be a really great asset for us.

Thanks again!

[Adam_Annen]

Hi Sergio,

I'll check a couple records today and see if a custom display is possible on existing data.
- I'm thinking PrognosisViewUsage or PrognosisStatus records right now.

Leave it with me and I'll get back to you with the results.

[Adam_Annen]

Hi Sergio,

As per screenshot below, it is the 'PrognosisAutomationProblem (PROBLEM)' record which can provide a list of all running thresholds and details of all the conditions they have running below them. Once on the display you can export to excel, publish to the web, or database collect it.

What version and patch is your Prognosis on (I need to ensure I create the below display for you on that version - It is currently running on 11.3 below). I'll send you a copy for your version when you let me know. (Note: ANyone else reading this that want's a copy, just reply here and we will ship you out a copy too)

Note: There are advanced sorting and grouping options that might make it look even more pretty.

[Anon]

Hi Adam,

That seems really great stuff, thanks a lot for your efforts.

Our Prognosis version is 10.4.0.

Best regards,
Sergio

[Adam_Annen]

Hi Sergio,

I just emailed you the .dpy file for the custom display and directions for deploying it.
If you do not get the email, or the file gets stripped, let me know.

I hope this custom display proves useful to you.

[Anon]

Hi Adam,

Thanks a lot for your work. It looks very promising. I have emailed you with my feedback and questions.

Best regards,
Sergio

[Deepan]

Hi Adam,

I am looking for all the current active thresholds on our environemt. The version we are running is on 11.9. Is it available by default on the current versions? Could you pelase share this display with me? 

[SCOTT_BALDWIN]

Hi @Deepan,

Open the Prognosis Status Display/Dashboard for each Prognosis server will show the running Thresholds (along with other Prognosis processes). Although this can be done from the Managing Node's Web UI or Windows Client, there does not appear to be a built in Display/Dashboard showing all Thresholds for all Prognosis Nodes.

The irfax of a Prognosis Node will also show the running Thresholds.

2 Options are available to see all the Thresholds at once.

Option 1:

Install and configuration Prognosis Self Monitoring (PSM).

• PSM requires some configuration by the end user, but it is a Display/Dashboard to show Prognosis health items not shown in Prognosis Status Display.
• PSM is only installed on the Managing Node and aggregates data from all the Monitoring Nodes.
• PSM is also able to alert if a Threshold stops.
• PSM is a solution from Support. Please open a Support case to request this solution.

Option 2:

• Create a Display to showing the PrognosisStatus (PSTATUS) record. The Where Clause should be set so field ProcessType (TYPE) equals "THRESH".
• The Where Clause would be something like this TYPE = "THRESH"

Thank you,
Scott Baldwin