Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

Deadletter indexing should be taken care of automatically #245

Open
Tracked by #16
philippkahr opened this issue Feb 14, 2023 · 0 comments
Open
Tracked by #16

Deadletter indexing should be taken care of automatically #245

philippkahr opened this issue Feb 14, 2023 · 0 comments
Labels
Team:Elastic-Agent Label for the Agent team

Comments

@philippkahr
Copy link

Hi,

this issue is sparked by a discussion in Slack. Filebeat supports a deadletter output to index any events that ES fails todo so.

As of now one can implement the following workaround, discovered by @herrBez .

  1. Go to output settings for Elasticsearch
  2. Add the following pieces:
 non_indexable_policy.dead_letter_index:
    index: "logs-unindexable-default"
  1. You need to create an index template for logs-unindexable-* where you disable any mapping.
  2. Now since the Agent isn't actually allowed to write to logs-unindexable-default because it does not have an API key.
  3. You need to create a custom log integration and put the unindexable as the dataset name, so it will allow the agent to write to that index.

I think that is not a good UX, not very straightforward and very error prone. I would hope that the shipper / agent is responsible directly to enable this feature and with a single toggle out of Kibana I can enable a logs-unindexable, metrics-unindexable, automatically and no need for manual intervention.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

No branches or pull requests

2 participants