Releases: Particular/ServicePulse
1.3.2
As part of this release we had 2 commits.
This is a hot fix for a bug introduced as part of release 1.3.1 It causes an error that would show if you attempted to retry messages.
What should you do?
If you have an earlier version of ServicePulse installed make sure you update to this version (1.3.2)
Where to get it
You can download this release from our website
1.3.1
1.3.0
As part of this release we had 43 commits which resulted in 5 issues being closed.
Features
-
#194 Improved the readability of failed messages group titles
Group titles were truncated with ellipses i.e. Company.Namespace.Exception.Type.Big.Long.Group.Title.Na... Making it difficult to determine the difference between groups.
We dropped the ellipses preferring to do a hard wrap so the entire content of the group title is visible. This makes the experience better for desktop users.
-
#188 Information messages confirming actions are now represented as in-place animations
When we introduced the failed messages grouping functionality, we noticed that the way we had been presenting action confirmations filled the screen in an annoying way. So we took the confirmations that seemed to be noisy and replaced them with interactions and animations where you are doing your work.
Where to get it
You can download this release from our website
1.2.1
As part of this release we had 2 commits which resulted in 1 issue being closed.
Bug
- #187 Font-Awesome not working in ServicePulse 1.2 on IE
Symptoms
Font-Awesome not working in ServicePulse 1.2 on IE
Who is affected
Users of Internet Explorer
Where to get it
You can download this release from our website
1.2.0
As part of this release we had 81 commits which resulted in 12 issues being closed.
Improvements
#177 Failed messages are now grouped by exception type and failed line of code
When a Failed Message is detected it is bundled into a group based on the type of Exception that was thrown and the method in the source code that it was thrown from.
All of the messages with a Failure Group can be retried or archived at once from the Failure Group screen. To see a list of messages within a Failure Group click the the title of the group.
See Failed Message Monitoring in ServicePulse for more information.
NOTE: This feature requires ServiceControl version 1.6 or higher.
#183 "Endpoints Overview" and "Configuration" screens are now displaying their lists in alphabetically order
When you have more than a few endpoints, this quickly becomes unmanageable.
By sorting these lists by default, it becomes easier to manage and browse the lists.
#180 Failed messages to display UNKNOWN when data is missing instead of blank or minimum date
When an NServiceBus endpoint receives messages from external systems such as BizTalk, TIBCO, etc. directly, the message itself will not contain regular NServiceBus headers. Without them ServiceControl cannot provide all usual information. For example, it won’t be able to determine when message was sent or what is its type.
To ensure that you are able to monitor your endpoints and have valuable metadata from ServiceControl, it becomes important as to how you integrate these messages. If for some reason failed messages will miss some metadata ServicePulse will handle it better by providing more meaningful defaults and descriptions.
Here is an example:
#171 A confirmation is now displayed when clicking the "Retry all messages" button
Confirmation when one clicks the "Retry all messages". This will prevent situations where messages are retried when the button is clicked by accident.
#170 In Failed Messages screen, word-wrap message type and destination address is now on
The failed message details cuts off long message types and destination addresses, this commit addresses this issue.
#22 Notification of a new version available is now displayed in the Dashboard
Added a footer to the dashboard of ServicePulse that displays when a new version is available.
This footer contains a hyperlink that will take you to the download page for the latest release.
Bugs
- #172 When a message is missing headers such as
TimeSent, display appropriate defaults - #169 In Failed Messages screen, when message types are not present in the metadata from ServiceControl, ServicePulse must display proper default values instead of
NULL_TYPE - #156 When upgrading ServicePulse the "config.js" file is overridden/reset
- #149 Word-wrap endpointname in endpoints screen
- #67 White rectangle appears behind notification messages on Failed Messages page
Where to get it
You can download this release from our website
1.1.1
As part of this release we had 1 issue closed.
Bugs
#150 Installer expects 'Users' group. Language specific.
In a non-English install of Windows 7 x64 I get the error "An error occurred while applying security settings. Users is not a valid user or group.", which is correct as it doesn't exist. All local groups are language specific. Manually creating the group skips the error but causes a nondescript error later. Install can't finish.
1.1.0
New Features in the Release
- Added the ability to view the header and body of failed messages
- Reworked installer and service to allow low privilege accounts to act as the service account
Improvements in this Release
- Changed the default service account to be localservice
- Messages summary statistics now updated correctly after successful retry / archive of a failed message
- CustomChecks list page now automatically updates in responsecontent in to CustomCheck updates
- Fixed issues with graphics glyphs not being shown on Internet Explorer
- Minor Content improvements
- Minor Installer improvements
As part of this release we had 8 issues closed.
What is Service Pulse?
Particular Software ServicePulse is the new operational monitoring tool for distributed applications developed using NServiceBus.
An Introduction to ServicePulse for NServiceBus provides a short ~7 minute introductory video and demo of ServicePulse capabilities and main features for this release.
Prerequisites
- .NET Framework 4.5 or later
- Particular Software ServiceControl 1.0.0 or greater (latest is best)
- Monitored NServiceBus endpoints must use NServiceBus 4.0.0 or higher
- (support for earlier releases will be added in a future release)
Installation
- Download and install ServiceControl 1.0.0 or greater
- Download and install ServicePulse 1.1.0
- The following installation parameters are used by the ServicePulse installer:
- ServicePulse Instance URI:
- Default is http://localhost:9090
- This is the localhost address and port that will be used for accessing the ServicePulse web application
- ServiceControl instance URI:
- Default is http://localhost:33333/api/
- The URI that will be accessed by ServicePulse web app in order to communicate with the ServiceControl instance
- Review ServiceControl 1.0.0 release notes for more details on installing and configuring ServiceControl for use by ServicePulse
- ServicePulse Instance URI:
- After accepting the license terms and conditions, click "Install" (installer will require elevated privileges)
- The installation process performs the following actions:
- Installs the Windows Service "Particular ServicePulse" which hosts the web application
- Open the ServicePulse web application using the default browser
- After installing ServicePulse, see the following sections to configure your existing endpoints to be monitored via ServicePulse.
HOW TO: Configure endpoints for monitoring by ServicePulse
http://docs.particular.net/Servicepulse/how-to-configure-endpoints-for-monitoring
HOW TO: Develop Custom Checks for ServicePulse
http://docs.particular.net/Servicepulse/how-to-develop-custom-checks
Troubleshooting:
1.0.1
Introduction
Particular Software ServicePulse is the new operational monitoring tool for distributed applications developed using NServiceBus.
An Introduction to ServicePulse for NServiceBus provides a short ~7 minute introductory video and demo of ServicePulse capabilities and main features for this release.
Prerequisites
- .NET Framework 4.5 or later
- Particular Software ServiceControl 1.0.0
- Monitored NServiceBus endpoints must use NServiceBus 4.0.0 or higher
- (support for earlier releases will be added in a future release)
Installation
- Download and install ServiceControl 1.0.0
- Download and install ServicePulse 1.0.0
- The following installation parameters are used by the ServicePulse installer:
- ServicePulse Instance URI:
- Default is http://localhost:9090
- This is the localhost address and port that will be used for accessing the ServicePulse web application
- ServiceControl instance URI:
- Default is http://localhost:33333/api/
- The URI that will be accessed by ServicePulse web app in order to communicate with the ServiceControl instance
- Review ServiceControl 1.0.0 release notes for more details on installing and configuring ServiceControl for use by ServicePulse
- ServicePulse Instance URI:
- After accepting the license terms and conditions, click "Install" (installer will require elevated privileges)
- The installation process performs the following actions:
- Installs the Windows Service "Particular ServicePulse" which hosts the web application
- Open the ServicePulse web application using the default browser
- After installing ServicePulse, see the following sections to configure your existing endpoints to be monitored via ServicePulse.
HOW TO: Configure endpoints for monitoring by ServicePulse
http://docs.particular.net/Servicepulse/how-to-configure-endpoints-for-monitoring
HOW TO: Develop Custom Checks for ServicePulse
http://docs.particular.net/Servicepulse/how-to-develop-custom-checks
Troubleshooting:
1.0.0
Introduction
Particular Software ServicePulse is the new operational monitoring tool for distributed applications developed using NServiceBus.
An Introduction to ServicePulse for NServiceBus provides a short ~7 minute introductory video and demo of ServicePulse capabilities and main features for this release.
Prerequisites
- .NET Framework 4.5 or later
- Particular Software ServiceControl 1.0.0
- Monitored NServiceBus endpoints must use NServiceBus 4.0.0 or higher
- (support for earlier releases will be added in a future release)
Installation
- Download and install ServiceControl 1.0.0
- Download and install ServicePulse 1.0.0
- The following installation parameters are used by the ServicePulse installer:
- ServicePulse Instance URI:
- Default is http://localhost:9090
- This is the localhost address and port that will be used for accessing the ServicePulse web application
- ServiceControl instance URI:
- Default is http://localhost:33333/api/
- The URI that will be accessed by ServicePulse web app in order to communicate with the ServiceControl instance
- Review ServiceControl 1.0.0 release notes for more details on installing and configuring ServiceControl for use by ServicePulse
- ServicePulse Instance URI:
- After accepting the license terms and conditions, click "Install" (installer will require elevated privileges)
- The installation process performs the following actions:
- Installs the Windows Service "Particular ServicePulse" which hosts the web application
- Open the ServicePulse web application using the default browser
- After installing ServicePulse, see the following sections to configure your existing endpoints to be monitored via ServicePulse.
HOW TO: Configure endpoints for monitoring by ServicePulse
http://docs.particular.net/Servicepulse/how-to-configure-endpoints-for-monitoring
HOW TO: Develop Custom Checks for ServicePulse
http://docs.particular.net/Servicepulse/how-to-develop-custom-checks
Troubleshooting:
1.0.0-Beta4
Introduction
Particular Software ServicePulse is the new operational monitoring tool for distributed applications developed using NServiceBus.
An Introduction to ServicePulse for NServiceBus provides a short ~7 minute introductory video and demo of ServicePulse capabilities and main features for this Beta release.
Prerequisites
- .NET Framework 4.5 or later
- Particular Software ServiceControl Beta 7
- Monitored NServiceBus endpoints must use NServiceBus 4.0.0 or higher
- (support for earlier releases will be added in a future release)
Installation
- Download and install ServiceControl 1.0.0 Beta 7
- Download and install ServicePulse 1.0.0 Beta 3
- The following installation parameters are used by the ServicePulse installer:
- ServicePulse Instance URI:
- Default is http://localhost:8082
- This is the localhost address and port that will be used for accessing the ServicePulse web application
- ServiceControl instance URI:
- Default is http://localhost:33333/api/
- The URI that will be accessed by ServicePulse web app in order to communicate with the ServiceControl instance
- Review ServiceControl beta 6 release notes for more details on installing and configuring ServiceControl for use by ServicePulse
- ServicePulse Instance URI:
- After accepting the license terms and conditions, click "Install" (installer will require elevated privileges)
- The installation process performs the following actions:
- Installs the Windows Service "Particular ServicePulse" which hosts the web application
- Open the ServicePulse web application using the default browser
- After installing ServicePulse, you will need to:
- Configure your NServiceBus applications endpoints
- Author and deploy Custom Checks that will be monitored by ServicePulse.
- See the following sections for detailed guidance on performing these actions
HOWTO: Configure endpoints for monitoring by ServicePulse
http://docs.particular.net/Servicepulse/how-to-configure-endpoints-for-monitoring
HOWTO: Develop Custom Checks for ServicePulse
http://docs.particular.net/Servicepulse/how-to-develop-custom-checks
Troubleshooting:
http://docs.particular.net/Servicepulse/Troubleshooting
Fixed issues
This release consist of these issues that were achieved through these commits.
Features
#97 Create a Chocolatey package
- Since chocolatey packages are limited in size the large binary component will be stored in github releases
- Host an icon online for the package. Particular/PlatformInstaller#27
- Generate the version number here as part of a build
- Support uninstall
- Make Silent
- Add logging http://www.advancedinstaller.com/user-guide/qa-log.html
#65 SP License check and user notification
User experience
Notification of licensing limitations
- As Opie is using ServicePulse, he will be notified when the installation of SP exceeds its licensing limitations
- SP licensing limitations are:
- Number of monitored (physical or virtual) servers (based on server names)
- Trial period exceeded
- SP licensing limitations are:
- The notification will be presented as a message in ServicePulse
- Message will be displayed on browser opening or on browser page refresh (Browser F5)
- The message will not be closeable (i.e. it will always be presented, until a license is intsalled and the page is refreshed)
Content trimmed. See full issue
#15 Implement endpoint configuration Indicator and management
As Opie, I want to be notified of any configuration issues that may affect the accuracy of the ServicePulse display. I want to know when I need to update, reconfigure an existing endpoint, or stop monitoring an obsolete endpoint
Visualization:
- In the dashboard, the configuration indicator is displayed indicating the status of the endpoint monitored by ServicePulse:
- It is green when:
- all monitored endpoints have a plugin installed
- plugin version applies to minimal requirements (configured value of minimum plugin version supported by current version of ServicePulse)
- It is red when;
- one or more of the monitored endpoints do not have a plugin installed
- the installed plugin is of an earlier version than the version specified as minimum requirement for the current ServicePulse version
- It is green when:
- Clicking on the configuration indicator in the dashboard leads Opie to the endpoint configuration page
- Opie can view the endpoints list
- Opie can un-check one or more endpoints, making the un-monitored
- An un-monitored endpoint will remain visible in the list of endpoints
- An un-monitored endpoint is not expected to send heartbeat messages, and failure to receive heartbeat messages from this endpoint does not result in the heartbeat indicator being red
Notes:
- An un-monitored endpoint can still be active (i.e. send custom checks events, failed messages and process SLA events; un-monitoring affects only the expectation for a periodic hearbeat message)
Demo / Acceptance tests:
Case 1:
- Configure the Video Store sample to have the plugin installed only on the Sales and eCommerce endpoints (2 of 5 endpoints)
- All 5 endpoints will be sending auditing and error data to the audit and error queues monitored by ServiceControl
- Run the Video Store sample (5 endpoints)
- The Configuration indicator in the dashboard page is green displays 2 monitored endpoints (after receiving heartbeat messages from the Sales and eCommerce endpoints)
- 2 Configuration events are added (severity: info) indicating that 2 new endpoints were added to the monitored endpoints list (including endpoint names and hosting machine name and IP) and that heartbeat messages were received from these endpoints
- Send a purchase order using the Video Store UI and await the successful completion of the purchase process
- The Configuration indicator in the dashboard page turns red, and displays that 3 endpoints are not configured
- (i.e. the 3 of 5 endpoints belonging to the Video Store sample that do not have a configured plugin; these endpoint were added to the endpoints list through the processing of auditing messages, and they expected by default to be monitored)
- 3 Configuration events are added (severity: warning) indicating that 3 new endpoints were detected and were added to the monitored endpoints list (including endpoint names and hosting machine name and IP), but that they do not have a plugin installed and no heartbeat messages were received from these endpoints
- Click on the Configuration indicator in the dashboard page and reach the endpoint configuration page
- There are 5 endpoints in the endpoint list.
- All are marked as monitored
- 2 (sales and ecommerce) have a plugin installed and the plugin version is displayed
- 3 have no plugin installed and there is no plugin version displayed
- Uncheck the "CustomerRelations" endpoint
- 1 Configuration event is added (severity: info) indicating that the "CustomerRelations" endpoint is no longer monitored
- Return to the dashboard and make sure the configuration indicator in the dashboard page is red but that it now displays that 2 endpoints are not configured
- Stop the Video Store sample and have the plugin installed on all 5 endpoints
- Run the Video Store sample (5 endpoints)
- The Configuration indicator in the dashboard page is green displays 4 monitored endpoints
- 2 Configuration events are added (severity: info) indicating that 2 monitored endpoints (already listed in the endpoints list) started sending heartbeat messages
- Click on the Configuration indicator in the dashboard page and reach the endpoint configuration page
- There are 5 endpoints in the endpoint list.
- Check the "CustomerRelations" endpoint to make it monitored again
- 1 Configuration event is added (severity: info) indicating that the "CustomerRelations" endpoint is being monitored
- Return to the dashboard and make sure the Configuration indicator in the dashboard page is green and displays 5 monitored endpoints
Improvements
#98 Add tooltip to describe "Monitor" in SP config page
- Related to #15
- (BTW - nice implementation of #15. Works great!)
- Please add a tooltip to the "Monitor" column to explain its purpose.
- Proposed phrasing: "Monitor the endpoint, and alert if no heartbeats are received"
- Also - optionally - add a label next to the checkbox stating whether the endpoint "Monitored" or "Not Monitored"
CC @indualagarsamy, @andreasohlund - Make sense ?
#89 Remove "Beta Expired" May 1st
Related to ...