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

Feature request: Elasticsearch 5.x support #5740

Closed
nickcarenza opened this Issue Aug 5, 2016 · 15 comments

Comments

Projects
None yet
@nickcarenza

nickcarenza commented Aug 5, 2016

Opening issue to track progress and interest for ES 5.x support.

@danielcb

This comment has been minimized.

Show comment
Hide comment
@danielcb

danielcb Nov 2, 2016

Is there any timeline for this yet? Days, weeks, months? Just wondering if running from sources for now is worth the effort. :)

danielcb commented Nov 2, 2016

Is there any timeline for this yet? Days, weeks, months? Just wondering if running from sources for now is worth the effort. :)

@bergquist

This comment has been minimized.

Show comment
Hide comment
@bergquist

bergquist Nov 2, 2016

Contributor

@danielcb no timeline yet. Our current main focus is alerting and ux.

Contributor

bergquist commented Nov 2, 2016

@danielcb no timeline yet. Our current main focus is alerting and ux.

@megakid

This comment has been minimized.

Show comment
Hide comment
@megakid

megakid Nov 2, 2016

I am in the same position @danielcb after our recent Elastic 5.0 upgrade - Sounds like running from sources is the way to go for now.

megakid commented Nov 2, 2016

I am in the same position @danielcb after our recent Elastic 5.0 upgrade - Sounds like running from sources is the way to go for now.

@Spacefish

This comment has been minimized.

Show comment
Hide comment
@Spacefish

Spacefish Nov 2, 2016

I compiled this from source as well for now.
B.t.w. i had to run "grunt build" after you ran "npm build" to get the js files merged into one big boot.js.. Otherwise the site would load like 3-4 times longer as ~100 js files get downloaded one by one.

Alerting does not seem to work for ES (datasource elasticsearch not supported).

Spacefish commented Nov 2, 2016

I compiled this from source as well for now.
B.t.w. i had to run "grunt build" after you ran "npm build" to get the js files merged into one big boot.js.. Otherwise the site would load like 3-4 times longer as ~100 js files get downloaded one by one.

Alerting does not seem to work for ES (datasource elasticsearch not supported).

@ToddZhao

This comment has been minimized.

Show comment
Hide comment
@ToddZhao

ToddZhao Nov 7, 2016

waitting...

ToddZhao commented Nov 7, 2016

waitting...

@defkev

This comment has been minimized.

Show comment
Hide comment
@defkev

defkev Nov 26, 2016

👍

Currently the only thing holding me back from upgrading my deployments.

defkev commented Nov 26, 2016

👍

Currently the only thing holding me back from upgrading my deployments.

@sachavuk

This comment has been minimized.

Show comment
Hide comment
@sachavuk

sachavuk Dec 7, 2016

Hello,

Any news about this feature request ?

sachavuk commented Dec 7, 2016

Hello,

Any news about this feature request ?

@nugusbayevkk

This comment has been minimized.

Show comment
Hide comment
@nugusbayevkk

nugusbayevkk Dec 8, 2016

today i had the same problem.
Grafana team can you tell me, when are you plan fix this problem?
Thanks you a lot.
Today i migrated all data to ELK 5.0.2 from 2.3.4 and then after got next error:
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "No search type for [count]"
}
],
"type": "illegal_argument_exception",
"reason": "No search type for [count]"
},
"status": 400

nugusbayevkk commented Dec 8, 2016

today i had the same problem.
Grafana team can you tell me, when are you plan fix this problem?
Thanks you a lot.
Today i migrated all data to ELK 5.0.2 from 2.3.4 and then after got next error:
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "No search type for [count]"
}
],
"type": "illegal_argument_exception",
"reason": "No search type for [count]"
},
"status": 400

@msteggink

This comment has been minimized.

Show comment
Hide comment
@msteggink

msteggink Dec 9, 2016

The latest nightly (grafana-4.1.0-1481284081pre1.x86_64.rpm) seems to work fine with ElasticSearch 5.0 (5.0.1-1)

msteggink commented Dec 9, 2016

