[
https://issues.apache.org/jira/browse/HBASE-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159718#comment-17159718
]
Madhusoodan commented on HBASE-20904:
-------------------------------------
[~ndimiduk] Here are the pros and cons of using the agent, please comment your
views.
Pros
* code management is no more a HBase developer burden
Cons
* On slider based deployments..
** we have to dynamically decide the port on which agent listens on as two
server processes (M / RS) can be deployed on a single host (by slider/yarn).
This becomes a burden for the slider user as agent doesn't provide this
funcationality and one cannot choose some random number <64k. Well we can use
agent+pushgateways combination but the metrics are published all the time which
may be become unnecessary given the size of metrics published (prometheus expo
format is verbose).
** these dynamically chosen ports have to be (discovered by) / (told to)
prometheus scraper. This is again a burden for the slider user as the HBase can
be run as a
* Some customers are skeptical about opening new ports for an agent.
> Prometheus /metrics http endpoint for monitoring integration
> ------------------------------------------------------------
>
> Key: HBASE-20904
> URL: https://issues.apache.org/jira/browse/HBASE-20904
> Project: HBase
> Issue Type: New Feature
> Components: metrics, monitoring
> Reporter: Hari Sekhon
> Assignee: Madhusoodan
> Priority: Major
>
> Feature Request to add Prometheus /metrics http endpoint for monitoring
> integration:
> [https://prometheus.io/docs/prometheus/latest/configuration/configuration/#%3Cscrape_config%3E]
> Prometheus metrics format for that endpoint:
> [https://github.com/prometheus/docs/blob/master/content/docs/instrumenting/exposition_formats.md]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
