[BUG] audit log doesn't work with alias

[rave189]

Describe the bug

I was using OpenSearch version 2.19.3.
At that time, I was able to manage the audit log settings using an alias name and a rollover policy.
However, this setting is not applied in OpenSearch versions 3.2 and 3.3.2.
Opensearch throws an error log saying that it cannot insert values ​​into an index that already exists.

Related component

Indexing

To Reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

When saving the audit log, if there is an index that already exists, please modify it to insert it into that index.

Additional Details

Plugins
Please list all plugins currently enabled.

Screenshots
If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[cwperks]

[Triage] Thank you for filing this issue @rave189 . Agreed that it should continue trying to store the auditlog message if its already determined that an alias exists.

[tender-barbarian]

@cwperks I've encountered this issue as well. It actually prevents me from updating to v3. Are there plans on fixing this any time soon please?

[cwperks]

@tender-barbarian yes, I believe @pCastq has expressed interest. Once a PR is raised and merged I will update this issue with a tag for the release that a fix will be included in. I think v3.5.0 (next release may be possible), if not v3.5.0 then I would certainly expect it in v3.6.0.

[pCastq]

yes i'm working on it . There a some technical problem that I/we are trying to overcome . Just have a patience :)