Sightline Enterprise Data Manager (EDM) Software Release Notes · 2019. 6. 6. · These release...

4035 Ridge Top Road, Suite 510 Fairfax, VA 22030

Phone: (703) 563-3000 [email protected]

Sightline EDM Release Notes of 40 © 2019 Sightline Systems

Sightline Enterprise Data Manager (EDM) Software Release Notes

Contents Introduction ................................................................................................................................................... 2

Power Agent Compatibility .......................................................................................................................... 2

Recommended Configuration ....................................................................................................................... 2

EDM 5.9 (June 2019) .................................................................................................................................... 4

EDM 5.8.3 (May 2019) ................................................................................................................................. 6

EDM 5.8.2 (May 2019) ................................................................................................................................. 7

EDM 5.8.1 (April 2019) ................................................................................................................................ 7

EDM 5.8 (February 2019) ............................................................................................................................. 8

EDM 5.7.4 (December 2018) ...................................................................................................................... 12

EDM 5.7.3 (December 2018) ...................................................................................................................... 12

EDM 5.7.2 (December 2018) ...................................................................................................................... 12

EDM 5.7 (November 2018) ........................................................................................................................ 13

EDM 5.6.1 (October 2018) ......................................................................................................................... 14

EDM 5.6 (August 2018) ............................................................................................................................. 15

EDM 5.5.6 (July 2018) ............................................................................................................................... 17

EDM 5.5.5 (June 2018) ............................................................................................................................... 18

EDM 5.5.4 (May 2018) ............................................................................................................................... 19

EDM 5.5.3 (April 2018) .............................................................................................................................. 19

EDM 5.5.2 (April 2018) .............................................................................................................................. 20

EDM 5.5.1 (April 2018) .............................................................................................................................. 21

EDM 5.5 (April 2018) ................................................................................................................................. 21

EDM 5.4.4 (February 2018) ........................................................................................................................ 25

EDM 5.4.2 (September 2017) ..................................................................................................................... 25

EDM 5.4.1 (August 2017) .......................................................................................................................... 26

EDM 5.4 (July 2017) .................................................................................................................................. 27

EDM 5.3.3 (June 2017) ............................................................................................................................... 30

EDM 5.3.2 (May 2017) ............................................................................................................................... 30

EDM 5.3 (May 2017) .................................................................................................................................. 31

EDM 5.2.3 (April 2017) .............................................................................................................................. 32


EDM 5.2.2 (April 2017) .............................................................................................................................. 32

EDM 5.2.1 (April 2017) .............................................................................................................................. 32

EDM 5.2.0 (March 2017) ............................................................................................................................ 33

EDM 5.1.5 (March 2017) ............................................................................................................................ 34

EDM 5.1.0 (February 2017) ........................................................................................................................ 35

EDM 5.0.0 (December 2016) ...................................................................................................................... 37

Introduction Sightline Enterprise Data Manager (EDM) provides centralized data collection, alerting, archiving and summarization for data provided by Sightline Power Agents and Interface Agents, as well as data collected agent-lessly from other data sources. EDM also provides a web-based interface for data visualization, root cause analysis and Agent Administration and configuration. These release notes describe new features and updates included release version 5.9 of Sightline EDM.

Power Agent Compatibility This release of EDM is compatible with all data sources provided by the Sightline Power Agents and Interface Agents. This release supports web-based Agent Administration for Power Agents running a supported version of the SLAA Listener. For specific versions, contact your Sightline support representative.

Recommended Configuration Operating Systems

• Windows Server 2008 • Windows Server 2012 • Windows Server 2016 • SuSE Linux Enterprise Server • Red Hat Enterprise Linux • Oracle Linux

Supported Browsers

• Chrome • Firefox • Internet Explorer


Java

EDM version Java version 5.x JRE or JDK 8

JBoss / Wildfly

EDM version JBoss version 5.0.x, 5.1.x, 5.2.x, 5.3.x, 5.4.x, 5.5.x, 5.6.x, 5.7.x

Wildfly-8.2.0.Final

5.8.x, 5.9 Wildfly-13.0.0.Final

Admin Database

EDM version Database type and version 5.0.x, 5.1.x, 5.2.x, 5.3.x,

5.4.x, 5.5.x • Microsoft SQL Server 2008, 2012, 2014 • MySQL 5.5, 5.6.20, 5.7.x • Oracle 11g R1, R2, Oracle 12c • PostgresSQL 9.2

5.6.x, 5.7.x • Microsoft SQL Server 2008, 2012, 2014 • MySQL 5.5, 5.6.20, 5.7.x • Oracle 11g R1, R2, Oracle 12c • PostgresSQL 10.4

5.8.x, 5.9 • Microsoft SQL Server 2012, 2014 • MySQL 5.5, 5.6.20, 5.7.x • Oracle 11g R1, R2, Oracle 12c • PostgresSQL 10.4

Database for Live Performance Data Repository

EDM version Database type and version 5.0.x, 5.1.x, 5.2.x, 5.3.x,

5.4.x, 5.5-5.5.4 • SightlineDB 1.4.2

5.5.5, 5.6.x, 5.7.x • SightlineDB 1.5.2 5.8.x, 5.9 • SightlineDB 1.7.1

JMS Database for Archive and Summary Data

EDM version Database type and version 5.x • Microsoft SQL Server 2008, 2012, 2014

• MySQL 5.5, 5.6.20, 5.7.x • Oracle 11g R1, R2, Oracle 12c


EDM 5.9 (June 2019) New Features

