Bug ID
Read on to know what's new and changed in Update 2 of ColdFusion (2018 release) Performance Monitoring Toolset.
Elasticsearch already supports SSL and Authentication, but in earlier releases, Elasticsearch used SSL and Authentication, then ColdFusion and Performance Monitoring Toolset were unable to communicate with Elasticsearch.
In this release, ColdFusion and Performance Monitoring Toolset can communicate with Datastore when it’s running over SSL and using Authentication.
When Datastore runs over SSL and uses Authentication, it remains secured.
For more information, see Authentication and SSL support in Datastore.
In the Purge section, there is a new tab Datastore.
Here you can see all data based on indices, which is data grouped by date. In an index, a full day’s data is stored.
You can also delete an index to free up disk space. You can delete the request indices for the Datastore. Typically, you’d delete an index to free up system space.
You can also delete a specific index from the list. To delete any index in the table, click Delete.
You can use the scheduler to delete data periodically. The depends on the frequency and data older than options, and based on the values defined, the scheduler will run and will delete data, which is older than the specified amount of days.
The scheduler, in this example, executes every day and deletes data that is older than seven days.
By default, the value for data deletion scheduler is 7 and 1 days. The data deletion scheduler is disabled by default.
Clear all alerts that you receive. To delete the alerts, navigate to the Alerts raised page, and click the bin icon.
Clear a single alert by selecting the alert and clicking the Bin button.
Also choose multiple alerts and clear all by clicking the Bin button (highlighted). This will clear all the alerts in the system.
Note: You can select up to 100 alerts at a time.
In the Advanced monitoring section, you can capture only those requests that exceed a specified threshold. A case in point is you want to log requests that take more than 30 seconds.
Bug ID |
Description |
Component |
---|---|---|
If you set a value of threads to be busy before an alert, you get a notification even if not all thosethreads have been busy for the allocated time. |
Alerts |
|
Performance Monitoring Toolset fails to start the service from the Windows service managerafter adding many instances. |
Core |
|
In Dashboard > Settings > Node > Alerts > Settings, you cannot add email ids separated by a comma. |
Settings |
|
There are issues when registering a node in a group if the name of the group contains a space. |
Group |
|
Provide support for update workflows in ColdFusion (2018 release) Performance Monitoring Toolset. |
Update |
Note: On 64-bit computers, use 64-bit JRE for 64-bit Performance Monitoring Toolset.
If the Performance Monitoring Toolset server is behind a proxy, specify the proxy settings for the server to get the update notification and download the updates. Specify proxy settings using the system properties below in the jvm.config, or provide the proxy settings in Performance Monitoring Toolset dashboard (Settings > Updates > Settings)
Windows: <pmt_install_home>/jre/bin/java.exe -jar <jar-file-dir>/hotfix-002-326016.jar
Linux-based platforms: <pmt_install_home>/jre/bin/java -jar <jar-file-dir>/hotfix-002-326016.jar
Ensure that the JRE bundled with Performance Monitoring Toolset is used for executing the downloaded JAR.
Install the update from a user account that has permissions to restart Performance Monitoring Toolset and Datastore services.
After applying this update, the ColdFusion Performance Monitoring Toolset build number should be 2018,0,2,326016.
To uninstall the update, perform one of the following:
Accedi al tuo account