Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.

 

Home > Success Center > Network Performance Monitor (NPM) > NPM supports both Report Writer and new Web Based Reporting

NPM supports both Report Writer and new Web Based Reporting

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 68 Votes: 0 Revisions: 10

NPM v10.6, supports both Report Writer and new Web Based Reporting.  Both are independent of each other and are fully functional in the latest release.

 

NPM v10.6 Web Based Reporting

The below documentation and video have been created as external resources explaining how to use the new reporting feature in 10.6 (and SAM 6.0). 

Web Based Reporting Documentation:

Blogs

Report Writer (Win32 App) Documentation

Help with Report Writer

Shared Custom Reports

We do not specifically write custom reports for customers. 
For help with customization, post your queries to Thwack and both the customers and internal Solarwinds employees respond to such requests.

Many custom reports are already shared on thwack content exchange, refer to the below links for more information:
http://thwack.solarwinds.com/community/application-and-server_tht/server-and-application-monitor/content?filterID=content~category[reports]&filterID=content~objecttype~objecttype%5Bdocument%5D

Show SQL

In the Report Writer, follow the below steps to view the SQL.

  1. Open Report Writer > Click on the report for which you need to see the SQL.
  2. The Report Designer window opens with few editable tabs. 
  3. Go to the top menu and click Report > Show SQL.
  4. Now, SQL tab will be visible on the Report Designer window and show the SQL behind the Report you have selected in the 1st step.

Note:
You cannot edit the SQL code from this SQL tab.

Advanced SQL reports

Several SQL codes shown in Show SQL > SQL are basic and are used in pulling data from the database tables.  Others are more complex and store SQL views. 
As you cannot edit the SQL directly on the SQL tab, you can do the following if you wish to modify the SQL code:

  1. Click File > New Report > Advanced SQL report, and then Click OK.
  2. Report Designer opens and you can write your own SQL report.

Report Writer Logs

OrionReportWriter.log, available in Logs\Orion\ has a record of all actions, validations, and exceptions related to starting and running the Orion Report Writer.

 

Report Scheduler

Once the report is created, you can view it in Report Writer, WEB Console or use Report Scheduler to email them out automatically once a week\month.
Note: Reports from Report Scheduler are generated from Web Console URL and not from Report Writer.

 

Troubleshooting Logs: 

  • RunOrionJob.log and OrionWeb.log in: C:\ProgramData\Solarwinds\Logs\Orion
  • Job-xxxxx.log in: C:\Program Files (x86)\SolarWinds\Orion
  • Also see CommonHelper.Interop-OrionReportScheduler.log

 

Web Report Scheduler (New in v10.7 and SAM 6.1)

NPM v10.7 is now using its built in Scheduler versus old Windows Task Scheduler.

 

We now have these logs now stored rolling last 6 logs in 
C:\ProgramData\Solarwinds\Logs\Orion\ActionsExecution.log

 

Logs

  • C:\ProgramData\SolarWinds\Logs\Orion\Core.BusinessLayer.log 
    – scheduling and updating schedules.
  • C:\ProgramData\SolarWinds\Logs\Orion\ActionsExecution.log 
    – all action execution is logged here. 
    Each start of action execution is logged with entry from ActionExecutorBase class e.g. “Action [{list of properties}] started ...” 
    and at the end we get message from same ActionExecutorBase class like “Action [{list of properties}] finished successfully.” OR “Action [{list of properties}] failed.”
  • Example issues:
    In Core.BusinessLayer.log log you could find message “Starting action execution” from class ReportJobInitializer. 
    After this, all information about actions executions is logged in ActionsExecution.log.
    If something goes wrong, for example, an email is not sent or report was not fetched from website, it is logged in ActionsExecution.log.
    as this log was separated from Core.BusinessLayer.log to store only information about actions execution.
  • Print action execution is a bit different as during execution it launches PrintLauncher.exe. 
    So It’s launching is logged in ActionsExecution.log but process of printing is logged in C:\ProgramData\SolarWinds\Logs\Orion\PrintLauncher.log
    The Important Class name for printing is HTMLPrinter so look for it when troubleshooting printing action.
  • Reports are kept in memory before sending/saving so there is no need for clean-up after sending email/saving to disk.

Applies to:  NPM v10.6 and later.

Last modified
23:13, 22 Jun 2016

Tags

Classifications

Public