Posts

ReportMagic 2.21

As we continue to progress with a new 3.0 user interface, with significant scalability and architecture benefits, ReportMagic 2.21 is released as a bug fix and maintenance release with a few small changes. Improvements A newly registered user who has confirmed their email address now receives a more reassuring message when their account has yet to be approved by their Tenant Administrator. A Security link is now available to non logged in site visitors, enabling the viewing of the security policy without the need to register. The API has been decoupled from the installer.  This seamless change ensures the API remains available in the usual way. Bug Fixes and Other Work There have been fixes to some graph macros.  The yAxisIsLogarithmic parameter is now better supported by the [LogicMonitor,Graph:] macro and the [List.Graph:] macro handles poorly specified donut chart data more gracefully. The progress page no longer presents message, status and macro breakdown statistics entir...

ReportMagic 2.20

As we continue to progress with a new 3.0 user interface, with significant scalability and architecture benefits, ReportMagic 2.20 is released as a bug fix and maintenance release with a few small changes. Improvements In Files, the 10-file limit at any one time has been relaxed. You can now upload or download up to 100 files at once. More detailed help is included showing our method of determining which alerts to include in macros, and why alert counts may differ to the those shown in LogicMonitor. When you create or edit Schedules, there is now an additional Description field shown. The LogicMonitor HealthCheck template has been updated. Bug Fixes and Other Work  A bug was fixed in the LogicMonitor HealthCheck stopping the portal URL being correctly obtained. You are no longer able to clone or update a Schedule which you then cannot read due to RBAC.

ReportMagic 2.19

Improvements LogicMonitor macros now pause during LogicMonitor portal upgrade, and retry every 10 seconds until the service is available. You can change this, the default behaviour, by setting waitDuringUpgrades for your LogicMonitor connection in Macro Parameter Defaults. You can also set this as a parameter on all LogicMonitor macros, which overrides any other defaults. You can redact the results of macros that produce textual output by setting the new redact parameter to true (default is false). This replaces substituted macro text and output macro text in the results, user interface and database with the word REDACTED. You can set a a clean up age (days) for the output folder of your Schedules. Any files in that folder / sub-folders are deleted if older than the specified value. You can of course set them not to age, or use a Tenant-level default (set by a Tenant Admin). [ReportMagic.ReportScheduleProperty:] and [ReportMagic.ReportScheduleList:] macros now allow you to specify mult...

ReportMagic 2.18

New Macros Many, many new Meraki macros! [Meraki.NetworkClientList: ] [Meraki.WirelessNetworkDevicesLatencyList: ] [Meraki.WirelessNetworkDeviceLatencyList: ] [Meraki.WirelessNetworkClientsLatencyList: ] [Meraki.WirelessNetworkClientLatencyList: ] [Meraki.WirelessNetworkDevicesConnectionStatsList: ] [Meraki.WirelessNetworkClientsConnectionStatsList: ] [Meraki.WirelessNetworkConnectionStatsProperty: ] [Meraki.WirelessNetworkDeviceConnectionStatsProperty: ] [Meraki.WirelessNetworkClientConnectionStatsProperty: ] Also: [ReportMagic.ConnectionStatusProperty:] macro determines the status of a ReportMagic connection so you can avoid running a section of a report if the remote system is unavailable. Improvements It is now possible to clean up old files from the output folder on Report Schedule execution. API: It is now possible to determine the status of a connection. [ReportMagic.ConnectionList: ] now supports skip and take parameters ReportMagicClient nuget package now makes a PUT request i...

ReportMagic 2.17

Introducing... RM Scripts! With the released of ReportMagic 2.17, it is now possible to move many of the hard-to-read macros out of your Report Template (.docx or .html) document and into one or more "RM Script" files. We hope that this new feature provides a much better development experience for power developers. Script development To develop a new RM Script: Create a new file in your Input folder with an ".rmscript" file extension (e.g. "test.rmscript") Right click on the file and click "edit in Report Studio" Develop the script: Enter macros, one or more per line You can add any whitespace, including tabs, spaces and newline characters, these are all stripped out before execution You can add any other characters between the macros - these are also stripped out when executing. To test, press the play button.  Note that there is no output, but the variables in the variables are updated. Script usage To use the RM Script: In your Report Template...

ReportMagic 2.16

In ReportMagic 2.16, the ReportMagic Agent now support Linux. This has been implemented as a native binary running on Centos 8 managed by systemd. Documentation is provided with the binary. Other than that, this version is a bug fix release.

ReportMagic 2.15

Enhanced Meraki Reporting Capabilities ReportMagic 2.15 contains enhanced Meraki reporting capabilities, Meraki HTTP reporting access connection support and the following new macros: [Meraki.ReportOrganizationList:] [Meraki.ReportTopDevicesUsageList;]  [Meraki.ReportNetworkClientsTotalsProperty:] to obtain client totals for a network for a given period [Meraki.ReportNetworkClientsPerDayList:] to obtain Meraki network clients per day [Meraki.ReportNetworkThroughput:] [Meraki.OrganizationDeviceListStatusProperty:] Additionally, you'll find a new template in the Library which provides detailed reporting information based upon the Meraki Dashboard Summary Report page. Other Improvements  The [Meraki.ReportNetworkEthPowerPerDayList;] macro can show increased numbers of datapoints, up from the previous maximum of 50. Updated version of the LogicMonitor HealthCheck New In RBAC: Layout more aligned with workflow  Additional feedback messages The [Sql.Graph:] macro now suppor...