Blog Viewer

12 Days of CA APM - Day 11 : APM Developer Community

By Anon Anon posted 12-18-2014 06:26 PM


"On the eleventh day of APM 9.7, the CA Team gave to me… APM Developer Community "


We started singing the 12 days of APM song on December 8th when we announced the release of CA APM 9.7 and plan to sing for 12 days until the CA APM 9.7 software is generally available to download on December 19th  . On 11th day, let me talk the new CA APM Developer community.


Screen Shot 2014-12-18 at 2.32.40 PM.png


Introducing the CA APM Developer Community


The CA APM Developer Community is a new community for APM developers for talking about and building CA APM field packs and extensions. While the CA APM community will continue to focus on the dialog around application monitoring and administration supported out-of-the box with CA APM, this new community will focus on tuning CA APM under the hood and extending it to do even greater things.


In addition, APM team recently announced the CA-APM organization on GitHub where you can find CA APM extension projects, clone or fork the source, make cool changes, share them back with the community. CA Technologies recently teamed up with MongoDBto create (and certify!) an important new data collector to harvest metrics from one of the most important big-data backends in the market.


We're posting this collector to GitHub to  provide you with a great ready-working example of collector using the newly announced RESTFull API support CA APM EPA . Leveraging this you can build similar collectors for all sorts of applications you may want to monitor via CA APM.


Getting Started with CA APM Developer Community Contributions


This community is designed to be a place where you can learn about building extensions, plugins, connectors, or anything else for APM.  Once built, we encourage you to share your best work back with the APM community. There's a number of different content types (like EPA plugins!) that are great candidates to share.  Using the new RESTful API, it's easier than ever to build integrations that send content into CA APM. Learn more


Contribution Process


We have a simple process that utilizes the GitHub:

  1. Sign a Contributor License Agreement (CLA). Learn more here for Understand licensing.
  2. Sign up or login to your GitHub account. Learn more about the basics of Git and GitHub here.  You may wish to be added to the CA-APM organization.  Contact us directly to be added.
  3. Fork the repository on GitHub.  If starting from scratch, fork the template repo.
  4. Report an issue or make a feature request using the Issues manager for the repo.  Look here for details.
  5. Add features or fix bugs.  Code!
  6. Request your code be merged; create a Github Pull Request.  See details here.
  7. Complete a Code Review with the CA APM Engineering Team or CA APM Core Committers on the pull request.  See details here.
  8. Build your fieldpack package, create a release, and upload to the APM community.  See details here.

On December 11, 2014, Chris Kline, Sr. Director at CA APM Product Management team , hosted a webcast introducing the CA APM Developer Community . You may find the replay of the webcast useful if you are considering to build CA APM collector for your favorite application by clicking the link below .


Screen Shot 2014-12-18 at 2.47.28 PM.png


Happy Holidays !


TThe 12 Days of APM Blog SeriesT


Twelve (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)