Skip navigation
All Places > CA APM > Blog > 2014 > December > 15

CA APM

December 15, 2014 Previous day Next day

We are happy to announce that the CA APM 9.7 release is now officially GA and available for download from CA Support Online (CSO).

 

Following the CA APM 9.7 announcement on Dec. 8th, we kicked off a 12 Days of CA APM Blog Series in the holiday spirit. I challenged our CA APM team get into the holiday spirit and sing ( to the tune of the 12 days of Christmas) their way through the 12 days of CA APM 9.7 . The CA Team accepted the challenge and covered top features of APM 9.7 in 12 blogs.

--------------------------------------------------------------------------------------

TThe 12 Days of APM Blog SeriesT

 

Twelve Refined Analytics (12/19)

Eleven Developer Community (12/18)

Ten CA Release Automation Integration (12/17)

Nine Node.js Monitoring (12/16)

Eight PHP Monitoring (12/15)

Seven CA UIM Integration (12/14)

Six MongoDB Monitoring (12/13)

FIVE Rich Email Notifications with Contextual Data (12/12)

Four Smart Instrumentation (12/11)

Three Mobile App Analytics (12/10)

Two APM Command Center (12/9)

and an E.P.I.C APM Strategy  (12/8)

--------------------------------------------------------------------------------------

 

In addition to features already covered in these 12 blogs, CA APM 9.7 included following functionalities as well :

 

End User Endpoints Monitoring: It uses a common business transaction definition to monitor the performance of an end-user business transaction in context from the backend application perspective. It also brings end point performance data into the APM AppMap, Investigator, and Transaction Traces in context of business transactions

 

High Performance Transaction Impact Monitor (TIM): The Transaction Impact Monitor now provides parallel processing functionality enabling users to scale up to handle as much traffic as the network card and CPUs can handle.

 

Real Time Transaction Metrics (RTTM): provides real-time information about the end-user experience before that experience degrades to the point that an incident is created. Users can now organize their RTTM metrics by user group to capture more effective and meaningful business metrics.

 

For more information, see the APM 9.7 Release Notes included with the APM 9.7 product documentation posted to the wiki.ca.com site.

 

CA team had a lot of fun singing along these last 12 days. In this brief and amusing video members of CA Technologies APM team sing highlighting powerful new capabilities in CA APM 9.7 to the tune of the all-time classic, The Twelve Days of Christmas.

 

 

Happy Holidays!!

 

Learn more about the E.P.I.C APM and CA APM 9.7 as the first proof point of this strategy in a webcast with well known APM best practices author Mike Sydor and me on January 13th Introducing the E.P.I.C. APM: Stimulate User-Loyalty and Differentiation | BrightTALK

 

slide3_001.png

On the eighth day of APM 9.7, the CA Team gave to me… PHP Monitoring

 

It has happened. Introscope has now an agent that is able to hook into a PHP enabled webserver.

Install this Agent, and continue monitoring and troubleshooting as you were used to it using Introscope Workstation or WebView. Of course some PHP Knowledge will be required to fix issues, the monitoring part though, has not changed.

 

 

So - what is this PHP Monitoring, and how does it work ?

 

The current implementation of the PHP Agent runs under Linux, has been compiled for 64Bit CentOS/RedHat 5.5+ and 6.5+.

It will require a PHP v5.3.x or 5.4.x framework running an apache 2.2.x and a Java 1.8.0_65 (which is provided by default). Note that the apache part is only required for the agent, not the probe.

The way this implementation works, is that a probe is loaded through the PHP configuration on the WebServer, and this probe will provide metrics to the java-agent which will be collecting the data. This agent can run on the same host, or a remote host. It really depends on the available resources on the PHP enabled web-Server. The agent can then feed the collected data to a APM collector release 9.6 or 9.7.

 

 

 

Installation

Installation is very easy and fast, requires however a restart of the WebServer to load the probe. Make sure the probe is configured right the first time, this avoids restarting the WebServer more than required.

The long and detailed version can be seen in the provided documentation.

 

The short version is:

Probe: Copy the probe executable to the plugin directory for PHP, configure the probe and copy this configuration file to the right directory too. Make sure the probe is loaded by the PHP implementation and restart the webserver. Make sure there are no errors showing up in the apache/probe logs (if enabled).

Agent Collector: The Agent is practically pre-configured to run as known under introscope. All that needs to be done is to tell the Agent where the collector is. Of course, if a MoM exists, point it to that one. They will figure out themselves where to send the metrics to.

 

By default, the probe/collector will collect only a minimum set of metrics. Transaction tracing and deep transaction tracing need to be enabled specifically, as not everyone wants these to be active by default.

 

Once done though, the results speak for themselves:

PHPAgent_Trace.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

--------------------------------------------------------------------------------------

The 12 Days of APM Blog Series

 

Twelve (12/19)

Eleven (12/18)

Ten (12/17)

Nine (12/16)

Eight APM PHP Monitoring (12/15)

Seven CA UIM Integration (12/14)

Six MongoDB Monitoring (12/13)

Five Rich Email Notifications with Contextual Data (12/12)

Four Smart Instrumentation (12/11)

Three Mobile App Analytics (12/10)

Two APM Command Center (12/9)

and an E.P.I.C APM Strategy  (12/8)

--------------------------------------------------------------------------------------

 

Filter Blog

By date: By tag: