Performance Monitoring Toolset Update 1

ColdFusion Performance Monitoring Toolset Update 1 includes the following changes:

• HTTPS support
• Tree view of Code Profiler data
• Datastore health monitoring
• Theme change
• Most frequently run queries chart
• Tracked and un-tracked servers in Topology

REST data does not get captured for a J2EE node in Performance Monitoring Toolset.

Workaround

For a J2EE instrance already deployed on application server, add the filter-mapping specified below under 'CF Monitoring Filter mappings' in cfusion/WEB-INF/web.xml. 
<filter-mapping> 
        <filter-name>CFMonitoringFilter</filter-name> 
        <servlet-name>CFRestServlet</servlet-name> 
 </filter-mapping> 

Issue #1

The line number of a leaf node appears as 0 instead of the actual line number.

Workaround

1. Click on Code profiler, choose the server, and start profiling.
2. Run a cfm file on the server that has a function call in the code.

Issue #2

Only a node that is tracked must display in the server drop-down list.

Issue #3

The code profiler must display top slow urls or service.

Issue #4

Inconsistencies in data that is shown in Code Profiler. When the time taken is shown for cfoutput/any other tag, the time taken does not get displayed for all the components, if any.

Issue #5

A few built-in functions do not get captured in tag/function and code flow tab.

Issue #6

Teh time shown in the code flow does not match the time on top of the page.

When you create a document ID with the pattern IP:instance:port, the existing configuration behaves unexpectedly.

1. Configure ColdFusion with Performance Monitoring Toolset.
2. Navigate to Performance Monitoring Toolset page on the ColdFusion Administrator.
3. Change the hostname.
4. Navigate to Performance Monitoring Toolset dashboard.

There are two entries for the same node.

Thread and heap dumps are visible before and after adding a node to a group.

Issue #1

1. Configure ColdFusion with Performance Monitoring Toolset.
2. On the Overview page, navigate to the section Server Overview.
3. Take few thread dumps and heap dumps.
4. Create a group and move this node to the group.

Thread heap dumps taken before adding this node to the group are visible, which, ideally must not be visible.

Issue #2

1. Take few thread dumps and heap dumps after adding the node to the group that has been created.
2. Remove this group

Thread and heeap dumps taken after adding this node to the group are visible to the individual node.

Issue #1

The chart in the section CF transaction on the Database overview page does not honor the Datasources filter.

When you choose a datasource from the drop-down list, the transaction queries do not get filtered as expected.

Issue #2

The Application and Datasource drop-down filters behave unexpectedly, if you choose a time filter that is more than one hour.

There must an option to import default mail settings at the node/cluster/group level.

Issue #1

Performance Monitoring Toolset must detect whether an incorrect Datastore is being used.

Issue #2

After installation, the datastore creates more than 60 GB of log files.

Issue #1

Performance Monitoring Toolset must include a UI to configure alerts to monitor the health of a datastore.

Issue #2

There must be autentication in datastore, so that it is possible to read/write to the data.

Issue #3

Datastore CPU usage is almost 100% all the time, if there are multiple dashboards that are up and running.

The health score includes the health of the node that is not tracked.

Issue #1

Tags/functions must be always ordered according to the maximum time taken to execute, not the average time taken to execute.

Issue #2

• Add support for tags, like, cfexchange, cfhtmltopdf, and CFOBJECT.
• Ability to view an action distribution chart for the tags for the time taken, and not just the number of invocations.

Performance Monitoring Toolset must add support for asynchronous programming.

In an active session, the number of sessions keep increasing.

Issue #1

In the Busy connections graph, the Y-axis must display only integer values.

Issue #2

The unit of Y-axis must be changed dynamically on the basis of data available.

Issue #3

There must be a graph that shows memory usage, which is based on session/application/server.

Issue #4

On the CF Metrics page, the drill-down url filter shows the url that does not contain the cfthread tag.

Issue #5

The cfthread queue graph does not show urls on drill-down at certain data points.

Issue #6

The drill-down data for graphs must also show details specific to the selected data or metric.

Issue #7

There must be a way drill-down to the urls that are prone to errore with additional details on the type of error.

Issue #8

There must be a graph to compare system memory usage and process memory usage.

Issue #1

On the CF Metrics page, in addition to template/component cache size, there needs to a query cache memory usage, which must be represented as a time series graph.

Issue #2

The CF Metrics page must contain the all the metric details that cfstat command displays.

Issue #1

A cluster is shown as down, even though the cluster serves requests as expected.

Issue #2

When removing the nodes, which are part of diferent clusters, the cluster information does not get removed.

The data for a cache region of a server and an application must be displayed alphabetically.

Issue #1

There must be an option to capture only those requests which are exceeding a specified threshold.

Issue #2

There must be an option to delete the request index.

The Server Overview page takes more time tha expected when pulling from the datastore, if there is a lot of data in the datastore.

If a connector is set for IPv6, the data in Connector dashboard is inconsistent. For consecutive requests, the data toggles in the graphs.

The interval chart for GC must include a drill-down filter to see relevant GC-related information. For example, if there are multiple major GCs, which took more than 10 seconds, there must be a way to check the time stamp of a specific GC.

There must be a Back button to go back to the previous page from the View Alert screen.