When using the HTTP collector to perform data collection, all data is stored at the node level. This is an RFE to permit data to be stored in an indexed fashion, as it is with the JMX collector.
For example, when currently using the HTTP collector to do data gathering against Apache's statistics module, all of the data gathers at the same hierarchical level as the rest of the node's basic SNMP information. Having all HTTP collections for a given node be gathered with the basic node information makes it inconvenient to separate relevant information out for the separate HTTP-based collections in place.
Environment
OpenNMS Version: 1.8.10
Java Version: 1.5.0_18 Sun Microsystems Inc.
Java Virtual Machine: 1.5.0_18-b02 Sun Microsystems Inc.
Operating System: Linux 2.6.9-67.0.1.mpc30smp (amd64)
Servlet Container: jetty/6.1.24 (Servlet Spec 2.5)
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Alejandro Galue July 30, 2013 at 4:32 PM
The XML Collector has been enhanced in 1.12 in order to process the following:
1) Bad formatted HTML using XPath 1.0 or using CSS Selectors 2) Process JSON data using XPath 1.0 3) Ability to process POST request sending XML, JSON or Form-URL-Encoded 4) Ability to pre-process data by passing an XLST 1.0
The documentation will be on the wiki soon, but in 1.12, the XML Collector is way more powerfull than the HTTP Collector, and with the XML Collector you can use anything that currently works only with the SNMP Collector like:
When using the HTTP collector to perform data collection, all data is stored at the node level. This is an RFE to permit data to be stored in an indexed fashion, as it is with the JMX collector.
For example, when currently using the HTTP collector to do data gathering against Apache's statistics module, all of the data gathers at the same hierarchical level as the rest of the node's basic SNMP information. Having all HTTP collections for a given node be gathered with the basic node information makes it inconvenient to separate relevant information out for the separate HTTP-based collections in place.