Geneos - How to identify broken Database Logging sources

Database Logging

Cell values that are logged to a database for the purpose of historical monitoring are identified in the Active Console by a database symbol.  (Example below shows database logging of the totalProcesses value).

A cell that has issues with database logging would display a red error symbol. (See cpuUtilisation below).

There may be many data cells across many probes and gateways being logged to a database, so how can we best monitor any failings ?

We can collate this information using the reporting tools.

Reporting, to identify issues.

From the Active Console, you can select Reporting from the Tools menu.

Add a new entry in the Reporting pop-up, and then double-click this entry to configure the report.

Now using the Report Settings pop-up.

From the Search Criteria tab 

• Select the Advanced radio button
• Add a new entry using the + symbol
• Click on this new entry and then on the ... button to access the Path Editor
• From the Path Editor, right-click and drag the Table Cell element to create the path, and then click OK.

You may want to limit reporting to only logging failures. If so, then double-click on the Cell entity to get the Properties pop-up and set Login success to false.

The path would now reflect this filter.

From the Results Destination tab

•     Select the File Destination tab
•     Add the filename (with path if required - default path is AC directory)

Now from the Report Schedule tab

Select the appropriate reporting interval.

To run an ad hoc, on demand report, you can set the time to be slightly in advance of current time.

Click OK in the Report Settings pop-up and then the Reporting pop-up to schedule the report.

You can delete the report scheduling after you have run it, or deactivate it if it is to be run again on an ad-hoc basis.

If you have any further questions:

• Please contact with our Client Services team via the chat service box available in any of our websites or via email to support@itrsgroup.com
  
   
• Make sure you provide to us:
  • ANY LOG FILE OR DIAGNOSTIC
  • ANY SCREENSHOT