Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

[BUG] Index management policy ignores index patterns starting with asterisk #456

Open
andy812 opened this issue Jul 25, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@andy812
Copy link

andy812 commented Jul 25, 2021

I use opendistro with index management plugin v1.13.2.0. My index policy contains such ism_template:

"ism_template": {
        "index_patterns": [
            "prod-*",
            "dev-*",
            "*-events-*"
        ]
}

I have no problems with indices prod-service1-timestamp, prod-service2-timestamp, dev-service1-timestamp, etc. But policy do nothing with indices kube-system-events-timestamp, default-events-timestamp, etc.

How to fix it?

@andy812 andy812 added the bug Something isn't working label Jul 25, 2021
@bowenlan-amzn
Copy link
Contributor

Tested with same ism_template's index_patterns. Create kube-system-events-timestamp index and see it's being managed.

One thing I suspect is when do you create kube-system-events-timestamp? If it's created before ism_template is there, it won't be auto managed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants