impossible to make indexPrefix working

[Benraay]

Hi,
thanks for the job you made on this, it was really helpful for me, however I can't get the "indexPrefix" option working

I tried adding it like this
const esTransportOpts = { level: 'info', clientOpts: { node: "XXXXX" }, source: NODE_ENV, indexPrefix:"scraper" };

But I always have an error "illegal_argument_exception"

Is there any other parameter I need to set ?
for now I'm using the default "logs" indexPrefix but I want to put it on another service and I'm stuck with it

the only way I found was specifying the "index" option but there is no way to have the index per day like default feature

[vanthome]

For me this is working fine with the latest version. I just set in test.js in the options indexPrefix: 'scraper'
and after running the test, I have an index called scraper-2021.07.15.
Are you using the latest version?

[Benraay]

Hi, here is the whole error message : illegal_argument_exception: [illegal_argument_exception] Reason: index template [template_scraper] has index patterns [logs-app-default*] matching patterns from existing templates [template_logs] with patterns (template_logs => [logs-app-default*]) that have the same priority [200], multiple index templates may not match during index creation, please use a different priority maybe there is some other configuration to change somewhere, thanks for your help

[vanthome]

I suppose you are using an ES instance that might already have older indexes. Can you maybe try to rempty all data in your ES instance and let the logger set the templates etc. anew?