Skip to content
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

Kibana 4 appears to break if using scripted fields and deleting old logstash indices #9751

Closed
silverl opened this issue Feb 18, 2015 · 3 comments

Comments

@silverl
Copy link

silverl commented Feb 18, 2015

Using Kibana 4 RC1 and ES 1.4.3.

I purge logstash indices nightly to maintain a rolling 90-day window of log data.

I created some visualizations and dashboards against my logstash indexes using the basic index pattern [logstash-]YYYY.MM.DD.

I added scripted fields like:
bytestotal = doc["bytesin"].value + doc["bytesout"].value
@timestamp._hourOfDay Integer.parseInt(new Date(doc["@timestamp"].value).format("H")) number

Everything works fine for that day. The next day, Kibana 4 is throwing errors on the Discover tab and nothing works. Overnight, the oldest index was intentionally deleted by cron.

If I then delete all my scripted fields, Kibana 4 starts working again. I can re-add them, continue on my merry way.

I couldn't find any errors in the node service logs. Couldn't figure out how to extract a meaningful error from the K4 UI.

@rashidkpc
Copy link

It look like you're using scripts from Beta 3. RC1 and above do not support Groovy scripting due to this ticket: #9655

@silverl
Copy link
Author

silverl commented Feb 27, 2015

Can you tell me how you arrived at the conclusion that this is due to scripts from Beta 3?

@clintongormley
Copy link

Closing this ticket as this is not an Elasticsearch issue.

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

No branches or pull requests

3 participants