[
https://issues.apache.org/jira/browse/FALCON-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708068#comment-13708068
]
Srikanth Sundarrajan commented on FALCON-9:
-------------------------------------------
Following metrics are already being collected via Falcon and the same is
published to a log file. This can be published to an external metrics
collection framework similar to Ganglia/Graphite as well. Personal preference
would be to avoid storing and exposing metrics through Falcon, instead collect
and publish to a standard metric repository & dashboard.
This is also an opportunity to visit the metric list to see if more needs to be
added to this list.
* Number of API calls & call execution latency of
* getRunningInstances
* getInstanceStatus
* getInstanceLogs
* killInstance
* suspendInstance
* resumeInstance
* submitNewEntity
* deleteEntity
* updateEntity
* getEntityStatus
* getDependency
* scheduleEntity
* suspendEntity
* resumeEntity
* Number of retry failures
* Instances of late re-run failures
* Execution time of failed process instances
> Expose runtime metrics from Falcon via http in JSON
> ---------------------------------------------------
>
> Key: FALCON-9
> URL: https://issues.apache.org/jira/browse/FALCON-9
> Project: Falcon
> Issue Type: Improvement
> Components: metrics
> Environment: Operability
> Reporter: Nikhil Mulley
>
> Please expose the runtime metrics of Falcon over http at /metrics handler.
> Something similar to hadoop components (namenode, datanode, tasktracker....)
> exposing the metrics on webUI /metrics handler. Format can be JSON.
> We need to discuss and come up with all possible runtime metrics needed to be
> exposed from Falcon which could further be usable with
> collecting/graphing/alerting systems.
> thanks,
> Nikhil
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
