-
Notifications
You must be signed in to change notification settings - Fork 79
cyanite master == graphite-api ref ? #117
Comments
maybe this helps - this is from the cyanite master compiled log:
|
@danielsand I'll test the whole scenario again throughout the weekend and will adapt graphite-cyanite if necessary |
@pyr thanks for the effort. |
@pyr same for me, e.g http://127.0.0.1/metrics/find/?_dc=1438359955641&query=*&format=treejson&path=&node=GraphiteTree Response: Graphite encountered an unexpected error while handling your request. Traceback (most recent call last): Have not found the 'leaf' in elasticsearch index.... |
@mrkb thanks, this is really helpful. I will push a fix later today. |
duplicate of #119. Fix should come around quick now, sorry about the wait. |
Hello Again @pyr,
i have some Questions again :)
i have now a complete setup running.
Cassandra 2.1
2 cyanite servers:
one with the exoscale packages
one with the current master compiled jar
if i use the packages from the exoscale repo and install graphite-api - all works like a charm.
but it looks like the deb packages are quiet old and when i put stress on cyanite - a lot of metrics get lost.
so i compiled a recent master version of cyanite and got it running.
Metrics get in and i try now to connect graphite-api to it.
when i try to query the metrics - 500 errors occur.
do you have a different graphite-api version chained to this ?
a git ref in the graphite-api or cyanite python module would be awesome :)
The text was updated successfully, but these errors were encountered: