Skip to content

Conversation

@ewencp
Copy link
Contributor

@ewencp ewencp commented Jan 28, 2015

Add support for metrics generated automatically by rest-utils. This required a few updates due to changes to the framework. Blocked by confluentinc/rest-utils#6

Most importantly, this changes the default prefix for the metrics. However, the
bulk of the change makes minor adjustments to work with the common-utils Time
interface.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ewencp To speed up review, could you post the jmx metric name that is created as a result of this annotation. This example should suffice to understand the rest.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure. This generates:

That's in addition to the global ones for Jersey (same as above, but without the brokers.list prefix) and global ones for Jetty:

  • connections-accepted-rate
  • connections-opened-rate
  • connections-closed-rate
  • connections-active

All the Jersey ones are collected under a "jersey-metrics" group and Jetty ones under a "jetty-metrics" group.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ewencp These look good. What do you think about 90, 99 and 999 percentiles for some of these, like for example the latency and byte-rate ones. One potential risk is that we don't know how well the percentiles work in common-metrics.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's actually exactly why I didn't add them in :) The new producer code only seemed to use avg and max, so I stuck with that. But I agree, 90, 99, and 999 would be great.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. Let's just leave it then and come back to it when we are slightly more confident of the quality of the percentiles :)

Other than that, this patch looks good.

Conflicts:
	src/main/java/io/confluent/kafkarest/KafkaRestConfig.java
ewencp added a commit that referenced this pull request Jan 29, 2015
@ewencp ewencp merged commit 33943d2 into master Jan 29, 2015
@ewencp ewencp deleted the rest-utils-metrics branch January 29, 2015 17:50
@ewencp ewencp mentioned this pull request Feb 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants