1 and 4:
We have thought about that in addition to service application specific
data, the timeline server should accept the web UI plugin from the
application, install it and render the data on the web page according the
application's design, but still need to figure out the plan. Before that,
the application needs to take care of the data rendering itself, or make
use of third-party monitoring service, such as Ambari, which AFAIK, has
integration with the timeline server in the recent release (Tez is
leveraging it). And yes, it's always welcome if somebody want to contribute.

REST APIs are available for accessing both the generic data and framework
specific data. For the API specification, you can temporally look at the
patch in YARN-1876.

In terms of services, they're almost there. The next step would be about
the security, scalability and integration stuff.
On Thu, Apr 24, 2014 at 11:11 PM, Ashwin Shankar

Zhijie Shen
Hortonworks Inc.

NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB