-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[indexPatterns] Remove time-based interval support #12242
Comments
I'm not sure I understand the intention here. What would be the problem if we persistently nagged users about using time-interval index patterns? They're doing something "wrong", so I think it makes sense to keep this warning surfaced and force them to deliberately ignore it each time they see it. |
@cjcenizal Sorry, missed your comment. The idea was that the person seeing the warning may not be the person who can fix it. The warning is now disabled until there is a simpler method for editing, since even the warning was too suggestive that there was some reasonable method to fix the issue. |
We should also remove this from the docs: https://www.elastic.co/guide/en/kibana/current/index-patterns.html |
Done in 5ca3001 @tylersmalley |
@elastic/kibana-management is this still incomplete? |
In Kibana 4.3.0 we deprecated creating index patterns with time based intervals, and we are finally going to remove the functionality. I propose the process look something like this:
Why not just pull off the bandaid and completely removing support for time patterns?
[logs-]YYYY.MM[-app-one]
would convert tologs-*-app-one
, but that also matcheslogs-not-app-one
The text was updated successfully, but these errors were encountered: