-
Notifications
You must be signed in to change notification settings - Fork 147
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
[otel] add geoip processor component #6134
base: main
Are you sure you want to change the base?
Conversation
This pull request does not have a backport label. Could you fix it @rogercoll? 🙏
|
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
@cmacknz Should we skip changelog fragments for this PR? |
Didn't notice that, this should have a changelog. If EDOT collector has a separate changelog for whatever reason (I'm not aware that it does) it could go there instead, but this is a feature addition to EDOT collector so we should document it. |
Quality Gate passedIssues Measures |
This pull request is now in conflicts. Could you fix it? 🙏
|
What does this PR do?
Adds the GeoIP OpenTelemetry processor into the agent. After adding the import into the
internal/pkg/otel/components.go
the following commands have been used to follow the project style:$ go mod tidy; mage fmt; mage update; mage notice;
Why is it important?
It can be used in OpenTelemetry configurations, for example, in a Nginx Ingress controller integration.
Checklist
./changelog/fragments
using the changelog tool