-
Notifications
You must be signed in to change notification settings - Fork 195
[otel] Add Logstash exporter to OTel mode #10137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This pull request does not have a backport label. Could you fix it @edmocosta? 🙏
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Is the plan for this exporter to always live in the beats codebase, rather than opentelemetry-collector-components?
Yes, it will live in the beats repository, and there's no short-term plans for moving it into the opentelemetry-collector-components. It was made to only work with beats receivers, and is highly coupled to the beats's codebase. |
|
* upstream: (505 commits) Update journald tests now that Filebeat supports watching folders (#10131) [deploy/kubernetes]: add info about hostPID for Universal Profiling (#10173) Fall back to process runtime if otel runtime is unsupported (#10087) Conditionall check for ms_tls13kdf build tag (#10160) [docs][edot] add entry for profiles (#10163) edot/docs: add support for profiles (#10146) Add Logstash exporter (#10137) Add back publish to serverless. (#10159) Improve Integration test documentation (#10155) Fix multiarch service image push from main to serverless (#10129) Forward migrate action to endpoint (#9801) Comment out check for ms_tls13kdf tag for FIPS-capable binaries (#10148) [otel] add receivers: apache, iis, mysql, postgresql, sqlserver v0.135.0 (#9344) Add k8sevents receiver in kube-stack (#10086) feat: emit system resource metrics for EDOT subprocess (#10003) [AutoOps] Configure OTel Exporter to Send Maximum-sized Batches (#10126) keep enrollment token when replacing data with signed (#10115) Revert "Publish `elastic-agent-service` container directly to serverless from main (#9583)" (#10127) Add agent_policy_id and policy_revision_idx to checkin requests (#9931) remove resource/k8s processor and use k8sattributes processor for service attributes (#10108) ...
What does this PR do?
Adds the Logstash exporter as an OTel component. This exporter only works with Beats OTel receivers.
Why is it important?
It allows beats receiver to send data (ECS) to Logstash.
Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
No impact on existing users / configurations.
How to test this PR locally
Use something like the following as
otel.yml
, and runelastic-agent otel --config otel.yml
This will run the beat receiver, which will produce one event.
The event should be sent to the local Logstash instance you specify in the
logstash
section.To run Logstash:
bin/logstash -e "input { beats { port => 5044 } } output { stdout { } }"
Related issues
Questions to ask yourself