The point i was trying to make is a more general one: there are all this different issues and somehow they are all related to each other and maybe there can be some sort of common strategy on how to solve this.
And the way to solve it was not only meant to be in technical nature but as well in questioning the current way the different agents get deliverd, who has possiblities to actualy do changes, who has interest that something changes, market considerations etc. (more details in the Beta Community mentioned above)
Thinking outside the box and understanding whats going wrong with the current state to create something better based on this whole process.
With regards to Web Server Power Pack:
The idea behind its a Power Pack for Web Server Monitoring:
The idea of monitoring the Web Servers is important and i dont think Web Server Power Pack is up to the task anymore.
The current technical implementation is a polling of the status page:
I agree that a module deployed in to the webserver is giving you much more possiblities then one just polling the status page. But before talking on technical details the question is what can all be done with the main idea: Web Server Monitoring.
As mentioned by Fred, its stuck in time:
And the fear that this is a example of an neglected part of the product and that it could potentialy happen to the PHPAgent too.
What can be done with Web Server Monitoring
And maybe we could start by defining whats meant with Web Server Monitoring
its crutial to get the basic KPIs (what are they) but obviously a Web Server does much more then delivering HTML files stored on the server, therefore the question about SSL/CGI/PHP/Web Proxy/etc. Defining the scope of monitored products and what else by sides the basic KPIs might be possible to gather or inject e.g.:
- A Web Server deliverds a HTTP Stream from lots of different potential sources
- It has own logic happning inside, as soon its not only just delivering a file but e.g. causing URL redirects, proxying, php, cgi, etc.
- The HTTP Header could be tagged with a transaction ID or simliar
Whata data is hard to gather or still missing and valuable for the new ApplicationMap in CA APM 10?
Maybe bringing the whole topic CEM/TIM back to life in a new form?