chetanmeh opened a new pull request #4665: Expose Kafka metrics for User Event consumer as json endpoint URL: https://github.com/apache/openwhisk/pull/4665 This PR expose the metrics related to specific Kafka producer or consumer over `/metrics/kafka` endpoint. ## Description For now this feature is enabled for User Event service where the event consumer's Kafka consumer instance metrics are exposed. Such metrics can provide insight into the Kafka consumers processing stats. The http endpoint is not exposed to end user and meant for developers and system admins to understand the performance characteristics of the consumer at any given time by direct access It also registers the `KamonMetricsReporter` (introduced via #4481) with the User Event consumer to expose some of those metrics as Kamon metrics A typical response for the `/metrics/kafka` endpoint is like below ( > 100 entries) ```json [ { "description": "The number of responses received per second", "group": "consumer-node-metrics", "name": "response-rate", "tags": { "client-id": "event-consumer", "node-id": "node--1" }, "value": 0.05848409232688709 }, { "description": "The total number of connections with successful authentication", "group": "consumer-metrics", "name": "successful-authentication-total", "tags": { "client-id": "event-consumer" }, "value": 0 }, { "description": "The maximum size of any request sent.", "group": "consumer-metrics", "name": "request-size-max", "tags": { "client-id": "event-consumer" }, "value": 179 }, { "description": "The total number of bytes consumed", "group": "consumer-fetch-manager-metrics", "name": "bytes-consumed-total", "tags": { "client-id": "event-consumer" }, "value": 0 } ] ``` Later we plan to enable this feature with Activation Persister Service (#4632) also ## Related issue and scope <!--- Please include a link to a related issue if there is one. --> - [ ] I opened an issue to propose and discuss this change (#????) ## My changes affect the following components <!--- Select below all system components are affected by your change. --> <!--- Enter an `x` in all applicable boxes. --> - [ ] API - [ ] Controller - [ ] Message Bus (e.g., Kafka) - [ ] Loadbalancer - [ ] Invoker - [ ] Intrinsic actions (e.g., sequences, conductors) - [ ] Data stores (e.g., CouchDB) - [ ] Tests - [ ] Deployment - [ ] CLI - [ ] General tooling - [ ] Documentation ## Types of changes <!--- What types of changes does your code introduce? Use `x` in all the boxes that apply: --> - [ ] Bug fix (generally a non-breaking change which closes an issue). - [ ] Enhancement or new feature (adds new functionality). - [ ] Breaking change (a bug fix or enhancement which changes existing behavior). ## Checklist: <!--- Please review the points below which help you make sure you've covered all aspects of the change you're making. --> - [ ] I signed an [Apache CLA](https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md). - [ ] I reviewed the [style guides](https://github.com/apache/openwhisk/wiki/Contributing:-Git-guidelines#code-readiness) and followed the recommendations (Travis CI will check :). - [ ] I added tests to cover my changes. - [ ] My changes require further changes to the documentation. - [ ] I updated the documentation where necessary.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