New Text chart type (ticket #25254) Text charts contain predefined text rather than charts or tables. EDM includes a WYSIWYG editor to create the text chart, which can include text, tables and images. Sightline macros have been introduced to include metric and system values. Text charts can be included in templates for reports or dashboards. New Macro language for text charts As part of the implementation of the new Text chart type, a group of macros has been introduced for use in reports and dashboards. See the Sightline EDM User’s Guide for details. Scheduled dashboards (ticket #25282) Dashboards can now be scheduled, similar to scheduled reports. Based on the combination of the report template, time definition and selected connection view, the dashboard will be rendered internally and printed to PDF. Add option to dashboard template for section repetition (ticket #25008) The Dashboards feature in EDM has been enhanced such that each section can be presented only once or once per connection in the selected Connection View. Enable custom headers and footers on printed reports (ticket #23550) The ability to add headers and footers to printed reports and dashboards, including page numbers, has been implemented in EDM. Standard timestamp formats allowed in CSV and EVT input files The first column in a CSV or EVT file is assumed the time column, usually the header "Time" is inserted. This header can now be used to define the time format; for instance, MM/dd/yyyy hh:mm:ss.SSS. Any value other than "Time" will be interpreted as a timestamp format. Schedule Export to CSV functionality Exports can be scheduled to CSV or PDF files, or both. This is configured on the report; the output format is selected when the schedule is added to the report definition. Allow Forecast charts in reports and dashboards Forecast charts can now be included in reports and dashboards, by adding a chart with the forecast option enabled to the report template. Sort indicator view display (ticket #25232) An option has been added to the Indicator chart definition to specify the sort order: Alphabetical, average ascending or descending or sort by status; that is, show red indicators first, then yellow and then green. The order can also be specified by metric or connection. Support Japanese characters in OPC connections (ticket # 24754) Japanese characters are supported for OPC connections; Japanese metrics names can be included in the OPC mapping file.


Specify metric order in charts (ticket #25394) Users can now specify the order that metrics are presented in charts and reports. Order precedence can be specified by metric name or by connection.

Changes

Settings for Actions on Alert Cleared not saved (ticket #25494) When configuring an alert, settings for the Actions on Alert Cleared were not saved in the alert definition. This has been corrected. Japanese characters in Event Data are corrupted (ticket #25485) Japanese characters in the input EVT file or a file connection were read and stored in the SightlineDB database, but were corrupted in the EDM display. This has been corrected, and Japanese event data items will display correctly. ArrayIndexOutOfBoundsException in DCS log file (ticket #25429) While looking at the DCS log file, a user noticed an ArrayIndexOutOfBoundsException. Investigation showed that this was caused by a symbol table change for an extremely large array. When adding a new metric, DCS modified the index variable of the original symbol, rather than new newly created object. This has been corrected. Selected date format not used (tickets #25428, 25424) The date format selected in the System Settings was not correctly reflected in the Forecast Alerts list on the Connections tab, or in the the AutoInvestigate Results display. This has been corrected. Time scale is not redrawn after zooming in forecast alert chart (ticket #25427) When zooming into a forecast alert chart, the details of the time range were not revised properly. This has been corrected. Hidden legend items displayed after zooming into the chart (ticket #25425) After hiding metrics in a chart’s legend, they are redisplayed when the user zooms into the chart. This has been corrected, and hidden legend items and their associated metrics in the display will remain hidden after zooming. Update Windows 1-click installer script with PATHEXT for .bat files (ticket #25423) The EDM 1-click installer for Windows systems did not successfully install the Enterprise Data Manager software suite, because the call for the installation batch script did not include the .bat extension and PATHEXT was not set. This has been corrected. . Milliseconds don't display in table charts (ticket #25417) When displaying metric values in table charts, timestamps with milliseconds did not include the milliseconds. This has been corrected. Allow Japanese characters in connection names (ticket #25377) We now support UTF-8 characters in host names and connection names. Allow Japanese characters in metric names (ticket #25376) We now support UTF-8 characters in metric names and group names for File connections. This functionality is supported only when using SightlineDB for the data repository; when using trace files the EDM system will incorrectly report the successful collection of data.


No connection name in alert log entry (ticket #22064) Alert entries in DCS’s files did not contain the name of the connection that the alert related to. This has been changed, and the connection name has been added to provide more complete information to the user. Array function [.*cnt] not evaluating correctly The array function [.*cnt] should return the number of subscripts for the specified array metric, but was not evaluating correctly. This has been corrected. Importing a nettf.vnt into EDM created empty schedules A user imported a nettf.vnt file into EDM that contained schedules for some connection definitions. This caused empty schedules to be created in EDM, which prevented the user from editing the connection's details. This has been corrected; the nettf.vnt file will now import correctly, with the appropriate schedules being created and assigned to the connections. Sort dropdown selection for Connections on dashboards alphabetically The dropdown list for connections on the Dashboards page are now sorted alphabetically.

Known Issues

Japanese characters are missing or corrupted In the RHEL 7 / CentOS 7 release, the language font group packages are no longer available. Instead, these releases have groupinstall lists which bundle multiple packages together. There is a single Fonts package which includes support for all Asian fonts, and this issue is resolved by installing the following group package: yum groupinstall Fonts Cannot use logarithmic scale on alert chart Logarithmic scales cannot be used on alert charts with metric thresholds of zero or less than zero. The user will be alerted if this combination occurs. PATHEXT must include .bat extension (ticket #25423) The EDM 1-click installer for Windows systems did not successfully install the EDM software, because the .bat extension was not set in the PATHEXT variable. The script must be executable or it will not run, so PATHEXT must include .bat.

EDM 5.8.3 (May 2019) Changes

Dashboard misses connections (ticket #25491) When producing a dashboard for a view with over 600 connections, not all of the connections were included in the display. Investigation revealed an issue when creating very large dashboards. This has been corrected, and all connections will be included in the dashboard when it is created.



Performance updates for I/O to SightlineDB Improved data handling in DCS when writing data to the SightlineDB data repository. These updates have no affect for EDM implementations that use trace files as the performance data repository.

EDM 5.8.1 (April 2019) Changes

All zoomed charts are reset in report when only one is selected (ticket #25426) After zooming multiple charts in a report, resetting only one chart causes all of the charts to be reset. This has been corrected, and only the selected chart will be reset. Table chart time range cannot be changed (ticket #25418) After displaying a table chart, changes to the time range and summarization settings were not applied. This has been corrected. CNR not working on File connections (ticket #25416) The Correlation Noise Reduction (CNR) feature did not exclude metrics from same metrics group when correlating metrics from File connection. This has been corrected. Correlation Results chart not displayed (ticket #25415) The correlation results chart is not always displayed when the list of Additional Data Sources contains connections that do not have data for the selected time range. Also, when this happens, clicking the green plus icon beside the metric's name results in a non-responsive “Loading” display that does not time out. This has been corrected. Time range on correlation results chart not updated after zooming (ticket #25413) After zooming into a correlation result chart, the time range was not updated to reflect the new start and end times of the metrics being displayed. This has been corrected. Zooming not working correctly in correlation results chart (ticket #25412) When zooming into the chart on a correlation result display, the selected area is not cleared; that is, the gray highlight remains in the display. This has been corrected. DCS dropping connections (ticket #25323) A new parameter called dcs.sightlinedb.threadpool has been introduced, which can be added to the DCS config.properties file. This specifies the number of threads that are continuously writing data to SightlineDB, and defaults to the number of cores available on the DCS machine. The following settings in the DCS config.properties file need to be changed or added:

ds.connection.timeout = 120 dcs.sightlinedb.threadpool=128


The following settings in the sightlinedb.conf file also need to change: [coordinator] timeout=60s [data] cache-max-memory-size = "2048576000" [data] max-concurrent-compactions = 4

SightlineDB requires 96 GB of memory. Enhanced logging Updates have been made to include additional information in the log files that are written by EDM and DCS.

EDM 5.8 (February 2019) New Features

New Table chart type Selected metrics are presented in a table format, with the timestamps in the first column on the left and the values for each metric in subsequent columns. Table charts can be used in Quick Charts and charts within reports. Hide all/show all metrics in a chart (ticket #24662) When the legend is visible in a chart, clicking one entry will hide that metric in the chart. You can now Shift+click on a metric name in the legend to hide all other metrics in the chart, leaving the selected metric visible. When there are hidden metrics, then Shift+click on the name of a hidden metric and all metrics will be shown in the chart. Use Ctrl+click to show a metric and have all other metrics' visibility become opposite of what they were. SightlineDB support on Windows systems SightlineDB is now supported on Windows systems, and will be the default data repository on new installations of EDM. New file descriptor metrics for JVM connections Two new metrics, JVM.OpenFileDescriptor and JVM.MaxFileDescriptor, are now included in the Wildfly 8+ datasource when they are running on Linux platforms. Support for multiple pop-out windows In previous versions of EDM, only one pop-out window was supported for a browser instance; for instance, only one Quick Chart or chart popped out from a report. This has been changed, and now multiple popped out charts are supported. Dynamic alerts implemented for SightlineDB In previous releases of EDM, dynamic alerts were evaluated only when EDM used trace files as the data repository. This functionality is now implemented for EDM installations using SightlineDB.


Changes

Upgrade to Wildfly 13 EDM 5.8 uses Wildfly 13 application server for its underlying framework; previous versions of EDM 5.x used Wildfly 8. Upgrades will need to use the Wildfly 13.0.0.Final version. Note that you may need to download Wildfly 13 before performing the EDM upgrade; contact your Sightline representative for more information. Java upgrade The EDM 1-click installers have been updated to use Java 8 update 181. Send Email Alerts checkbox is unchecked (ticket #25389) The customer reported that when editing a connection’s settings, and moving between tabs, the display of the Send Email Alerts checkbox may be delayed, and edits were not always saved properly for this and other connection custom fields. This refresh issue has been corrected. EDM not responsive (ticket #25371, 25378) On a system with 96 GB of RAM, and 50 allocated to JVM, EDM ran out of memory. At other times, EDM was intermittently observed to be non-responsive. Performance enhancements have been made to address these issues. SightlineDB not starting properly (ticket #25366) While normally starting almost immediately, SightlineDB was observed to take an excessive amount of time to start. This is actually normal behavior, due to periodic compaction processing within the database, and has been documented in the Sightline EDM User’s Guide. Data for specified time range not exported to CSV (ticket #25358) After changing the time range on popout chart, the user selected Export to CSV. However, the data of the exported CSV was the data before changing the time range. This has been corrected, and the data for the correct time range will be exported. Only summary data displayed from SightlineDB (ticket #25343) When DCS was configured to read from SightlineDB, a few minutes after initial DCS startup live metric data was not accessible by EDM, only summarized data was displayed. In this instance, the requested time range was much longer than the amount of data available. This has been corrected, and live data is immediately available to EDM in this situation. Export to CSV button not available on Event window (ticket #25324) The Export to CSV capability was not implemented for all user roles. This has been corrected, and the Export to CSV button is now available for all users. Issues with dropped connections (ticket #25323) Enhancements have been made to prevent connections from dropping. When writing event data to SightlineDB fails, the connection will be retried rather than disconnected. Also, when migrating from trace files to SightlineDB, the number of connections can be configured rather than using a hard-coded value set to the number of processors on the system. Time selection disappears from Event list display when sorting (ticket #25195) When restricting the Event list to 0 intervals (to display events from only one time point), then sorting the list, all records from the number of intervals according to the system default were added back into the display.This has been corrected.


EDM connection doesn’t start with SSL enabled (ticket #25183) The Wildfly (EDM) connection could not start after configuring SSL at the customer’s site. This was due to a bug in Wildfly 8, which has been corrected in Wildfly 13. Not all event data is included when sorting in Quick Charts (ticket #25070) When sorting the event data at the bottom of the Quick Chart, only the five original event data lines were included in the sort. This has been corrected, and the entire set of event data lines for the time point are included when sorting the event data. Meter charts not displaying correct entries for Show Top/Bottom selection (ticket #25005) The Show Top/Bottom N feature was coded to use MAX (for top) and MIN (for bottom) statistics, which could lead to confusion over why certain metrics were listed. This has been changed to use the AVG of the metric data over the specified time period to select what should be Top and Bottom N. Connection dropped due to trace file size limit (ticket #24888) After increasing the retention policy for a connection, the connection would not stay active. Investigation revealed that the longer retention policy would require a trace file larger than the maximum size of 16GB. This has been corrected, and the trace file will be sized at 16GB so that the connection can be established. Details will be written in the connection’s log file. Edit a chart’s characteristics from within a report (ticket #24455, #24456) The Edit Chart Options dialog box now includes the ability to edit a chart’s scale, title and sub-caption, show/hide legend, and other chart-specific options. Store data for Utilization Reports in the SightlineDB data repository (ticket #23450, #23315) When using SightlineDB as the data repository, data for Utilization Reports will be stored in the SightlineDB database. If trace files are being used, the Utilization Report data will be stored in EDM’s admin database. Access EDM report URL without logging into EDM (tickets #22704, #24586, #25267) When clicking on a report URL to display the report, users may see an EDM login screen. To display the report without having to log into EDM, append &login=false to the end of the URL. SNMP v2 and v3 INFORMS are now handled by EDM These INFORMs are processed the same way that EDM creates an alert when receiving an SNMP v2 or SNMP v3 trap. Agentless monitoring for SMI-S compliant storage arrays Enhancements have been made to the SMI-S data collection capability in EDM, for collection data from SMI-S compliant storage arrays. See the EDM User’s Guide for more details. No time range on AutoInvestigate results This has been corrected, and the time range is now included in the AutoInvestigate display. Cannot chart data with subscripts containing a plus (+) sign or brackets When using SightlineDB as the data repository, subscripts containing a plus (+) sign or brackets ( [] ) could not be displayed in charts. This has been corrected.


Updated Clairvor display behavior In previous versions of EDM, the Waiting message on the Clairvor window could inhibit user interaction until the complete Clairvor results were presented. This has been changed, and the Clairvor results are displayed in a new tab, with each section shown as it becomes available. In addition, you can now open multiple Clairvor windows. Customized charts (from reports) are no longer listed in the Charts table When a chart is customized in a report, EDM creates an internal copy of the chart. These charts are for EDM's internal reference when rendering the report, and should not be included in the Charts table. This has been corrected, and only user-defined charts are now shown. File data source re-reading the same file If a file took longer than the file interval to be read, it would cause the same file to start to be read again and again, ad infinitum. This has been corrected. Store millisecond data in JMS data repository You can now configure DCS to write millisecond data in a JMS data repository. The database.timestamp.milliseconds setting has been added to the jmsconfig.properties file to facilitate this option; see the Sightline EDM User’s Guide for more information. Dynamic alert information not deleted from admin database If dynamic alerts were enabled on forecasts, the administrative database could grow fairly large because rows were not deleted from the T_CONFIDENCE_BAND table when their corresponding rows were deleted from the T_FORECAST_RESULTS table. This has been corrected. In addition, the upgrade script for EDM 5.8 will delete any abandoned records during the upgrade.

Known issues

Scheduled report not created (ticket #25374) After investigating, it was determined that the absence of certain font files on Linux systems can cause scheduled reports to fail; installing the font files resolve this issue. See the EDM User’s Guide for more information. SightlineDB takes a long time to start (ticket #25366) While normally starting almost immediately, SightlineDB occasionally took an excessive amount of time to start. This is normal behavior, due to periodic compaction processing within the database, and has been documented in the Sightline EDM User’s Guide.

Upgrading to EDM 5.8

EDM 5.8 uses Wildfly 13 application server for its underlying framework; previous versions of EDM 5.x used Wildfly 8. Upgrades will need to use the Wildfly 13.0.0.Final version. Contact your Sightline representative for more information. To upgrade EDM to EDM 5.8, follow the installation steps in Section 2.3 of the Sightline EDM User’s Guide.

Before the installation you will need to download Wildfly 13.0.0.Final and unzip it into the directory where Wildfly 8 currently resides; for instance, \Sightline\EDM\Wildfly-8.2.0.Final\*.* and \Sightline\EDM\Wildfly-13.0.0.Final\*.*

Update the JBOSS_HOME environment variable from Wildfly 8 to Wildfly 13.


Begin the EDM 5.8 installation. In Step 3, the new Wildfly 13 directory will be the Installation Path. Enter the Wildfly 8

directory as the Previous Version Installation Path. Continue the installation as documented in the EDM User’s Guide.

Note that if you installed EDM using a 1-click installer then the upgrade can be performed using the 1-click installer for EDM 5.8, which will perform all of the above steps.

EDM 5.7.4 (December 2018) Changes

Event data written with incorrect timestamp (ticket #25349) Event data from millisecond data sources was written to the RDBMS database with the wrong epoch timestamp value. This has been corrected, and will now follow the seconds or milliseconds setting in the jmsconfig.properties file. Alert emails not always sent (tickets #25302, #25320) A user noticed that all alert emails were being sent, although the triggered alerts were shown in the Triggered Alerts list. This has been corrected, and all alert emails will now be sent. Excessive blank space at the top of scheduled reports When printing reports, a excessive amount of white space is included in the top margin. This has been corrected.

EDM 5.7.3 (December 2018) Changes

DCS hangs after dropping connections (ticket #25323) After several days, connections dropped but were not reconnected, and ultimately the DCS process locked up and had to be restarted. This has been resolved by not allowing any connection to remain in the TLC thread loop for more than two minutes. The firewall network code has also been re-worked to use all of the defined firewall range, rather than a single port.

EDM 5.7.2 (December 2018) New Features

JMS can now write metric data in millisecond format When upgrading to EDM 5.7.2, a new jmsconfig.properties file will be created, to configure the JMS timestamp format. By default, JMS will continue to write timestamps in second format for backwards compatibility with previous customers.


Changes

OPC connections caused other connections to be deadlocked This was caused by a timing problem in the data collection code, when such a large amount of data was collected that it exceeded the summary interval. This has been corrected, and some OPC data collections can no longer occur in an overlapping fashion. Memory and thread leak from failed SNMPv3 connection During internal testing, a memory leak was observed from a failed SNMPv3 connection. In addition, a handle leak was observed when an SNMPv2 connection repeatedly attempted to connect to an SNMPv3-only source. These issues have been addressed, and we no longer leak threads, handles, and memory for failed SNMP connections.

EDM 5.7 (November 2018) New Features

Dynamic alert functionality refactored In previous releases of EDM, dynamic alerts were evaluated only on EDM implementations using trace files as the data repository. This functionality is now implemented for EDM implementations using SightlineDB. In addition, the functionality of the dynamic alert feature has been refactored to produce more accurate results and displays. Global Connect all Data Points setting can be overridden at the chart level When charting data that may contain gaps, you can now select Connect all data points on a per-chart basis. In addition, you can override the global setting for connecting all data points (set in Settings > System Settings > Chart Settings) for individual charts.

Changes

User roles and views not behaving properly (ticket #25294) When there are no public views and no private views are assigned to the user, selecting a tab (such as Hosts or Connections) threw the user back to the login screen. This has been corrected, and the user will now be moved to the selected tab with the message “No views configured” on display. Private Connection view not applied to Choose Data Source drop-down lists (ticket #25294) When there are no public views, the Choose Data Source drop-down lists still contained all available data sources. This has been corrected, and the drop-downs will now contain only those data sources from Connection Views that are assigned to the user. URL for pop-out report generated incorrectly (ticket #25285) When a report is popped out from a report, the URL of the new browser tab was converted from the IP address to the hostname. In an environment where the hostname cannot be resolved, the pop-out report is not displayed. This has been corrected, the the URL for the popped out report will retain the system reference from the original URL. REST API data retrieval request failed after EDM upgrade (ticket #25280) The API request failed when no time reference was specified. This issue is specific to SightlineDB implementations of EDM; trace file implementations were not affected. This has been corrected.


Chart Height setting not applied to Statistics charts (ticket #25257) A statistics chart contained only a few entries, leaving a lot of blank space beneath it. Changing the chart height to suppress the blank space had no affect. This has been corrected. Top List chart does not retain sort column after refresh (ticket #25228) The user selected a sort column for the Top List chart, not using the first column. However, after the chart was refreshed the display was sorted on the first (default) column. This has been corrected, and the selected column will remain as the sort column after the Top List chart is refreshed. Top List charts not sorting correctly (ticket #25196) When sorting a Top List display, columns with zeros or empty values were not always sorted properly. This has been corrected. Top List charts not working with expressions (ticket #25194) When SightlineDB was used as the data repository, Top List charts based on array expressions were empty. This has been corrected. Sightline EDM and DCS not starting after system reboot (ticket #25172) Sightline EDM, DCS and Power Agent did not restart after rebooting the RHEL system where they are installed. This has been corrected by replacing the symlink with scripts in the /etc/init.d/ folder, to account for the possibility that the software is installed on a non-rootvg file system.

EDM 5.6.1 (October 2018) Changes

SNMPv3 traps not being received by DCS (tickets #25264, #23955) SNMPv1 and SNMPv2c traps were received by DCS at the customer site, and displayed in the Alerts table as expected. SNMPv3 traps were received but not processed correctly. We now support SNMPv3 traps using the security authorizations MD5 and SHA, and privacy protocols DES and AES128, AES196, and AES256. User configurations are defined in snmp_v3.properties in the resources\settings directory, with the format: <Username>, <Auth Protocol>, <Auth Passphrase>, <Priv Protocol>, <Priv Passphrase> Examples: user1, none, , none, user2, MD5, 1234567890abcdef, none, user3, SHA, 1234567890abcdef, none, user4, MD5, 1234567890abcdef, DES, 1234567890abcdef user5, SHA, 1234567890abcdef, DES, 1234567890abcdef user6, MD5, 1234567890abcdef, AES, 1234567890abcdef user7, SHA, 1234567890abcdef, AES, 1234567890abcdef All commas must be present, but if there is no passphrase then the field may be left blank. Note that AES is simply a shortcut to AES128, so they are equivalent.


Event data not accessible with German locale (ticket #25262) Event data was not displayed in EDM, due to an error when parsing the date field. This has been corrected. Note that this only occurs if the EDM Data Format setting is DD MMM YYYY. SNMPv3 collection failed with null pointer (ticket #25250) Data collection from a device using SNMPv3 occasionally failed, and investigation showed a null pointer in the log files. The code has been updated to handle this error more gracefully. Indicator view settings evaluated incorrectly in Spanish/German locale (ticket #25182) When running in a Spanish or German locale, the metric values for the indicator view were not evaluated properly, so the view was not displayed properly. This has been corrected. Event data from some connection types not displaying with SightlineDB When the data source type for a connection is empty, any associated event data was not displayed. This occurred only with the SightlineDB data reporsitory, and has been corrected. DCS upgrades fail on previously upgraded EDMs Upgrades of DCS may fail, due to a missing SightlineDB URL property. This was observed when EDM was originally installed with a pre-5.0 version and then upgraded to a pre-5.5.5 version. This has been corrected. Note that there are no issues when upgrading from a fresh install of EDM 5.5.5 to EDM 5.6.

Known Issues

Weekly time definitions may be offset for some locales It was observed on one EDM system that weekly time definitions were off by a week; for example, the Last Full Week display actually contained the current week’s data. Investigation revealed that the locale for the system was Germany. Changing the Week Start Day to Monday resolved the issue. Invalid email addresses can block delivery of alert emails When multiple email addresses are included in an alert definition, they must all be valid. If one or more of the email addresses is invalid then no emails will be received for the alert. This will be corrected in a future release. Connections do not always restart automatically after EDM upgrade Some EDM upgrades require that connections be restarted manually the first time. Note that they will be automatically restarted, as expected, after subsequent restarts of the EDM software.

EDM 5.6 (August 2018) New Features

Scheduled reports (ticket #23634) EDM now includes the ability to schedule reports, to automatically generated static reports based on a predefined schedule. As part of a report configuration, you can specify a schedule; at the scheduled time the report will be generated internally and saved as a PDF. View the resulting PDFs by clicking the new View Scheduled Reports icon on the Reports tab, or by navigating to http://<edminstance>:8080/reports in your browser.


Support aggregated results on history data (ticket #25006) Aggregation support has been added to summarized data. We now store minimum, maximum and sum values for each summary file definition. This will allow you to plot accurate sum values over longer periods of time, or be able to see the true min and max values over summarized data and longer time ranges. This capability is available only when SightlineDB is used as the data repository. Replace slider bar with new time selection The slider for time selection in the Schedules and TF Times to Download dialog boxes has been replaced with a new, easier-to-use time selection text box. Automated generation of OPC mapping files EDM now includes the ability to automatically generate mapping files from the Mapping Files screen. Only OPC mapping files are supported at this time. After supplying requested information, EDM queries the identified OPC server and generates the XML file based on that input. Note that the EDM UI will be unresponsive while the mapping file is being generated, which may take a few minutes. Mapping file generation will be moved to a background task in a future release of EDM. Centralized Schedule management A Schedules option has been added to the Settings menu to area in settings to manage schedules. Schedules can be created, edited and deleted from the Schedules display. This capability creates schedules at a global level to be used across Scheduled Reports, Archives and AutoRun options. When upgrading to EDM 5.6, all existing schedules will be migrated and maintained as global schedules; all existing schedules with the same name will point to the same schedule definition. New time definition type for previous 'n' datablocks You can now create a time definition based on previous ‘n’ data blocks. New Top List chart type (tickets #24457, #24973) A new Top List chart type has been added in this version of EDM, for use in Quick Charts and Reports. Top List charts are tabular charts that display array metrics with the array name as the column header and subscripts as rows. Top List charts can be used in conjunction with a new “last 1 datablock” time definition to show values for a single data block. Updated installation and upgrade scripts SightlineDB can now be optionally installed during DCS install/upgrades. Depending on the user selection for where to write performance data (tracefile only, SDB only, or both), the config.properties file will be updated appropriately. We also now automatically add other related tags for SightlineDB and trace file-to-SightlineDB migration into the config.properties file during upgrades for user convenience. Additionally, the answer file for silent/automated installs has changed. You can run java -jar DCS-installer.5.6.0.jar -options-template DCSAnswerFile.properties to generate a new answer file, with these additions: writeToSDB=XXXXX, installSDB=XXXXX, dcs.sightlinedb.url=XXXXXXX, and writeToTracefile=XXXX. Leave check boxes blank for false or enter true for true.


Changes

"Last Full Day" only includes 23 hours when summarizing by 1 hour (ticket #25147) When displaying a report with the “Last Full Day” time definition, only 23 points were included. This became more apparent when the data was exported to a CSV file. This has been corrected, and “Last Full Day” time definitions should be defined with 00:00:00 as both the begin time and end time. Update DCS upgrade procedure to install correct data repository (ticket #25130) With the introduction of SightlineDB, DCS installation and upgrade scripts have been updated to respect and preserve custom installation settings. When trace files are selected as the data repository, SightlineDB is no longer installed. DCS upgrade not working properly (ticket #25121) When upgrading a previous DCS installation, the old binaries were not replaced by the newer versions in the installation kit. This has been corrected. Event data of unrelated time is displayed on quick chart (ticket #25104) When selecting a time in a Quick Chart where event data did not exist, event data for an unrelated time point was displayed. This has been corrected, and the “No Event data available” message will be displayed. OPC Mapping file generator fails to map data if the type is FLOAT This has been corrected. Deleting event data from SightlineDB takes a long time When deleting a connection, the EDM UI seemed to hang in a loading state while deleting the event data from SightlineDB. The delete operation has been moved to a separate thread, and any errors are logged by DCS. No Event data will be displayed for summarized charts An update made in EDM 5.5 to display Event data for summarized charts had unintended consequences and has been rolled back in EDM 5.6. As a result, no Event data will be displayed when the data in a chart has been summarized. Timestamps for summarized datablocks now represent the beginning of the interval In previous versions of EDM, the timestamps for summarized datablocks written by EDM reflected the end of the interval. This has been changed for consistency with industry standards; the timestamp for summarized data blocks is now set to the beginning of the interval.

EDM 5.5.6 (July 2018) Changes

Migration aborts before completing (ticket #25143) In rare cases, DCS tried to flush data on an already-used http connection object, mainly during tracefile to SightlineDB migration but could also occur for an active connection. This caused a "stream is closed" exception, which would restart the affected active connection or trigger the migration as failed for the connection. This has been corrected.


Japanese characters not allowed in HostID Field (ticket #25138) After upgrading to EDM 5.5.5, Japanese characters are no longer accepted in the HostID field. This has been corrected. Zip file size increases continually when downloading all logs (ticket #25134) When downloading the EDM and DCS log files from the EDM UI, the size of the resulting zip file increased substantially on consecutive downloads. This was caused by incorrectly retrieving the DCS wrapper logs, and has been corrected. Duplicate setting in DCS config.properties (ticket #25123) After installing EDM 5.5.5, the user noticed that the dcs.db.migration.type entry appeared twice in the config.properties for DCS. This has been corrected, and no duplicate entries should now appear. SightlineDB stopped before DCS (ticket #25110) In the stop script, SightlineDB was shut down before DCS, which could cause exceptions in the DCS logs. This has been changed and we now stop DCS first. Cannot chart two array metrics with aggregation other than avg (ticket #25103) When charting multiple array metrics with aggregation other than avg, not all metrics were rendered in the chart. This has been corrected and you can now chart multiple metrics with different aggregations. Reassert email not sent for OPC connection alerts (ticket #25086) On a connection with a sub-second collection interval, the initial alert email was sent but the Reassert email was not. This has been corrected, and Reassert emails will now be handled correctly for alerts on data sources with sub-second collection intervals. No priority included in SNMP trap for dropped connection alert (ticket #25083) No priority was included in the SNMP trap for a dropped connection, although a priority was included in the SNMP trap sent for the cleared alert when the connection resumed. This has been corrected, and the dropped connection SNMP trap now contains a priority of 50. Changing the summarization for a chart did not work When requesting an interval larger than the auto value, large time ranges did not properly choose the summarized data set. This has been fixed.

EDM 5.5.5 (June 2018) Changes

Sightline migration utility now migrates live data and event data The trace file-to-SightlineDB migration utility will now migrate live trace files and event data, in addition to the summary files, for each connection. Contact your Sightline distributor for more information and assistance to migrate your EDM implementation from trace files to SightlineDB. SightlineDB upgrade The SightlineDB database has been upgraded from version 1.4.2 to version 1.5.2. The upgrade will be applied automatically for sites using SightlineDB for their data repository.


Not all data deleted from SightlineDB when a connection is deleted When deleting a connection from Sightline EDM, only the event data was deleted from SightlineDB but the metric data was not. This issue appeared after the schema update in EDM 5.5.0. This has been corrected. Correlation timeout increased The correlation timeout value is user-configurable, but the previous maximum value was 900 seconds. This has been increased, and the timeout range is now 1-86400 seconds (1 day). Add Event data info text (ticket #25080) A user observed that not all processes seemed to be listed in the Event data from a Linux Power Agent. We've added an info icon with explanatory text in the Event data popout window. Not all connections (data sources) have event data, resulting in an empty Event display. In addition, when the data source is a Sightline Power Agent, there may be filtering configured in the Power Agent to limit the number of event lines passed to EDM. Width of navigation pane cannot be changed (ticket #25078) The width of the left navigation pane became fixed and could not be changed. This has been corrected.


Updates to time system not dynamically applied (ticket #25051) Updates to time systems were not applied to alerts that were assigned to active connections. This has been corrected, and any updates to alerts and time systems will take effect immediately.

EDM 5.5.3 (April 2018) New Features

Import Host definitions from CSV file You can now import Host defintions from a CSV file, using EDM’s Bulk Load capability. This allows large implementations to quickly populate EDM with all of the host entries required to monitor the environment. In addition, sites that cannot use AutoDiscover on the network will benefit from this new functionality. See the Sightline EDM User’s Guide for details.

Changes

File connection fails when event data row ends with a null value (ticket #25048) Empty values at the end of the row for an event file (.EVT) being loaded into EDM would fail to load. This is now detected and handled gracefully; the data load will not fail and the value for any missing data items will be blank.


No array metrics included in correlation results when using SightlineDB (ticket #25047) Correlation on SightlineDB didn't show array metrics in the results, as they were being excluded incorrectly. This has been fixed. Constant browser refresh with EDM UI (ticket #23674) When a user with a timeout setting of 0 (never timeout) closed the browser without logging out of EDM, and then logged back in to the same browser, the window was constantly refreshed. This has been corrected. stopConnectionByID API method incorrectly returned true if no DCS was provided The stopConnectionByID API request requires both the connID as well as the dcsID in order for the connection to be stopped. If the dcsID was omitted from the request, the response incorrectly returned true, but the connection never stopped. This has been corrected, and the API method will now correctly return false. updateCloudwatchConnectionTemplate returns false every time The updateCloudwatchConnectionTemplate API method always returned false, even if it succeeded. This has been corrected.


getMetricData API call did not work for array metric (ticket #25038) The SOAP API getMetricData did not return data for the array metric’s subscripts. This has been corrected. REST API data retrieval did not work with relative time reference (ticket #25032) Relative time definition references in REST API calls have been enhanced. Additionally, the maxIntervals parameter will help with summarization intervals, and also ensure that SUM statistics are accurate. 1-click upgrade on Windows does not install EDM service (ticket #25027) When upgrading EDM on a Windows system using the 1-click installer, the old EDM service was removed but the new EDM service was not created. This has been corrected. 1-click upgrade on Windows deleted the DCS AccessKey After using the 1-click installer to upgrade EDM on a Windows server, the DCS AccessKey was blank. This has been corrected, and the DCS AccessKey entry will be retained. Updated wrapper EDM 5.2.2 includes version 3.5.35 of the wrapper.


EDM 5.5.1 (April 2018) New Features

REST API enhancements for additional aggregation (ticket #25007) EDM 5.5.1 includes updates to the data retrieval REST API to support specifying AVG, MIN, MAX, SUM and STDDEV for the types of aggregation that will be returned from the data request. Use the statType parameter to specify the aggregation type; if not specified then AVG will be used.

Changes

Unable to sort in Japanese (ticket #25025) When logged into EDM in Japanese, sorting on several pages did not work. This has been corrected.

EDM 5.5 (April 2018) New Features

Trace file-to-SightlineDB migration utility EDM 5.5 includes a migration utility to assist in moving from a Sightline EDM implementation using trace files to an EDM implementation with SightlineDB. The migration utility requires that you set up a second instance of EDM/DCS (all instances of DCS) and migrate existing summarized data into the SightlineDB repository. At the same time, all connections are established to write live data and event data into SightlineDB. Contact your Sightline distributor for more information and assistance to migrate your EDM implementation from trace files to SightlineDB. New SightlineDB schema A new schema has been introduced to SightlineDB in EDM 5.5; this is a change in the way data is stored. For current SightlineDB implementations, a migration of data is required into the new format for EDM 5.5 and above. This upgrade will be done automatically when EDM and DCS start up. Progress and errors will appear in DCS logs. As the data is successfully migrated, the old data is removed from the old format. You can backup your SightlineDB database before the upgrade by performing steps in the documentation for backing up the database. Summarized data supported for SightlineDB In previous releases, SightineDB maintained only the live data set for a connection, and no summary data was maintained. Now, any summarization defined in the connection’s configuration will be stored in the SightineDB database and made available for analysis and visualization. Data is migrated to new retention policy when retention policy is changed When using SightineDB as EDM’s data repository, changing the retention policy for a connection in previous EDM released caused the old data to be abandoned. This has been changed, and the data set for the connection is now migrated to the new retention policy. After updating the retention policy and restarting the connection, you must wait until a DCS-type alert is presented for the connection before referencing the data set or data loss may result.


New Scatter chart type (ticket #24917) A new scatter chart type has been added in this version of EDM. The scatter chart plots one metric against the others as a set of data points represented by dots. One metric is plotted on the y-axis and the remaining metrics are plotted on the x-axis. The scatter view makes the relationship between two metrics clear at a glance. New Indicator chart type (ticket #24546) A new indicator chart type has been added in this version of EDM. The indicator chart communicates the state of a metric or expression in respect to the caution and critical values defined for the them. The indicator view does not display specific values, but rather indicates whether a metric has crossed a threshold. New Stacked Column and Stacked Column 100 chart types Two new column charts have been added in this version of EDM. The stacked column chart shows multiple data series, one on top of the other, to show the relation between individual metric values and the total sum. The stacked column 100 chart is similar except that individual height of each metric is calculated as a percentage of the total sum. This allows you to compare individual contribution of data series to the total sum in percent. Enable time ranges within relative time settings In previous releases of EDM you could create a relative time setting, such as Today or Yesterday. In EDM 5.5 you can now create a time setting that contains a time range, such as Prime Shift, where the time setting is today from 8:30 am through 5:00 pm. Set first day of the week for weekly time settings You can now select the first day of the week when creating relative time settings for a week. This is a new global setting under System Settings.

Changes

Size-based retention policies no longer supported Size-based retention policies are being deprecated in EDM. You can no longer create a retention policy based on MB or number of data blocks, only time (days or months). Existing retention policies will be honored when the data repository is trace files, but connections will be blocked from starting when the data repository is SightlineDB, until the retention policy for the connection has been updated. Update visualization APIs to work with Dashboards (ticket #25002) Visualization APIs could create templates, but could not set the template to be used as a Dashboard. This has been corrected; visualization APIs have been updated to work with the Dashboard feature. Connection views not showing up if not public (ticket #25000) For users other than with EDM Admin role, connection views only are listed in the navigation pane if they are configured to be public views. This has been corrected. Reported values don't match the values reported by SNMP target (ticket #24984) In the SNMP agent-less data source, we have corrected an issue that was causing the rescanning of the SNMP device to be delayed if the collection interval was greater than 60 seconds.


Actions on Alert Cleared tab doesn’t include the Command option (ticket #24966) On the Alert configuration dialog box there's an Actions on Alert Triggered tab and Actions on Alert Cleared. The Command text box did not appear on the Action on Alert Cleared tab. This has been corrected. Charts not presented properly when printed to PDF (ticket #24904) When printing a report to a PDF, charts did not render correctly; they appeared only half as wide as they should be. Although the Print Preview window looked correct the resulting PDF was not. This has been corrected. In addition, charts could break across two pages when printed; this has been corrected and a chart will no longer span pages. Popped out reports not refreshing (ticket #24949) Multiple reports that were popped out and set to refresh every 5 minutes were not updating properly. This has been corrected. No Event data displayed when chart with Event data is summarized (ticket #24921) When a Quick Chart showing Event data was summarized, the Event data display did not include all of the events for the selected time point. This has been corrected. File connection fails when input CSV file has fewer than 10 data rows (ticket #24913) This has been corrected. Note that the file connection requires that the input CSV file have a minimum of 10 rows when the data repository for the connection is a trace file; when the data repository is SightlineDB there is no minimum number of rows. Forecast shows negative values but should not (ticket #24902) When viewing a forecast report there were negative values shown, but the Allow negative values checkbox was not enabled. This has been corrected. Correlation for millisecond data shows “No Results” (ticket #24900) When performing a correlation against millisecond data, the correlation results displayed “No Results.” This has been corrected. Millisecond Event data is not displayed (ticket #24898) After using a file connection to load Event data into EDM, the Event data could not be displayed. Investigation showed that the timestamp was not read correctly. This has been corrected. OPC connection fails after mapping file changes (ticket #24897) After adding new metric groups to the mapping file, an established OPC connection would no longer connect. This has been corrected. Issue forecasting OPC data (ticket #24842) When attempting to display the forecast report for an OPC connection, the user was returned to the EDM login page. This has been corrected. EDM UI tabs do not load for EDM Admin (ticket #24841) Unchecking a view's Public property was causing the EDM UI to hang on the loading stage for all main tabs for a user with EDM Admin privileges. Other users with different roles continued to work without any impact. This has been corrected.


Event data is not displayed (ticket #24828) When adding new fields to the CSV file (*.csv, *.evt) and loading data using the File connection in EDM 5.4.2, the Event data loaded in the past would not display. This has been corrected. Duplicate dynamic views created (ticket #24816) There was no constraint in the T_VIEWS table that prevents duplicate dynamic views from being created. This has been corrected; a database constraint has been added to prevent duplicate views. Expressions with aggregation cannot be charted (ticket #24782) When an expression with aggregation is included in a chart, and the aggregation is other than avg, the chart is displayed as “No Data Available.” This has been corrected. Note, however, that for min and max aggregations the aggregation level is applied to the underlying metrics before the expression is evaluated; this can produce unexpected results. Send to Host option not working for triggered alerts (ticket #24758) An alert was configured to send a message to the monitored ClearPath MCP host, but the message was not sent. This has been corrected. High system memory and DCS crash with 3-month correlation (ticket #24499) This has been corrected. Correlation now handles larger requests without causing memory issues. NaN error on AutoAlert definition with expressions (ticket #24463) When creating an alert based on an AutoValue, EDM calculates the alert value based on existing data for a specified reference metric. In previous releases this was not supported for expressions; this has been changed, and AutoValue will now produce a correct value when referencing an expression. Updated wrapper Wrapper is used by DCS for logging; an updated wrapper is included in this release. The new version of wrapper includes a fix for a memory issue as well as other updates. Exported report templates not importing correctly During testing, report templates exported from EDM 5.4.x did not import properly to EDM 5.5. This has been corrected. EDM now includes VMware alert groups by default on new installs Separate alert groups are included for ESX servers and VMware guests. Event data written incorrectly in SightlineDB When storing Event data in SightlineDB, spaces were preceded by a backslash. This has been corrected and Event data is now written correctly. Performance improvements writing Event data Performance improvements have been made when writing Event data to SightlineDB. EDM Admin passwords can no longer expire EDM Admin passwords should be exempt from the EDM password expiration setting, but were not. This has been corrected. Issues charting event data over long time ranges Very long response times were observed when displaying a chart for a long time range (several days or more) when the chart contains one or more Event data items. When the chart contained only event


data items a restart of the DCS could be required. This has been corrected and Event data retrieval has been made more efficient. ACE no longer supported The ACE feature is no longer supported in EDM. References to ACE and its configuration have been removed from the EDM UI. Expressions now included in AutoInvestigate results Expressions can now be included in the AutoInvestigate execution, and will be included in the AutoInvestigate results if the Merit value is high enough. Correlation can now be based on an expression Expressions can now be used as the independent metric in a correlation. In correlations initiated from a chart, expressions in the chart will be included in the drop-down list to select the independent metric. In correlations initiated from the Correlation icon, expressions can be selected from the metric list for the selected data source. Incorrect behavior with DCS restart icon In a multi-DCS environment, the restart DCS icon was only effective on the last DCS in the list, no matter which DCS was selected. This has been corrected.

Known Issues

On the Connections tab, sorting columns based on custom fields does not work Sorting on other columns on the Connections tab works as expected.

EDM 5.4.4 (February 2018) Changes

Private views with multiple users not handled properly (ticket #24989) When an EDM Admin created a private view and assigned several users, the view was not retrieved correctly from the database. This caused an incorrect presentation of the private view to the allowed users, as well as a performance degradation when loading the Connections tab. This has been corrected.

EDM 5.4.2 (September 2017) New Features

Event data support for File data source (ticket #24727) The File data source can now include Event data items. Event data is supplied via an .EVT file. The update necessitated a change in the architecture of the File data source; see the Sightline EDM User’s Guide, version 5.4.2, for more information. Support longer passwords In previous versions of EDM, only 20 character passwords were allowed. This has been changed and passwords can now contain up to 50 characters.


Active Directory Authentication EDM can use the site’s Active Directory entries to authenticate user logins. Optionally, AD entries that do not exist within EDM can be dynamically added. See the Sightline EDM User’s Guide for more information. Verbose API logging When using API calls there is minimal information logged in the edmadmin.log file. For debugging purposes an option has been added to log all EDM API related communication in a separate api.log file; every API call is logged, along with the remote source IP and all parameters passed to the API. Due to the volume of information recorded, this option should only be enabled for short periods of time. No restart of EDM or DCS is required to enable/disable verbose API logging.

Changes

Correlation displays “No Results” (ticket #24763) When a correlation was performed against an OPC data source with a summary interval of 15000 ms, no results were displayed. Analysis revealed that the DCS was setting the time at the end rather than the beginning of the collection process, resulting in irregular timestamps. This has been corrected. Incorrect display when chart summarization is set to several days (ticket #24765) When requesting a chart with 30 days as the summarization period, the output display was not correct because EDM only supported a summarization interval of up to 24 days. This has been corrected. Chart displaying reduced values with Sum across Data Sources (ticket #24794) A chart containing values from multiple data sources and the Sum across Data Sources option checked displayed reduced or zero values when refreshed. This has been corrected.

Known Issues

Event data is not deleted from SightlineDB when connection is deleted (ticket #24780) When deleting a connection from EDM, the data associated with the connection was deleted but not all of the associated event data. This will be corrected in the next version of EDM. Excessive response time charting event data for long time ranges Very long response times have been observed when displaying a chart for a long time range (several days or more) when the chart contains one or more Event data items. This chart can be either a Quick Chart or in a report. This will be addressed in the next release of EDM; Event data retrieval will be made more efficient. [Addressed in EDM 5.5]

EDM 5.4.1 (August 2017) Changes

Data is not deleted when connection is deleted (ticket #24780) When deleting a connection from EDM, the data associated with the connection was not deleted. This has been corrected.


Unable to edit template after upgrade (ticket #24777) Report templates with more than one instance of the same chart could not be updated. This has been corrected. Dynamic views updated via the EDM API causes duplicate entries (ticket #24773) Updating dynamic views from an external file using the EDM API created many duplicate entries. This has been corrected. Performance issues when loading a large number of connections Navigating EDM’s Host and Connections tabs with a very large number of connections (several thousand entries) was very slow. Performance improvements have been made to address this issue.

EDM 5.4 (July 2017) New Features

Export event data to CSV file (ticket #23754, 24502) The menu for event data tables (popped out from a Quick chart or report) now includes the Export to CSV option. When selected, the Event data in the selected display will be exported from EDM to a CSV file. Use the Event table settings to determine the amount of data to be included. Relative time definitions (ticket #24363) You can now create a time definition in EDM that refers to relative time periods; for instance, current day/week, last day or two days ago, last week, etc. Time definitions are added in the Settings > Time Definitions. Average across Data Sources (ticket #24447) A new setting has been added to the chart options called Avg across Data Sources. When checked, EDM will determine the average value of a metric across all selected data sources. The hostid will be displayed as AVG in the chart legend. Show summary interval at the chart level EDM now shows the connection and summary interval for each chart instead of at the report level. Click the info icon to see the display the list of data sources included in the chart and the summary interval for each one. Display dashboard processing time The time required to process the data requests for a dashboard is now included in the dashboard display. Support complex passwords In previous versions of EDM password strings were limited to letters and numbers. This has been changed, and you can now include most special characters in the EDM password.

Changes

Loading filter definition takes a very long time (ticket #24356) In very large environment, loading a filter definition took several minutes. Investigation showed that EDM was unnecessarily searching for the referenced connection and retrieving its metric list before


displaying the list of metrics in the filter. This has been modified, and the list of available metrics is no longer retrieved when displaying the contents of the filter. To edit the filter, identify a connection so that a metric list can be retrieved. Incorrect data block count when reading from file data source (ticket #24431) When reading data from a File data source, the data block count was not always correct. This was corrected for EDM implementations using the SightlineDB data repository in a previous release, and has now been corrected for trace file implementations. JMS stops writing to the database if it goes down (ticket #24559) This has been corrected. Database validation has been added to JMS to help recover when the database is restarted. Non-privileged users can edit a report's charts (ticket #24493) This has been corrected. The Edit Chart Options, Edit Time, Edit Metrics and Y Axis Options menu items have been suppressed for users with User role logins. Inconsistent timestamps between live and summarized data blocks (ticket #24549) The timestamp for live datablocks written by EDM represent the end of the interval, but when summarizing data the timestamp is the beginning of the interval. As a result, correlating live data items with summarized data produces invalid results. This has been changed, and the timestamp for both live and summarized data blocks now represents the end of the interval. Note that this change will result in the appearance of one missed data block in any summarized trace file when EDM is upgraded to version 5.4. For example, if you are storing 30-minute summary files and you upgrade EDM at 3:15 am, the last data block before the upgrade will be 2:30 (representing 2:30 to 3:00 am). The next data block, stored after the upgrade, will be at 3:30 (representing 3:00 to 3:30 am). The entire time range from 2:30 to 3:30 is included. This will occur only once for each summarized data repository. No connection views displayed for Analyst role (ticket #24642) When logging into EDM as an Analyst role user, the Connections tab is the first display. In some instances the view pane was blank until the user navigated away from and then returned to the Connections tab. This has been corrected. Slow response from Quick charts when selecting a data source (ticket #24643) In very large deployments of EDM, slow response time was observed when displaying the drop down to select a connection for a Quick chart. Enhancements have been made to improve this process. DCS Log4J scavenger inefficient (ticket #24644) A profiler running in DCS shows inefficiencies in the Log4J scavenger code. This has been corrected; refactoring has improved the performance of the log scavenger code. DateInFormat performance issue (ticket #24645) A minor performance issue was observed when loading reports. Investigation showed that it was related to the DateInFormat code. This has been corrected. Metric list disappears from Quick chart (ticket #24646) When navigating away from a Quick chart and then returning to it, the metric list was not always available in the drop down. This has been corrected.


Array based expression using IF condition not working (ticket #24647) Expressions using IF conditions with scalar metrics produced correct results, but when used with array metrics the results were incorrect. This has been corrected. Editing expressions is slow (ticket #24648) Users noticed that editing expressions seemed to take a long time. Performance improvements were made to remove unnecessary references to metric lists while editing the expression. DynamicView column shown in generated views (ticket # 24651) The DynamicView column was incorrectly included in generated views. This has been corrected, and the DynamicView column is no longer included when creating dynamic views. Quick charts take a long time to load (ticket # 24653) In some instances Quick charts took a long time to load. Performance improvements have been made to render Quick charts more efficiently. Expand event data display to use entire window (ticket #24654) The display in the Event Data window did not use the entire window, meaning that not all event data was displayed. This has been corrected. OPC mapping files not processing Boolean data type Mapping files for OPC data connections did not properly process Boolean type metrics. This has been corrected. Opening the Configure All pop-up on a report is slow (ticket # 24658) Displaying the Configure All pop-up from a report could take several seconds. Performance improvements have been made to improve the display time. No Event data shown in Quick Chart (ticket #24693) Expected Event data was not displaying in a Quick Chart, due to time zone differences. This has been corrected. Too many timestamps on x-axis When displaying charts containing metrics from data sources with different intervals, there were sometimes too many timestamps on the x-axis. This has been corrected. Default value for y-axis no longer zero The default value for multiple y-axis settings is now auto instead of zero. In addition, negative minimum values can be entered when updating settings in the Y Axis Options dialog box. Changed behavior for browser Back button In previous releases of EDM, clicking the browser's Back button exited the user from EDM. This has been changed and clicking the browser's Back button will now navigate to EDM's Home page. Max Metrics setting removed from Chart Settings In previous releases of EDM, the Chart Settings > Max Metrics per chart setting limited the number of metrics that could be displayed in chart, which sometimes led to confusion when displaying array metrics. The Max Metrics setting has been removed and there is now no limit to the number of metrics that can be included in a chart. Keep in mind that an excessive number of metrics in a chart can affect the data retrieval and chart render time.


Support relative time ranges on API calls API calls can now include an optional refTime variable that refers to an existing time definition in EDM; for example, refTime = Last 3 hours.

Known Issues

EDM and DCS services do not start on Redhat 7.2 systems A Redhat 7.2 operating system bug prevents traditional services, which are symlinks, from starting. This affects the EDM and DCS services. Redhat has patched this in 7.3, and the problem is no longer an issue. A workaround is to copy the EDM and DCS startup script into /etc/init.d directly, or update to systemd-219-19.el7_2.4 package, which fixes the issue.

EDM 5.3.3 (June 2017) New Features

Add Sum column to Statistics chart The Statistics chart now contains a Sum column, in addition to the previous Mean, Min, Max and Std Deviation columns. This value is the sum of all data values for the time range of the chart.

Changes

Slow license evaluation on connection start (ticket # 24652) When starting a connection, EDM checks the license settings before allowing the connection to proceed. On the Connections tab, the EDM screen can lock and display the blue "Loading" bar for a long time, preventing the user from doing anything else within EDM. This has been corrected; the license check has been optimized for performance and will no longer lock the EDM UI. Certain negative values not inserted into SightlineDB database The values -1, -2 and -3 were not inserted correctly in the SightlineDB database. This has been corrected. Enhancements to API methods (ticket # 24624) EDM 5.3.2 contained new API methods to provide better performance. Some API methods have also been enhanced in this release.


Event data files continue to grow (ticket # 24672) While investigating an issue with low disk space, it was discovered that the EDM event files were consuming ever-increasing amounts of disk space. Investigation showed that they were not wrapping as expected. This has been corrected, and the event data files will again roll over in sync with the related trace file retention.


Additional logging for File data source (ticket # 24634) Additional logging and minor error handling updates have been made for the File data source. New API methods (ticket # 24624) EDM 5.3.2 contains new API methods to provide better performance. All previous API methods remain, for backward compatibility. Exporting Event data to CSV file (ticket # 23754) Backslashes were not handled correctly when exporting Event data. This has been corrected. OPC connections randomly disconnect Due to timing issues, OPC connections randomly attempted to connect multiple times simultaneously. This has been corrected.

EDM 5.3 (May 2017) New Features

REST API for data retrieval (ticket #24338) Restful API calls for getMetricData are now supported for data retrieval from EDM. See the Sightline EDM User’s Guide for more information. Export event data to CSV file (ticket #23754) The menu for event data displays now includes the Export to CSV option. When selected, the Event data in the selected display will be exported from EDM to a CSV file. This option applies to popped out Event data displays as well as Quick Charts and Event tables within reports. Suppress negative values in forecast results (ticket #24544) Negative vales were reported in forecast results; in some instances this is valid, but not always. A checkbox has been added on the forecast definition page to allow negative values in forecast results. When not specified, negative values will be reported as zero.

Changes

Updated Japanese translations (ticket #24465) Several menu items have been translated, or existing translations updated, in the EDM UI. Deleting a connection deletes the connection template when the template includes a schedule A connection template was created with both Run at Startup checked and a schedule specified. The template was assigned to a connection, and the connection was subsequently deleted, causing the template to be deleted. This was also happening if the template was the default template. This has been corrected. Support for MySQL 5.7 This version of EDM includes support for MySQL 5.7.x. Display dashboard processing time Dashboard processing time is now included in the dashboard display.



Browser memory leak when displaying large reports The browser page is now refreshed when navigating away from a dashboard or a report, which releases the memory. Refactor VMware discovery When scanning for VMware guest updates, EDM checked all hosts to determine whether they were a VMware server. The code has been refactored to query in advance for only VMware hosts, which will reduce the number of calls to EDM’s admin database and improve performance. VMware connections not restarting after retention policy update The retention policy for a VMware connection was updated, and the connection appeared to restart successfully but no data was stored in the SightlineDB repository. This has been corrected, and VMware connections restart properly after retention policy changes. Keep in mind that changing a retention policy with SightineDB causes a new data set to be started for the connection. Refactor EDM login process In large environments the EDM login process could take several seconds. Unnecessary database calls have been removed, and the login process is now noticeably faster. EDM stops writing to SightlineDB In rare cases, an error would cause all writes to SightlineDB to stop, and not continue until DCS was restarted. This has been fixed. Max Intervals setting should only apply to charting The Max Intervals setting was being used for all data requests, occasionally causing unexpected results for correlation and forecasting. The Max Intervals setting now only applies to Quick Charts, reports and dashboards. Correlation and forecasting use the user supplied summarization level.


Browser memory leak fixes reverted Updates made in EDM 5.2.1 to release browser memory after displaying charts or reports had unintended consequences in large farms. These fixes have been reverted.


Garbled message in email alert (ticket # 24536) Alert emails were not properly displaying Japanese characters. This has been corrected.


SNMP v1 is missing in the Connection template as an option (tickets # 24533 and #24471) SNMPv1 is now a supported SNMP version for data collection. This option is listed in the SNMP type drop down in Connection templates and in Connection detail displays. Browser memory leak Updates have been made to release memory from the browser after displaying charts or reports. Quick charts with event data and a custom time range displayed the last hour of data This behavior has been corrected, and the custom time range is now used. Stacked Bar 100 charts not refreshing as expected This has been corrected. The file_data folder was not being created during DCS install This has been changed. The DCS installation routine now creates the folder by default.

EDM 5.2.0 (March 2017) New Features

SightlineOPCServer This release includes the new SightlineOPCServer. Enable Configure All for userids with User role (ticket #24467) Users logged into EDM with the User role can now make temporary changes to displayed reports using the Configure All capability. Changes to reports using Configure All are not persisted to the report after it is closed. Updated documentation for Retention Policies The EDM User’s Guide has been updated to contain more detailed explanations regarding how retention policies are applied and evaluated, especially when SightlineDB is used as the data repository. Rather than defining the amount of data that will be stored for a connection, no data will be retained that is older than the number of days specified in the connection’s retention policy.

Changes

Starting Correlation after zoom uses the wrong start and end times (ticket #24541) After displaying a chart and then zooming in to display a smaller time range, the user initiated a correlation. The time range in the Correlate dialog box referenced the original chart, not the time range after zooming in. This has been corrected, and starting a Correlate from a chart will use the time range on display. Save connection for event table display when report loads (ticket #24507) When several instances of an event table were included in a report so that each would display data from a different connection, the connections to be displayed were not saved; when the report was initially displayed all event tables displayed information from the same connection. This has been fixed and the specified connection for each event table is now saved correctly.


Password settings incorrectly enforced Although not activated in System Settings, password validation rules were applied to password update attempts. This behavior has been corrected and no password validation will be applied unless specifically enabled. Switching chart type after zoom returns to the original time range This has been corrected. Interval for file connections incorrect The value for the Interval metric for file connections was not properly determined when the file was processed. This has been corrected. The units for the Interval metric in file datasource is seconds for tracefile, and milliseconds for SightlineDB.

Known Issues

Unpredictible behavior with bar charts and column charts Time range not always correctly displayed and number of bars/columns incorrect. This will be corrected in the next release.

EDM 5.1.5 (March 2017) Changes

Chart menu items not fully translated Several new chart types have been added to EDM in recent releases, but the chart types in the chart menu were not all translated. This has been corrected. Correlation not detected when data sources have different intervals (ticket #23129) When correlating a metric across data sources with different intervals, correlation results were not correct. The minimum aggregation interval, used by the correlation process, should be the least common multiple of the selected data sources' intervals. This has been corrected. Issue charting expressions when underlying data was absent (ticket #23937) When including an expression in a chart, the expression disappeared if any of the referenced metrics were not available for even a single data point. This has been corrected. Expressions will be charted for any data point where all of the referenced metrics are available. Stacked Area charts not displaying all plot points in dashboard roll-up (ticket #24312) When the metrics being charted contained N/A values at different time points, the stacked area chart showed gaps. This has been corrected. Don’t load dashboards or reports when logging into EDM (ticket #24453) If a browser window is refreshed while EDM is running a dashboard or report, the refreshed window tried to re-run the display before allowing the user to perform any other action in EDM. This has been corrected, and the user is now taken to the EDM Home tab.


NaN error on AutoAlert definition using SightlineDB with expressions (ticket #24480) When creating an alert based on an AutoValue, EDM calculates the alert value based on existing data for a specified reference metric. Note that AutoValue is not supported when configuring an alert for an expression, and the alert value will return 0.0 in this instance. Aggregation naming (min, max, sum) conflicts with Cloudwatch datasource metric names (ticket #24490) Some Cloudwatch metric names contain 'min' or 'max' etc. As a result, when these metrics are plotted no data is displayed and the metric names all have the red 'X' in the chart legend. This has been corrected.

Known Issues

Dashboards cause JVM to run out of memory when rendering large dashboards (ticket #24453) Dashboards containing thousands of charts may cause JVM to run out of memory. Deleting a connection deletes the connection template when the template includes a schedule A connection template was created with both Run at Startup checked and a schedule specified. The template was assigned to a connection, and the connection was subsequently deleted, causing the template to be deleted. This can happen if the template is the default template. To avoid this error, do not specify a schedule in any connection template. [Corrected in EDM 5.3.]

EDM 5.1.0 (February 2017) New Features

New candlestick chart type A new candlestick chart type has been added in this version of EDM. Candlestick charts show the min, max and average values for a metric over a summarized interval. New UI for retention policies Retention policy handling has been changed in EDM 5.1. There is now a specific set of retention policies for live data, and each connection and connection template must use one of them. EDM has several default retention policies, and site-specific retention policies can be created on the Settings > Retention Policies page. When creating a connection template or updating an individual connection you will see the list of defined retention policies. Support for Metric Group names in the File data source File support now includes the ability to specify Metric Groups for usability. To create a Metric Group simply include the name of the Metric Group as part of the Metric Name in the column header and then separate them with three dashes ("---"). For example, you could create a metric group to contain all Fan metrics; to include the “Fan Speed” metric in the group use the column header "Fan---Fan Speed". Refer to the EDM User’s Guide, Chapter 36, Using the File Data Source, for details.

Changes

Report Chart timestamps are inconsistent after 30 second refresh (ticket #24417) After displaying a chart and setting the refresh rate, the time range was not always updated properly when new data blocks arrived. This has been corrected.


Data gaps when charting from file data source connection (ticket #24431) When charting data from a File data source, occasional gaps appeared in the data. This has been corrected. Incorrect data block count when reading from file data source (ticket #24431) When reading data from a File data source, the data block count was sometimes off by 1. This has been corrected for EDM implementations using the SightlineDB data repository, and will be corrected for trace file implementations in a future release. Charts showing blank gaps on the right side after refresh (ticket #24435) When refreshing a report, some charts were rendered with a blank gap on the right side of the chart, particularly when charting data from data sources that are behind the current DCS time but being actively collected. Additionally, some charts did not refresh after the first refresh occurred. These refresh issues have been fixed. File connection data value specification (ticket #24438) In the initial release of the File data source, data read from the input CSV file was displayed as is. This was inadvertently changed in EDM 5.0.2, and the input values were divided by 1000 before being displayed. This has been corrected, and input values are again displayed and manipulated in the same granularity that they are supplied in the input file. NaN error on AutoAlert definition using SightlineDB (ticket #24463) When creating an alert based on an AutoValue, EDM calculates the alert value based on existing data for a specified reference metric. When using SightlineDB the AutoAlert values returned NaN (Not a Number). This is now fixed. Note, however, that AutoValue is not supported when configuring an alert for an expression. AutoInvestigate results do not reflect selected date format (ticket #24464) After executing an AutoInvestigate, the timestamps in the results display did not reflect the requested format of YYYY/MM/DD. This has been corrected, and AutoInvestigate results now use the selected date format. Rounding precision from file data source (ticket #24470) Values from the File data source were sometimes rounded incorrectly; for example, displaying 4.06 as 4.059. This has been corrected. Charts not refreshing when aggregated values are displayed (ticket #24472) When aggregated values (min, max, sum) were included in a chart definition, refreshing the chart or report did not work. This has been corrected. Back and forward buttons not working for event chart tables in reports In Event tables rendered within reports the back and forward buttons did not work to move between data points. This has been corrected. Incorrect y-axis values with meter charts When rendering a meter chart, values on the y-axis incorrectly included timestamps. This has been corrected.


Connections in a remote SightlineDB instance are unstable until all historical data is downloaded When EDM first tried to connect to all discovered hosts, and was using a remote SightlineDB instance, the connections went repeatedly up and down until all historical data was downloaded. Once the data was downloaded, all connections became stable. This has been addressed.

Known Issues

Connections will not resume automatically after upgrade to EDM 5.1 After the DCS upgrade to EDM 5.1, connections will not resume automatically because the structure that is saved to disk and used to resume connections has been changed. As a result, DCS cannot read the previous version of the file. Connections will need to be connected manually after the upgrade. Timestamps for event charts not always correct When charting event data, the start and end time are not always correct when the chart is initially rendered. With the first refresh, the timestamps are corrected. This will be fixed in the next release. Correlation cannot be based on an Event metric Event metrics cannot be used as the independent metric in a correlation. This will be addressed in a future release. Correlation cannot be based on an expression Expressions cannot be used as the independent metric in a correlation. This will be addressed in a future release. [Changed in EDM 5.5.] Expressions not included in AutoInvestigate results Expressions are not included in the AutoInvestigate execution, and are not included in the AutoInvestigate results. This will be addressed in a future release. [Changed in EDM 5.5.] Charts containing metrics with duplicate HostIDs do not refresh correctly When a chart contains the same metric from multiple connections, and one or more connections have the same HostID, the chart may not update correctly. This will be fixed in the next release.

EDM 5.0.0 (December 2016) New Features

SightlineDB repository for storing performance data EDM 5.0 includes SightlineDB for storing performance data. SightlineDB provides fast and efficient data storage for large amounts of data, and utilizes a fraction of the disk space required for trace files. Note that the data repository is configured per DCS instance; that is, each DCS will write to either SightlineDB or trace files, but not both. AutoInvestigate AutoInvestigate examines each metric in a connection’s data repository and determines at which intgerval its most abnormal behavior occurred. Use AutoInvestigate to determine which metrics and time periods need more in-depth analysis. AutoInvestigate is supported only when SightlineDB is used as the performance data repostitory.


New histogram chart type When creating a Quick Chart or a chart definition there is a new option in the chart type drop down called Histogram. Histogram charts group numeric data into buckets, to depict the distribution of the metric’s data; that is, how often values fall into ranges. All buckets are equal width in the chart, and have a height proportional to the number of data points in the bucket. New statistics chart type In previous versions of EDM the statistics chart was available only as a pop out window. Statistics is now an option when creating a Quick Chart or a chart definition, so that the statistics chart can be persisted in a report. Enhanced chart options Charting options have been enhanced in EDM 5.0. In addition, options are now available from a single chart-specific menu, including: - User defined summarization levels - Support for multiple Y-axis Chart metrics from multiple data sources in a Quick Chart (ticket #23429, #23689) EDM now provides the ability to include metrics from multiple data sources in a Quick Chart. Change a chart’s configuration regardless of where the chart was launched (ticket #23632) Clicking on a data source name in the Connections tab launches an overview report for the selected connection. The new chart-specific menu is included in this display, so charts can be updated without having to re-render the report form the Visualization > Reports tab. Launch correlation from any chart (ticket #23779) The Correlate menu option has been added to the chart context menu, so that a correlation can be initiated from most charts. Clicking the Correlate menu item displays the Correlation dialog box, which retain several settings from the chart, such as the time range and displayed metrics. This enhancement makes it very easy to initiate a correlation. Save as Chart and Save as Report options available from most pop out charts Previous version of EDM included the ability to save a Quick Chart directly to a chart or report definition. This capability has been expanded to most popout charts within EDM, for instance, alert pop outs or charts popped out from a report. Create alerts from charts The Add Alert menu option has been added to the chart context menu, so that an alert definition can be added to an Alert Group (or a new Alert Group created) based on the metrics available in a chart. Shade plot points where alerts are firing When popping out a chart from the Alerts page, the chart is now shaded for all data points that violate the threshold value. Chart multiple metrics from correlation results It is now possible to add multiple metrics to a correlation result using the new correlation interface. This allows comparison between multiple data points without having to re-run another correlation.


User-defined date format The default date format used throughout EDM has now been made configurable to the user. The user defined date format will be applied to all areas of EDM that display a date. This configuration is located in the system settings menu.

Changes

Missing data for disk subscripts on VMware connections Investigation shows that trailing backslashes in the disk subscripts caused missing data. This affected VMware connections only. The trailing backslashes have been removed; however, any user-defined alerts or charts that reference the subscript directly will need to be updated (if the alert or chart references "All" subscripts then it will not be affected).

Stacked area chart not displaying all data points (ticket #24312) When the metrics being charted contained N/A values at different time points, the stacked area chart showed gaps. This has been corrected.

Known Issues

Connections in a remote SightlineDB instance are unstable until all historical data is downloaded When EDM first tries to connect to all discovered hosts, and is using a remote SightlineDB instance, the connections will repeatedly go up and down until all historical data has been downloaded. Once the data has been downloaded, all connections will be stable. This issue does not affect EDM running with a local instance of SightlineDB. [Fixed in EDM 5.0.1.] Incorrect y-axis values with meter charts When rendering a meter chart, the values on the y-axis incorrectly includes timestamps. This will be corrected in the next release of EDM. [Fixed in EDM 5.1.] AccessKey updates not immediately reflected in EDM UI When entering multiple AccessKey strings in the System Settings > AccessKey section, AccessKeys become immediately effective after clicking Save. However, the connection counts are updated only for the first entry until you click Save once for each entry, or if you navigate away from the page and back to it. This will be corrected in a future release. Note that this is a UI issue only. Only one SNMP connection can be configured per host Configuring more than one SNMP connection on a host produces issues with the Symbol Table. This will be corrected in a future release. Expressions not supported as independent metric for AutoCorrelate when using SightlineDB An expression cannot be specified as the independent metric when initiating an AutoCorrelate on a connection stored in SightlineDB as the repository. This will be changed in a future release. [included in EDM 5.5] Summarization not supported for SightlineDB Data summarization is not supported for DCS instances where performance data is stored in the SightlineDB repository. As a result, we recommend increasing the retention policy of the live data to accommodate storing longer time ranges, for historical data retrieval, examining past periods and forecasting. This will be addressed in future releases. [Retention policies introduced in EDM 5.1.]


Back and forward buttons not working for event chart tables in reports In EDM 5.0 event tables render in reports and are updated with new events when the report is refreshed. However the back and forward buttons do not work in chart tables within reports. This will be corrected in the next release. Sorting intermittently fails on many tables in the EDM UI This will be corrected in a future release. AutoDiscover for SNMP connections must be performed last When using AutoDiscover to add SNMP data sources to EDM, the AutoDiscover for SNMP should be initiated after all other AutoDiscover processes have completed. If you AutoDiscover the SNMP connections first, subsequent AutoDiscover processes for TLC, VMware and Cloudwatch connections will be extremely delayed. This will be corrected in the next release. Note that you can always manually configure hosts and connections in EDM.

Sightline Enterprise Data Manager (EDM) Software Release Notes · 2019. 6. 6. · These release...

Documents

Transcript of Sightline Enterprise Data Manager (EDM) Software Release Notes · 2019. 6. 6. · These release...