Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Archive > 2017December29 - VMAN Deletes > Best practices for reports in VMAN

Best practices for reports in VMAN

Table of contents
No headers
Created by Lori Krell_ret, last modified by Gerald.Prado on Dec 29, 2017

Views: 392 Votes: 0 Revisions: 3

Create and modify custom reports to through the Orion Web Console for virtual environment historical use, alerts, and recommendations. Orion reporting includes over 40 predefined virtualization reports accessible through My Dashboards > Virtualization > Reporting. Click Manage Reports to review the full list of available reports or create a new report.

Run reports on-demand or schedule for specific systems and times. As you create reports, assign them to an existing schedule or create a new schedule. Every schedule can have different configurations for frequency to run and actions after completion:

  • Frequency: run the report on a specific date or daily, weekly, or monthly.

    Example: Run the report daily at 6 a.m., after overnight maintenance hours.

  • Action: steps to complete when the report runs including sending a report in email (CSV, HTML, PDF, or XLS format), print, or save to disk. Add multiple actions as needed.

    Example: Email a PDF to a network admin mailing list and save a copy in all file types to a snapshot VM.

For more information to create reports, see View, create and schedule reports in the Orion Web Console.

To better create and run reports:

  • Test reports before scheduling. To test performance and format, run your report for a limited date/time range after you customize it. Verify data, table columns, chart content, and performance of the report during peak times.
  • Limit data by time and filter. To refine and speed up report results, modify the data displayed in the report content to filter and limit data. Every report section can be formatted as a chart, graph, table, gauge, and resource available in views and dashboards displaying only selected data available to objects and resources.
  • Schedule reports after maintenance. If you have a nightly maintenance, schedule reports to run after the maintenance window ends. Snapshots and recommendations run during the maintenance that can greatly change the virtual environment. Generating reports after maintenance ends provides immediate updates based on completed VM moves and resource allocation.
  • Schedule heavy load reports after business hours. If a report pulls a large amount of data, or you have multiple larger reports, schedule them to run during off-peak hours.
  • Create copies of reports. Use copies of existing reports to quickly customize reports to gather data per configured objects, resources, and conditions. Report copies give you the flexibility to create multiple versions for specific data gathering and schedules.

  • Create reports for specific virtual objects and date ranges. Create multiple reports for specific virtual systems or data sets for better performance when you generate reports and refine content. Configure a report for specific VM objects (cluster, host, datastore, or VM), the Dynamic Query Builder per object properties (example all VMware or all Hyper-V), or database queries to further restrict virtual objects.

Learn more...

To manage and create reports:

Last modified