Chukwa Agent provides REST interfaces that allow management of data stream movement. The primary resources are:
The resources and the entities that are passed to them are defined using JAXB and are represented in either XML or JSON formats depending on the ContentType and Accept HTTP headers. The definition of the types is given in the JavaDoc.
Typical usage would be to create a new adaptor from a pre-defined one and change the necessary configuration parameters. Then configure parser to process the data stream.
Resource | Method | Description |
---|---|---|
http://[host]:[port]/rest/v2/adaptor | POST GET | Adds an adaptor to the agent and returns the adaptor info Get all adaptors |
http://[host]:[port]/rest/v2/adaptor/{adaptorId} | DELETE GET | Remove an adaptor from the agent Get a single adaptor |
JAX-RS controller to handle all HTTP request to the Agent that deal with adaptors.
POST | addAdaptor() |
Adds an adaptor to the agent and returns the adaptor info
Content-Type: application/json | |
Example
| |
Content-Type: application/xml | |
Example for application/xml is available in /rest/v2/application.wadl |
Status: 200 | Content-Type: application/json |
Adaptor has been registeredExample
| |
Status: 400 | Content-Type: text/plain |
Example for text/plain is available in /rest/v2/application.wadl |
GET | getAdaptors() |
Get all adaptors
Status: 200 | Content-Type: application/json |
List all configured adaptorsExample
|
DELETE | removeAdaptor() |
Remove an adaptor from the agent
adaptorId | string | id of the adaptor to return |
Status: 200 | Content-Type: text/plain |
Example for text/plain is available in /rest/v2/application.wadl |
GET | getAdaptor() |
Get a single adaptor
adaptorId | string | id of the adaptor to return |
Status: 200 | Content-Type: application/json |
Adaptor status and data transfer rate in 1, 5, 10 minutes averagesExample
|