New component: Filebeat Receiver

[shrenikjain38]

The purpose and use-cases of the new component

This is a receiver which is able to accept lumberjack protocol events from filebeat agent.

Impact/Why is it needed:

1. Support for ingesting logs from one of the most widely adopted log collection agent i.e., filebeat.
2. Complimentary addition alongside currently existing fluentforward receiver which is able to receive log data from fluentbit.

Implementation Details:

1. It includes a go-lumber server which supports both lumberjack v1 and v2.
2. A translation layer which converts lumberjack events to logs in otlp log format, it adds the filebeat event fields apart from "message" field as resource attributes in otlp log object.

Example configuration for the component

receivers:
  filebeat:
    endpoint: "0.0.0.0:5044"
    tls:
      ca_file: "/abc"
      cert_file: "/abcd"
      key_file: "/abcde"
      min_version: "abcdef"
      max_version: "abcdefg"
      reload_interval: 20

Telemetry data types supported

Logs

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am proposing to contribute this as a representative of the vendor.

Sponsor (optional)

No response

Additional context

No response

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[atoulme]

Discussed in SIG 6/14: this is not a vendor specific component as understood by the definition of a commercial vendor backing.

[shivanshuraj1333]

Cross-linking the relevant issue from elastic beats: elastic/beats#32549

@atoulme what you think would be the best approach to take here?
Implement Filebeat Receiver in opentelemetry-collector-contrib as this issue suggests or have an exporter in Elastic which exports Elastic data in OTLP format following OTLP log data model.

For the 2nd approach we already have some implementation which does the translation of logs data from Elastic format to OTLP log data model.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.