The fifty second update of JXInsight 5.7 has been published. This release includes enhancements to the tier probes provider enabling the automatic mapping of classes or packages to tiers via a system property. A system property has also been added to enable a performance optimization that disables future metering of a probe with consecutive non-tierpoint firings. In addition the transaction probes provider now supports the creation of one or more counters (which can be mapped to meters) tracking the number of transaction point probes that have exceed the threshold.
Additional columns have been added to the probes transaction changes table and tree table views comparing the metering average of a change with that of the overall cumulative and mark meterings for the same probe and meter tuple (metering).
For further information please consult the release-notes.txt file located in the root directory of the installation.
The CloudConnect conference is just around the corner. Check out this posting by William Louth, product of JXInsight, giving a glimpse into some of concepts and ideas he will touch on during his two sessions.
William Louth, product architect of JXInsight, has published a blog entry answering two common questions we receive in relation to our resource metering runtime.
“What makes it so much more faster and scalable than other solutions?”
“How can its high quality be maintained with such high frequency of software updates?”.
William Louth, product architect of JXInsight, has published a blog entry highlighting an important issue common to all legacy & modern application performance management transaction tracers at analysis time – they do not scale.
William Louth, product architect of JXInsight, has published a blog entry demonstrating an alternative approach to legacy application performance management transaction tracers. Unlike existing trace solutions which have excessive runtime overhead and reduced visibility this approach does indeed scale in production.
If only a small percentage of your traced requests are breaching service level agreements then you really need to rethink whether the overhead incurred in flooding your network with redundant data packets is truly warranted.
The fifty first update of JXInsight 5.7 has been published. A new optional probes provider, transaction, has been added that automatically records metering ChangeSets for probes marked as typed transaction points which exceed one or more specified metering thresholds. The change set which is basically a (mini) metering model within a metering model for a particular transaction instance can help in efficiently performing root cause analysis of request outliners.
This innovative use of metering is much more efficient & scalable solution than what is promoted by todays application performance management transaction (path) tracers as there is no need to record expensive and deep caller-to-callee call paths (trees/sequences/journals) – only metering changes need be tracked within the executing threads model.
For further information please consult the release-notes.txt file located in the root directory of the installation.
The fiftieth update of JXInsight 5.7 has been published. This update adds the ability to automate dumping of a probes snapshot prior to each automatic mark cycle as well as an important but non-failing bug fix for an issue with access to optional thread level metering model elements – billings and stacks.
For further information please consult the release-notes.txt file located in the root directory of the installation.
William Louth, product architect of JXInsight, has published a blog entry demonstrating how to perform cluster-wide metering analysis of Apache Hadoop’s dynamic JVM execution environment.
William Louth, product architect of JXInsight, has published the second entry in a series of blog entries highlighting the ease at which one can extend the data collection technologies of the product.
The forty ninth update of JXInsight 5.7 has been published. This update includes a set of probe extensions for Terrastore and XWork as well as a non-failing bug fix to the Probes Open API.
For further information please consult the release-notes.txt file located in the root directory of the installation.