-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS & User/Pass auth accessing druid coordinator endpoint #19
Comments
Nice feature request, I guess we can work on this |
Tried it out today, I'm only getting druid health check status being returned, not seeing the other ones now.
|
I have just tested and it seems to be working fine
Can you confirm that you have some running tasks in druid? Also, have you configured the emitter in your druid If you have done both things and still you don't have metrics, please share the logs. |
We wrote our update on the ultils/http.go part, by modifying the requests to allow the basic auth (and ignoring TLS for the time being) We are able to get metrics that way:
While running the newest update from here... we show that the druid exporter running in AWS ECS and we have debug logs turned on with this output 2020-06-08 23:29:14{"level":"info","msg":"GET request is successful for druid api","ts":"2020-06-09T06:29:14.317Z","url":"ELB_OMITTED:9088/druid/coordinator/v1/datasources?simple"} I'll dig into this more tomorrow. Please do know that we truly do appreciate the work and how fast you were able to turn around and get this feature request in! |
Dug into it more, this is not an entire answer but you should be able to see the issue if you add in debugging more on the response data. https://github.com/opstree/druid-exporter/blob/master/collector/druid.go#L35 While the requests are being authenticated, the entire response isn't being reported back with all the stats, it's just reporting back an array of values and when json.Unmarshal(responseData, &metric) it nullifies the data making it through. |
Error was on our side, many different things are embedded and after breaking things down we found it was an issue on the password being stored. |
I didn't see an option to add in a username & password & specify a cacert when accessing a druid coordinator endpoint. Any chance to add those?
The text was updated successfully, but these errors were encountered: