Conversation
|
@rohitkochar please checkout this and let me know what you think |
There was a problem hiding this comment.
you might need a blank line before the table starts for it to render correctly
There was a problem hiding this comment.
This would read better if you said "All the configuration parameters ...". That would solve the subject-verb number disagreement here.
It would be good to have some punctuation at the end, maybe a colon.
|
Thanks @b-slim . |
There was a problem hiding this comment.
instead of module README, please put this in a the doc file in the docs/development folder and link in TOC as an experimental feature
|
This may be unrelated to this PR but, |
There was a problem hiding this comment.
nit: you can probably just do
catch (ExecutionException | TimeoutException e) {
log.error(e, e.getMessage());
}
6d8db4b to
44632ce
Compare
|
@himanshug and @b-slim - we are using https://github.com/dropwizard/metrics in production for ages now. Just works. I guess it's finally time to write our own emitter (dropwizard -> kafka), I was holding it off for druid 0.8 changes. |
There was a problem hiding this comment.
nit: the comma here should be a semicolon, and no space before it
|
@himanshug can you please review this ? |
There was a problem hiding this comment.
@fjy though the all the MD files are converted to html, ? i am i wrong ?
|
👍 after my comment around the README fix is addressed |
There was a problem hiding this comment.
can we just link to the json file containing the whitelist or else the json below has to be kept in sync
|
@bslim 👍 besides the minor comments, feel free to merge after resolving the comments |
9ef88a2 to
c075b44
Compare
|
@rohitkochar are you aware of the current changes on how to supply the whiteList map |
c075b44 to
f5a51cd
Compare
|
@spektom we changed the way we supply the map in favor of file path. |
f5a51cd to
e0d90f8
Compare
|
I added the graphite extension but now even though it is present : I get this error : The default It is just cannot be loaded. Btw the graphite-extension is part of the docker image and |
|
I think it's a bug, because : cannot read a path gotten from : So it basically expect users to always supply custom |
|
@l15k4 are you sure your user used to run druid is able to read the file ? |
|
@b-slim yeah it's a docker container, everything runs as root. Imho it is clear that : Cannot work ... |
|
@l15k4 will take a look thanks for you concern ! |
|
@b-slim thanks, it is weird that it works for others though. I'm using the implydata distribution and docker-distribution image. I had to modify it : Btw would you mind giving me a hand here? https://groups.google.com/d/msg/druid-user/RnpKpW5vowg/0sTc4syLBAAJ |
|
Hey @b-slim, I've noticed of another problem, major one, when graphite becomes unreachable for some time (i just stopped it for a few minutes) then even though it becomes reachable the GraphiteEmitter cannot recover from that and it indefinitely throws exceptions every minute : The |
Adding a new emitter that sends some carefully selected metrics to a graphite server.