InterMapper provides visual cues to help you understand the states of the devices on your map quickly. Here is a summary of the visual indicators available in your map:
Devices turn different colors depending on the magnitude of the problem detected. Links may be "haloed" with yellow or orange as utilization reaches 50 and 90 percent respectively. These are coupled with status badges, described below.
These are the default color assignments. You can redefine the colors from the Server Settings window.
InterMapper uses status badges as additional visual cues to increase the ease with which you can determine the status of a device among many devices.
Note: You can specify which badges you want appear on devices from the InterMapper User Preferences window.
The Map Legend
The Map legend to the right of the toolbar shows the different states of the map and the number of devices in each state. It also acts as a filter in list view.
Down - No response has been received from the device within the specified timeout period.
Critical - The specified threshold for critical state has been met.
Alarm - The specified threshold for alarm state has been met.
Warning - The specified threshold for warning state has been met.
Up - The device is working below the specified thresholds.
Unknown - The device is not being polled, so its state is unknown.
Acknowledge - Timed or Indefinite - The device's problem has been acknowledged and notifications are being suppressed, either indefinitely, or for a specified period of time. During the designated time period the wrench will be visible whatever the status of the device.
Acknowledge - Basic - The device's problem has been acknowledged, and notifications are being suppressed until the device comes back up, at which time the checkmark is cleared.
List Acknowledged Devices – (Filter button) List all devices that have been acknowledged.
List Un-Acknowledged Devices – (Filter button) List all devices that have not been acknowledged.
InterMapper draws dotted lines ("ants") next to a link to indicate that its current traffic flow is above a user-settable threshold value. Use the Thresholds>Traffic panel of the Map Settings window, available from the Edit menu, to change the settings and to view a legend of the different varieties of ants. You see the ants only in Monitor mode (as opposed to Edit mode.) To toggle between the two modes, click on the padlock icon in the toolbar or press Tab.
InterMapper regularly polls all the visible interfaces for packets, bytes, errors and discards.
Note: InterMapper uses SNMP to query the MIB of SNMP-enabled equipment to compute and display the traffic processed by each interface. Traffic indication appears only for SNMP-enabled devices.
The boxes represent the physical equipment of your network. The ovals represent the networks which link the routers together. The numbers in the bubbles are "network identifiers". For IP networks, the number is the network and the subnet portion of the IP addresses of all devices on it. For example, "126.96.36.199/24" is a network where IP addresses are in the range 188.8.131.52-184.108.40.206, and the subnet mask has 24 bits (it is a Class C network.)
For AppleTalk networks, the number is the AppleTalk network number.
Click and hold on a router or network to see a status window with information about that item. (This only works in "browse" mode -- press Tab, or click on the padlock icon in the upper left corner until it is in the locked position).
The style of the line corresponds to the type of interface.
As with the networks and devices, you can click and hold a link to see a Status window, containing information about the interface type and traffic statistics.
An X in the middle of a line or link means the link (or interface, or port) is down, as determined by SNMP. A red X signifies that the link's operational status is down. This could mean that it's broken, or simply that nothing is plugged into the interface. A blue X signifies that the link's administrative status is down (e.g., it has been explicitly disabled by an administrator.) It can also indicate that the red X has been acknowledged.Many times, a switch is in Alarm state (orange) because it has ports that are not in use, and therefore, down. To resolve this, you should uncheck the ports in the Interfaces window. You can also select all DOWN interfaces in the Edit menu and delete them all at the same time.
Our definition of a probe, is a SNMP, TCP or Command Line query. i.e. querying a device for information and receiving and collecting that information. Use the Set Probe command, available from the Monitor menu, the device's context menu, or by clicking Choose... in the Add Device(s) window, to view the Select Probe window. From this window you can choose and configure the probe for the selected devices.
For a comprehensive list of probes with descriptions, see the Probe Reference.
To choose and configure a probe:
Additional actions available from the Set Probe window:
Import a probe - click this button and select from a standard file dialog to import a probe file.
Reload probe list - click this button to reload the list of probes found in the InterMapper Settings/Probes folder.
Click this button to launch your browser and view a list of probes contributed by InterMapper users. These probes can be downloaded and imported.
InterMapper comes with a set of utility probes that serve a great number of uses. These probe types are described below:
InterMapper first tries to use the Simple Network Management Protocol (SNMP) to communicate with the device. If SNMP is enabled and a SNMP response is received, the probe type automatically changes to "SNMP Traffic" and InterMapper continues to poll the device using SNMP.
If InterMapper is unable to elicit a SNMP response after a number of attempts, the probe type automatically changes to "Ping/Echo" and InterMapper continues to test for basic connectivity.
Use the Map Status probe to place an icon in a map which represents the status of another map. Use the Map Status probe to place an item on your map which represents another map. You can use this probe to hide map detail by creating "sub-maps".
The device shows the current state of the most serious condition on the sub-map.
For IP devices, this probe sends an ICMP Echo Request to the device's address.
The data area in an Echo packet is 20 bytes long and contains the version of InterMapper that sent the request. The data area is configurable in the probe.
This probe retrieves system and traffic information from a device. The information comes from the system and interfaces groups of SNMP MIB-II.
To view traffic (bytes/second, packets/second, errors/minute) for any interface, right-click a link attached to the interface, and choose Status Window.
The device's status window shows sysLocation, sysContact, and sysUptime from the system group.
Note: The SNMP Traffic probe was formerly known as SNMP MIB-II in earlier versions. It was renamed to reflect its purpose more accurately.
InterMapper shows detailed status about any item on a map (a device, a network, or a link) in a Status window, as shown in the Device Status window below.
To view device, network, or link status:
To keep a Status window open:
If you are using a custom TCP or SNMP probe, you can override the default contents of a Status window. For more information, see Custom Probes and Customizing Status Windows in the Developer Guide.
The window shows the device name, network address, device status, the probe used to poll it, up-time (i.e., SNMP sysUptime, if available), availability (the percentage of the time the device was available based on the number of packets lost while testing), round-trip time (in msec), and spanning tree status (if available), and probe-specific information.
When the device reports a problem, the reason for the most important error is shown in red at the bottom of the Status window.
The network status window shows the network's IP address and subnet mask, (if available) and information about the amount of traffic flowing on that network segment. This data comes from all the SNMP devices attached to that network
Note: The traffic statistic shown are only for devices connected to this network that speak SNMP: Ping/Echo, or TCP-based devices (such as HTTP, FTP, etc. probes) do not have this information and are ignored when computing the sums and maximums displayed in the Status Window.
The link status window shows the link's interface name and description, its type (10 or 100 Mbps, 1.5 Mbps T-1, etc.), its status and up-time, its IP, AppleTalk, and MAC addresses (when available), traffic statistics (transmitted from and received by the interface), and the time since the last poll.
Tip: Certain devices do not report their link speed accurately in their SNMP responses. This causes InterMapper to report a value which is not actually correct. To work around this, switch the map to Edit mode, then right-click the link and choose Set Link Speed... The Set Link Speed window appears, allowing you to set Transmit and Receive speeds.
InterMapper strip charts display the history of one or more variables. This information can also be saved to a log file for further analysis.
To create a strip chart:
A strip chart showing two traces.
InterMapper displays historical information in a strip chart. Strip charts can hold an unlimited number of data sets for an unlimited time period. These data can also be written to a tab-delimited text file.
A strip chart is a persistent window that belongs to a particular map. All the data that is displayed in a chart must come from devices or links of that map.
A strip chart showing two data sets.
You view and hide strip charts using the Charts command in the View menu or by selecting options from the Charts menu at the bottom left of the chart's window..
To show an existing strip chart:
To hide a chart:
To scroll the strip chart:
To create a strip chart:
To add a dataset to an existing strip chart:
*The same dataset may appear in more than one chart but it will only be saved to disc once.
You edit the parameters that control a strip chart's content and appearance from the Chart Options window, available from the Strip Chart menu.
You delete strip charts using the Strip Chart menu.
InterMapper provides three menus you can use to view and edit strip charts.
Use the Charts menu to view and hide strip charts.
To show all charts:
To hide all charts:
To view an individual chart:
To view the Strip Chart menu:
The Strip Chart dropdown menu.
The Strip Chart dropdown menu appears.
Use the Time Interval dropdown menu, located next to the Strip Chart dropdown menu icon at the lower left corner of the Chart window to set the time between the tick marks on the strip chart's horizontal axis.
Use the Chart Options window to view and edit the parameters that define a strip chart's appearance and content.
The Chart Options window is available from the Strip Chart menu. or by right-clicking within the strip chart window.
Use the Apply button to apply changes to a chart. Here are some things you should know about using the Apply button:
The chart's title appears in the Charts menu and in the chart's title bar. Enter a title in the Title box.
Vertical Axis Tab parameters
Time Axis Tab parameters
The Data tab shows a lists of data sets used in the current chart. Use the Data tab of the Chart Options window to export a data set, to remove it from the chart, or to edit the appearance of a data set's legend.
The Data tab of the Chart Options window
To remove a data set from the chart:
To export a data set:
Exporting a dataset may take some time and will interrupt polling for large datasets.
To edit the appearance of the legend for a data set:
In the list of data sets, double-click the data for the set whose legend you want to edit. The edit window for the data set's legend appears:
To delete a range of data from a data set:
Use the Colors tab of the Chart Options window to define the colors for various parts of the chart.
To change a color:
InterMapper can send many different kinds of notifications to alert the network manager of problems in the network. An entire map can be configured to use a default notifier (or set of notifiers), and then individual devices can have customized notifiers.
Think of a notifier as a little "robot" that watches the state of one or more devices, and performs a specified action when the device changes to a certain state. The action is called a notification.
You can attach notifiers to a device, and then specify which states (down, up, warning, alarm, critical) should trigger the notifier. When a device changes to that state, the notifier triggers, and InterMapper sends the notification.
For example, you can create a notifier that sends an e-mail message. You then attach that notifier to a device. You might also specify that it should be triggered when the device goes down or comes back up. When the device goes into either of those states, the e-mail would be sent.
There are several types of notifiers; each uses a different method to send a notification:
This is a human-readable description of the notifier. It's useful to include the type and recipient in the name, e.g., "Network Techs via email" or "Syslog to Main Logger"
There are many notifier types - e-mail, sounds, traps, etc. - as listed above. Each notifier you create will cause some kind of notification or alert, depending on its parameters.
The parameters of a notifier indicate the recipient or the action to be performed. Parameters can specify an e-mail address, a sound file to play, the address of a syslog or trap server, a pager account, or a script or program to run. Each notifier type determines its parameters.
Each notifier has a schedule associated with it. The schedule specifies the days of the week, and the hours of each day during which a notifier should send notifications. If the event happens outside the schedule, no notification will be sent.
The Notifier list is a library of notifiers that you can attach to different devices on your map. It is available from the Server Settings window. You create, configure, edit, remove, and disable notifiers from the Notifier list. Once you have created and configured the notifiers you want to use, you can attach them to devices.
Occasionally, you may be about to attach a Notifier, and discover that you need to create a new one before you can attach it. You can quickly open the Notifier list from the Notifiers window, and create a new notifier.
When an event occurs, for example, when a device changes to a new state (Up to Down, Warning to Alarm, Alarm to OK) InterMapper triggers the attached notifiers that apply to that new state. The notifier then sends a notification, as defined in its parameters, to the specified target users as defined by the notifier schedule.
You create and configure notifiers in the Notifier list. You attach notifiers to devices in the Notifiers window.
Notifier List window. The Default Sounds are built-in.
Use the Notifier List to view a list of all notifiers defined for all open maps. You can also use the Notifier List window to:
To view the Notifier List:
To add a notifier:
To edit an existing notifier:
To make a copy of an existing notifier:
To remove a notifier:
To activate or deactivate a notifier:
You can create one or more notifiers that, by default, are attached to every new device you create. When the status of the device changes to a specified state, the notifier sends a notification automatically.
InterMapper ships with one default notifier, called "Default Sounds." It plays a default sound when a device goes down, and another sound when the device comes back up.
To create a set of default notifiers:
Note: Changing default notifiers does not change existing notifiers attached to existing devices; it applies only to newly added devices.
To change all notifiers on a map:
You can attach one or more notifiers to any device. For each notifier, you can choose which states trigger a notification to be sent. For example, a particular device might have a notifier send an e-mail when a device goes down, but can have a second notifier that plays sounds when the same device goes down, comes up, or enters an alarm state. You might also send an e-mail to an on-site system administrator during the day, and to a different administrator outside business hours.
To attach a notifier to an item:
Notifier Settings window
Note: You can create a new notifier from the Notifier Settings window. The "Edit Notifiers..." button is a shortcut to the Notifier List in the Server Settings page.
For each notifier, you can specify Delay, Repeat, and Count parameters. These parameters can be used to control how quickly and how frequently notifications are sent. For example, to avoid unnecessary pages you might configure a notifier to wait until a device has been down for two minutes before sending the first page. You might also choose to re-send a notifier every 10 minutes forever. Notifications are sent until the count is reached, or the device has been acknowledged.
InterMapper maintains a queue of notifications to be sent. When a DOWN, WARN, ALARM or CRITICAL event happens, InterMapper places a notification in the queue, and sets its "time to be sent" according to the delay. (UP, OK and Trap notifications are never delayed.)
When an UP or OK event occurs, InterMapper first searches the notification queue for the corresponding down, warn, or alarm notification. If it's there, InterMapper removes both the DOWN (or Warn or Alarm) notification and UP (OK) event and won't send either one. If not, then InterMapper sends the UP/OK notification straight away.
You can use notifiers to implement a problem escalation system by creating two or more notifiers for a device. The first notifier can fire quickly to alert someone immediately. A second notifier can be delayed for a period of time, perhaps 30 minutes or an hour, before notifying a second person. If the problem remains when the second notifier's delay time is reached, the second notification is sent. As soon as a problem is acknowledged, no further notifications are sent, even if the outage lasts a long time.
Enter a name in the Name box. The name can be any can be any descriptive text string.
Tip: If the notifier is active only at certain times of the day or week, you may want to include a description of the time period as well. For example, you could assign names like "Weekend Pager" and "Second Shift Pager" to notifiers that had those time schedules.
From the Configure Notifier window's Notifier Type dropdown menu, choose a notifier type. For more information, see Notifier Types at the top of this topic.
Select a range of hours during which this notification should be sent.
To set a range of hours:
To add or remove hours from the schedule:
To activate or deactivate all hours in the schedule:
To edit the message sent with the notification:
Once you have created notifiers, you may attach them to all devices (the default notifier is used for all new devices) or to one or more devices.
A typical notification schedule. In this example, an e-mail notification is sent to "firstname.lastname@example.org", at any time -- 24 hours per day and 7 days per week.
The window above shows the Configure Notifier window.
When you select the type of notifier from the Notifier Type dropdown menu, the left pane changes to show the parameters required for the selected notifier type.
You can remove a notifier from the Notifier List window.
To remove a notifier:
A sound notifier plays a sound whenever a device enters a new state. For each state, you can assign a different sound.
The Configure Notifier window for Sound notifier type. For each device state, you can select a different sound.
To configure a sound notifier:
InterMapper uses these default sound notifiers:
You can use sounds in many different ways to help give you audible indicators the condition of your network. Here are two possible uses for sound notifiers.
Sound files must be placed in the InterMapper Settings/Sounds folder before they can be made available in the Server Configuration Notifier List panel of the Server Settings window.
These sound file formats are supported:
Use an e-mail notifier to send an e-mail message to one or more recipients. The e-mail message can provide detailed information about the device that triggered the notifier. The example below shows the Configure Notifier window for the E-mail notifier type.
Configuring an e-mail notifier.
To configure an e-mail notifier:
Note: E-mail is sent using an outgoing SMTP mail server. Before InterMapper can send e-mail notifications, you must specify the SMTP host you want to use for sending e-mail notifications. For more information on how to specify your outgoing SMTP mail server (and a backup server) see E-mail Preferences.
Edit E-mail Message window, showing the default e-mail message.
An E-mail notifier sends a text message that describes the failure.
Use the Edit Message window to edit the message sent by the notifier. The example below shows the Edit E-mail Message window containing the default e-mail message. The list at the lower left contains variables you can substitute in the text.
Double-click an item to insert it into the message text. When the notification is sent, the inserted item is replaced with its current value in the message text.
<Event>: <Device Name>
<Timestamp>: Message from InterMapper <Version> Event: <Event> Name: <Device Name> Document: <Document Name> Address: <Device Address> Probe Type: <Probe Type> Condition: <Device Condition> Time since last reported down: <Last Down> Device's up time: <SysUpTime>
InterMapper can group notifiers together so that a transition to a particular device state sends multiple notifiers, even of different types, for that event.
To create a Group notifier:
When the Group notifier is invoked, InterMapper first checks the time schedule. If the time is applicable, InterMapper invokes each of the checked notifiers. They in turn check their schedules, and send the notification if desired.
Syslog is a mechanism for recording information about significant events into a log file. It originated on Unix hosts which wrote the information to a local file (the system log file). This was later enhanced to write the data across a network to a server that collects the entries.
InterMapper can send a syslog message as a notification. That is, when an event occurs, InterMapper can write the data to a specified syslog server on the network.
Send syslog messages to: - the IP address or DNS name of the syslog server that should receive the message
Facility: - The syslog server administrator may specify that messages from a particular source be tagged with a certain facility code. Select the facility requested by your administrator.
Severity: - Syslog messages can be tagged with a severity, so that the syslog files can be scanned for entries with different priority. Select the desired severity from these choices:
Edit message... - You may enter the format of the syslog message. Newline characters will be converted to spaces, so the message will appear as a single line. Syslog messages will contain "InterMapper" as the syslog tag.
InterMapper can block or suppress notifications for devices that are "behind" or "shadowed by" another failed device. This helps you avoid receiving dozens (or hundreds) of notifications for devices that don't respond because there is a router or link down between InterMapper and that device.
This feature is called dependencies, because InterMapper can suppress the notifications for other devices that depend on the failed device.
There's no need to set the dependencies manually between devices on a map. Instead, InterMapper follows the links that are already part of the map.
To enable dependencies, you set a Vantage Point. The Vantage Point indicates the position from which InterMapper views the network. You usually set the Vantage Point on the actual device where InterMapper is running. Once you've set the Vantage Point, InterMapper can determine which devices are dependent on which other devices.
The example below shows a map with several interconnected routers. The yellow star on the InterMapper icon shows that it is the map's vantage point.
Example 2: One device is down, shows dependent devices
In this example, Router2 has failed. InterMapper will send the normal notifications for Router2, but it will suppress notifications for any of the devices that depend on it. Those dependent devices' icons are dimmed on the map to show they're being shadowed by the failure.
To set a map's Vantage Point:
You may remove a Vantage Point or move it to a new item.
To move a Vantage Point to a new item:
To remove a Vantage Point:
When a device goes down (when no response has been received from it), InterMapper uses the dependencies to determine whether to suppress the notification. Starting at the Vantage Point, InterMapper follows the links toward the device in question.
If the only path to that device passes through a device, link, or interface that's already down, InterMapper knows that the device is shadowed, dims its icon, and suppresses the notifications.
If there is no failure along the path, or if there is no path at all (functional or not) to the device, InterMapper allows the notification to go through.
Even though a device is shadowed (and its notifications are suppressed), InterMapper continually probes the device to show its status.
Use the Acknowledge command, available from the Monitor Menu, to acknowledge failures or problems in the network. When you acknowledge a problem, the InterMapper program does the following:
Acknowledgments allow the network administrator to see the state of the network, as well as the responses that have been made to the current set of problems.
To acknowledge a problem with a device:
InterMapper offers three kinds of acknowledgements:
The device is acknowledged, and notifications are suppressed until it gets better or worse. The icon turns blue to indicate that someone has taken responsibility for it, and that no further notifications will be sent.
As soon as the device's state changes to any other status, its acknowledge status is automatically cleared, and notifications resume. From then on, notifications are sent for any subsequent failures.
Down, with Basic Acknowledgement
The device is acknowledged, and notifications suppressed for the specified period of time. The icon turns blue (if it's not okay), and the wrench badge appears to show that notifications will be blocked for the specified time. In this case, the state of the device is OK.
The device remains acknowledged until the operator unacknowledges it.
As with the Timed acknowledgement, the icon turns blue and the wrench badge appears to remind the operator that notifications are suppressed. In this case, the device is DOWN.
Down, with Indefinite Acknowledgment
Note: With timed and indefinite acknowledge, you can acknowledge a device even when it is up and okay (i.e., green). This is useful if you know that there may be future outages (for example, planned maintenance) with the device, and you want to avoid extraneous notifications. You cannot do this with Basic Acknowledge.
Note: The presence of the wrench badge is a safety measure. When you scan the map visually, the wrench indicates devices whose notifications are currently being blocked.
When you acknowledge a device, use the Block notifications for dependent devices check box to specify whether the acknowledged device should be considered in finding dependencies. Checking the box suppresses notifications for any device "on the other side" of the device being acknowledged.
To suppress notifications for all devices that are dependent on the selected device:
For more information on dependencies and dependent devices, see Using Vantage Points.
Use the Unacknowledge command to restore the device to its current notification state.
To remove the acknowledgement for a device:
Use the InterMapper Reports server to create, view, print and save reports that use data collected from InterMapper servers.
InterMapper Reports is a module of InterMapper DataCenter. Use your favorite browser to use InterMapper Reports to create your reports.
Note: Before you can use it, you must start the InterMapper Reports Server. This allows InterMapper to send data to the Reports Server where it is collected in a database.
To start collecting data:
To view the Reports Server interface:
Use the Reports Server web UI to create, save, load, link, or print a report.
You can open the InterMapper Reports window from an InterMapper map.
To open the InterMapper Reports window:
Two other ways you can also open the Reports window:
There are several ways to create a report:
To create a new report from a template:
The Templates List
Report templates fall into two general categories:
Graph - Can be used with datasets that contain only numeric data. Three display options are available in a Graph report:
Area - a line chart with the area below the line filled.
Table - a tabular report, containing columns and rows.
To create a new report from the Empty Report template:
The image below shows the controls you can use to fine-tune your report definition.
Once in Edit mode, you need to answer some or all of these questions (in the areas shown above), depending on your needs:
Use a number of other controls to customize your report further:
You can save any number of reports, then open, view or print them at a later time. For more information, see Managing and Printing Your Reports .
When creating a report, you first need to choose the devices or interfaces for which data is included in the report.
Use the data source selection bar to select the devices or interfaces for your report.
To select data sources:
To create graphs, you need to select a dataset that contains numeric values. The datasets available depend on which devices are selected, the probes used to monitor those devices, what datasets are recorded through those probes, and whether those datasets are being exported to the Reports Server database.
A dataset is available when retention policy for the selected device is not set to None and one of the following is true:
To select a dataset:
In most cases, the selected time scale causes each data point to represent a group of raw samples. Use the data grouping buttons to specify how you want the group of samples represented by a graph data point to be displayed.
To select data grouping for each time period:
When multiple devices or interfaces are selected, each device or interface's dataset appears as a line or bar on the graph. The Group check box allows you to group the datasets from multiple devices or interfaces into a single dataset that shows the minimum, average or maximum value for all devices in the group over the selected time period.
To view devices or interfaces as one dataset:
In Table view, regardless of the selected dataset, use the Columns selector to choose the columns to show in the report.
Use the page controls to choose the page of data you want to view.
You can limit the amount of data from the dataset that is displayed in the report. In selecting a data range, you select data over a time range, and control the density of that data over the specified range. You do this using the Show Data From controls at the bottom of the window. Select a range of data by date, and specify the units to use (hours, days, weeks, months, etc.). Learn more about data range selection options in Data Range Options, below.
Select a data in a range of time previous to today.
Select all data from beginning of the most recent day, week, month, or year.
The time units vary with your selection.
Select data for a specific date.
All dates before
Select all data before the specified date.
All dates after
Select all data after the specified date.
Select data from the specified range of dates.
In addition to selecting a range of data over time, you can specify the units used to display the data.
Of course, the data units selected affect the time it takes to display the report. (Displaying data every 5 minutes over a year, for example, represents a large amount of data.)
You can limit the amount of data, or select specific subsets within a dataset, using Filters.
To create a filter:
Filters generally have three parts:
The available values for comparison operators depend on the type of data field selected.
Data field options
This menu lists all the available fields in the dataset.
When comparing values in non-numeric fields, a simple boolean comparison operator is available.
When comparing numeric values, a number of comparison operators are available.
You can create filters with more than one set of filter criteria.
To add a filter to an existing filter set:
To remove a filter from an existing filter set:
Four report styles available:
Note: Area, Line, and Bar styles are available only for datasets with numeric values.
Use the report style tabs in the lower right of the window to choose a report style.
Use the Edit button to switch between Edit and View modes.
Use the File and Export menus to create new reports, to Load, Save, to get a Link URL for distribution or to Export a report to a CSV file.
To edit a report, you must be in Edit mode.
To switch to Edit mode:
Reports window in Edit mode
You can save any number of reports, then open, view or print them at a later time.
To open a saved report:
The Saved Reports list
You can delete a saved report from the Saved Reports list.
To delete a saved report:
Use the Report window's Export menu to obtain a URL for distribution, or to export the report data in a CSV file.
To get the URL to a report:
To export a CSV file:
Still have questions? We can help. Submit a case to Technical Support.