Gibraltar 2.5.1 is a maintenance update to resolve issues found in Gibraltar 2.5.

New Features In This Release

Agent Auto Send on Exit

When Hub server auto send is enabled the agent will automatically submit the session on exit if possible.  This eliminates the need to manually set the SendSessionsOnExit option to get the session immediately.

AddIns Can Access Metric Data

The AddIn API has been extended to expose all of the metric data available in each session along with the log messages.  This data is available in both raw and analyzed form, allowing add ins to replicate the various Metric displays and perform other metric-related tasks.

Support for NLog 2

While NLog 2.0 is still in beta the Gibraltar Agent for NLog has been updated to work with the latest builds.  For more information see Third Party Integration - Using NLog with Gibraltar.

User Opt In / Out

Windows applications (WinForms and WPF) can now use a built in feature for users to opt in & out of sending data automatically to the Hub.  This is configured with the AutoSendConsentConfiguration Class.  For more information see Reference - User Opt In.

Hub Upload Performance

New optimizations have been added to Hub to improve performance over fast network connections, dramatically increasing the speed that large sessions can be uploaded over a fast network.  This was done without sacrificing the efficiency and throttling requirements for low bandwidth connections.

Hub Storage

Previously, the hub cached a compressed copy of a session if it was ever downloaded in compressed form (which is the default for newer versions of Analyst).  This could cause the repository to use up to 175% as much space on disk as the data storage limit configured by the administrator.  In this release the Hub uses a dynamic cache that drops data more quickly and will generally not exceed 2GB regardless of the size of the repository.

Defects Fixed In This Release

This is the list of issues fixed since the last release version (2.5.0.748)

Agent

• Fixed: Process-related performance counters aren't collected under .NET 4.0 on certain operating systems when the primary UI culture is not set to english and the selected culture alternate language pack is installed. 
• Fixed: Hub session transfers don't restart after a higher level protocol error in the transfer.
• Fixed: Agent can slow down service start on OS startup due to dependency on WMI.
• Fixed: Exceptions while packaging will get recorded into the client log.
• Fixed: Extended memory performance counters can't be enabled through configuration files.
• Fixed: Agent refuses to utilize auto send to the hub if a later version of the agent or Analyst has been used locally.
• Fixed: Packager class does not add file extension as documentation indicates it will.
• Fixed: Packager class now throws clear exceptions for common bad input scenarios as documented.

Analyst

• Fixed: New Metric Chart Dialog will not enable the OK button immediately when starting with a metric that has only one numeric column.
• Fixed: New Metric Chart Dialog can throw exception during reconfiguration when switching the argument from a numeric to a non-numeric column and a topping function is configured.
• Fixed: Metric Graph doesn't correctly summarize event metric data when the dataset has no samples for a time interval.  Instead, it drops the time interval.
• Fixed: The current log message selection is lost when switching between log message views.
• Fixed: Folders in the repository view are not reliably sorted in alphabetical order, often being instead shown in the order they were added.
• Fixed: The repository view filter dropdown list incorrectly applies a filter when transitioning from one item to multiple items causing user confusion.
• Fixed: The repository view sessions grid scrolls the current selection to the top row unnecessarily when refreshing, hiding new sessions that show up above the selection.
• Fixed: Add Ins that fail to initialize can cause context menus to not display.

Hub

• Fixed: Pop3 client crashes the Team Service when an error occurs during the low level TCP transfer.
• Fixed: Pop3 client logs excessively while checking mailboxes.
• Fixed: Team Server Service doesn't reliably start on OS startup, often timing out.
• Fixed: When Team Service is left stopped and restarted after a significant number of sessions have been received it can consume a significant amount of memory while attempting to work through the backlog.
• Fixed: Team Server locks the repository while analyzing sessions, causing client (Agent and Analyst) errors interacting with the Hub.
• Fixed: Missing files (typically due to them being manually removed from the repository) prevents maintenance from completing.
• Fixed: Server Administrator can't configure repository size limit to a value greater than 2GB.
• Fixed: Server repository can take up to 2x the expected disk space even for very large repository limits.
• Fixed: Calculating statistics for hub usage can take an unreasonable amount of time for larger repositories.
• Fixed: If multiple clients connect for the first time to a hub with a large number of sessions the web site may consume an excessive amount of memory.