Sightline EDM 7.2.1: Move Your Trace File History Into SightlineDB

Every EDM release sharpens the same promise: one trustworthy view of your infrastructure, without asking you to choose between where your data lives and how easily you can get to it. Version 7.2.1 delivers on that with a guided way to bring trace file history into SightlineDB, plus a set of installation, stability, and security improvements drawn from real customer feedback.

Trace File to SightlineDB Migration, One Connection at a Time

If your site still keeps performance data in trace files, EDM 7.2.1 gives you a controlled path into SightlineDB, without disrupting live collection while you move.

From the new Migration Status tab under Connections, you can:

• Preview the plan first. Show Migration Plan lists each tier (live and event data, and every summary level) with its source size, time span, retention policy, and SightlineDB availability, before you commit to anything.
• Migrate only what’s missing. Each phase compares the trace file’s time span against what SightlineDB already holds and fills in the gaps at either end, so you’re not re-migrating data that’s already there.
• Verify with a downloadable report. Every migration is checked for completeness. The report leads with a clear verdict, flags any gaps alongside the recommended action, and can be downloaded for your records or shared with Sightline Technical Support.
• Confirm before you switch. The read source is selectable per connection (trace file, SightlineDB, or the Data Collector default), so you can migrate, check the data in a Quick Chart, and only then move that connection’s reads over. Migration never changes your read source on its own.
• Reclaim disk space on your terms. Once a connection’s migration is complete and verified, a Delete source tracefile action removes the original trace files. This is always something you initiate; EDM never deletes source trace files automatically.

For the full procedure, see Migrating Trace File Data to SightlineDB in the Sightline EDM User’s Guide. We recommend looping in your Sightline representative before a large migration.

A Clearer View Across Every Connection

The new Migration Status view on the Connections tab shows migration state for every connection in one place, including how much data has already moved to SightlineDB, current lag, retention policy, read source, and throughput, with filtering, sorting, and an explicit refresh.

Repository mode is also easier to manage. EDM Administrators can now set the Data Collector Service’s write and read modes directly from Settings > Data Collectors, no more hand-editing config.properties to stage a migration or cut over once it’s verified.

Smaller Wins Worth Noting

• Retention policies can now be renamed without breaking existing queries or reports; access under the old name is preserved.
• The SightlineDB 1.7 to 2.8 upgrade free-space requirement has been corrected. Budget the size of your existing SightlineDB 1.7 data plus 1 GB, not double that figure as previously published.
• Non-default SightlineDB install locations are now detected correctly during upgrades, including drives other than C: and data paths with no drive letter.
• Configuration files are merged, not overwritten, on upgrade, so new settings in config.properties, quartz.properties, and eventExcludeList.properties show up alongside your existing setup instead of replacing it.

Under the Hood

This release also resolves a set of defects reported from the field: EDM now listens on all network interfaces after upgrade, service start and stop behavior has been hardened, and unused libcurl and StackBuilder components have been removed from the bundled PostgreSQL install on Windows to close out flagged vulnerabilities. Security updates include BouncyCastle 1.84, Jackson 2.18.8, and OmniFaces 4.7.5, along with a new X-Frame-Options response header.

Ready for the deep dive? View the full EDM 7.2.1 Release Notes here for the complete list of new features, changes, and known issues.