The latest nightly (grafana-4.1.0-1481284081pre1.x86_64.rpm) seems to work fine with ElasticSearch 5.0 (5.0.1-1)

@bergquist

This comment has been minimized.

Show comment
Hide comment
@bergquist

bergquist Dec 9, 2016

Contributor

Closed by #4970

Available as nightly builds at http://grafana.org/builds/

Contributor

bergquist commented Dec 9, 2016

Closed by #4970

Available as nightly builds at http://grafana.org/builds/

@bergquist bergquist closed this Dec 9, 2016

@amdei

This comment has been minimized.

Show comment
Hide comment
@amdei

amdei Feb 14, 2017

Hit exactly the same issue with Grafana v4.1.2 and ES 5.2.0

amdei commented Feb 14, 2017

Hit exactly the same issue with Grafana v4.1.2 and ES 5.2.0

@panikgaul

This comment has been minimized.

Show comment
Hide comment
@panikgaul

panikgaul Feb 20, 2017

Have the issue with Grafana 4.1.1 or 4.1.2 and ES 5.1.1 or 5.2.1 (all version combinations).

Log from grafana by using an Elasticsearch datasource:

t=2017-02-20T08:49:49+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=POST path=/login status=401 remote_addr=X.X.X.X time_ms=188ns size=42
t=2017-02-20T08:49:49+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=GET path=/api/login/ping status=401 remote_addr=X.X.X.X time_ms=21ns size=26
t=2017-02-20T08:50:48+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/_msearch status=403 remote_addr="X.X.X.X, Y.Y.Y.Y" time_ms=73ns size=0
t=2017-02-20T08:50:48+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/_msearch status=403 remote_addr="X.X.X.X, Y.Y.Y.Y" time_ms=513ns size=0
t=2017-02-20T08:50:56+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/_msearch status=403 remote_addr="X.X.X.X, Y.Y.Y.Y" time_ms=62ns size=0

panikgaul commented Feb 20, 2017

Have the issue with Grafana 4.1.1 or 4.1.2 and ES 5.1.1 or 5.2.1 (all version combinations).

Log from grafana by using an Elasticsearch datasource:

t=2017-02-20T08:49:49+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=POST path=/login status=401 remote_addr=X.X.X.X time_ms=188ns size=42
t=2017-02-20T08:49:49+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=0 uname= method=GET path=/api/login/ping status=401 remote_addr=X.X.X.X time_ms=21ns size=26
t=2017-02-20T08:50:48+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/_msearch status=403 remote_addr="X.X.X.X, Y.Y.Y.Y" time_ms=73ns size=0
t=2017-02-20T08:50:48+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/_msearch status=403 remote_addr="X.X.X.X, Y.Y.Y.Y" time_ms=513ns size=0
t=2017-02-20T08:50:56+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=POST path=/_msearch status=403 remote_addr="X.X.X.X, Y.Y.Y.Y" time_ms=62ns size=0
@sujaldalia

This comment has been minimized.

Show comment
Hide comment
@sujaldalia

sujaldalia Aug 14, 2017

Any updates on this? I'm using Grafana 4.4.3-1 & Elasticsearch 5.5 and have same issues.

sujaldalia commented Aug 14, 2017

Any updates on this? I'm using Grafana 4.4.3-1 & Elasticsearch 5.5 and have same issues.

@torkelo

This comment has been minimized.

Show comment
Hide comment
@torkelo

torkelo Aug 15, 2017

Member

what issues? We have only one other report of issues with 5.5,

Member

torkelo commented Aug 15, 2017

what issues? We have only one other report of issues with 5.5,

@agxs

This comment has been minimized.

Show comment
Hide comment
@agxs

agxs Nov 14, 2017

@amdei @panikgaul @sujaldalia make sure to specify you're using ElasticSearch 5.x in the Data Source properties too.

image

agxs commented Nov 14, 2017

@amdei @panikgaul @sujaldalia make sure to specify you're using ElasticSearch 5.x in the Data Source properties too.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment