Beta Release
This is a Beta release to preview new functionality coming in Gibraltar 3.0. Full
documentation is not available for new features and some aspects of the API may
change before final release. This release will be supported for a limited period
of time.
Upgrade Can't be Rolled Back
Once you have run the Analyst in this release it will upgrade your repository to a new
standard that can't be converted back to the Gibraltar 2.x format. Contact Gibraltar Support
if you need to roll back for a discussion of options that can preserve your log data.
Prerequisites
Before installing Gibraltar, you need to have .NET 4.0 or later installed.
If .NET 4.0 is not installed you will be prompted to before setup can continue.
Compatibility Notes
This is a beta release that has minor API changes from the last official release. Additionally, its API is still
in the process of being defined so further changes can be expected to break compatibility between this version
and the final release of 3.0.
New Features In This Release
New features in the Hub and Agent are not being covered as neither should be used at this time.
Analyst Scalability
A number of updates have been done to improve the ability to use Analyst with larger sessions and more sessions. This includes:
- 64-Bit support: If you're running a 64-bit operating system Analyst will now run in 64-bit to let you take advantage of all the
RAM you can muster.
- Analysis safety limit: Analyst won't attempt to perform background analysis on sessions that might require more memory than is
available.
- Refresh suppression: As your repository gets more sessions in it, refreshing data gets more time consuming. Analyst
detects this and suppresse most automatic refresh of repository data when the expected duration is too high.
Hub Synchronization Options
You can now configure if you want Analyst to automatically download all session data (previously the only option), just download session summaries or not
download anything until prompted. When set to just download session summaries the session detail will be automatically retrieved if you open a session to
view it. This can tremendously reduce the disk space and time required to get in sync with the hub. This configuration option is under the new
Server menu.
Metric Graphing
Session metric graphing has been rewritten to offer similar capabilities to metric charting. You can now:
- Customize metric grouping and display: You can change the default grouping of metrics by unit to your own grouping. Additional
graph types such as area, stacked area, and full stacked area are supported to facilitate viewing how sets of metrics contribute together to a total in
absolte and percentage terms.
- Edit graphed metrics: Once you've added a metric to the graph you can edit its configuration.
- Easy export to PNG: In addition to a full featured printing feature for graphs you can do a one-button export to PNG to quickly get an
image of a graph.
Support for MONO
The Agent in this release has been verified to work under some versions of MONO (2.4.2 and later) on Linux. It may work for other versions of MONO and
on other operating systems. The final release of 3.0 is expected to work with MONO 2.4.2 and later under Linux and MacOS.
Defects Fixed In This Release
This is the list of issues fixed since the last release version (2.5.2.815)
Agent
- Fixed: Packager utility will not crash when presented with bad input, it writes a message to the console instead.
- Fixed: Gibraltar Agent for PostSharp doesn't set a default event metric value.
- Fixed: Gibraltar Agent for PostSharp is not thread safe when calculating timing for methods that may be invoked concurrently.
- Fixed: Gibraltar Agent for PostSharp GFeature treats EnableSourceLookup exactly backwards when set.
Analyst
- Fixed: AddIns can't access metric samples because they don't implement the correct interfaces.
Hub
- Fixed: Updated session data isn't available if the session was already read by an Analyst due to a problem with the file cache.
- Fixed: If a request times out while waiting on an internal lock it may cause all subsequent requests to timeout.