Skip to content
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

feat(otel): add integrations components #5608

Conversation

andrzej-stencel
Copy link
Contributor

@andrzej-stencel andrzej-stencel commented Sep 24, 2024

This is a "proof of concept" draft pull request, not to be merged.

It adds the following OTel Collector components, as implemented in elastic/opentelemetry-collector-components#96:

  • config_integrations extension
  • file_integrations extension
  • integration receiver
  • integration processor

I was able to build the agent binary using the command:

go build .

After that, I ran the agent in OTel mode with the following command:

./elastic-agent otel --config config.yaml

with the following config.yaml file:

exporters:
  debug:

extensions:
  config_integrations:
  file_integrations:
    path: .

processors:
  integration:
    name: integ2

receivers:
  integration:
    name: integ1

service:
  extensions:
    - config_integrations
    - file_integrations
  pipelines:
    logs:
      exporters:
        - debug
      processors:
        - integration
      receivers:
        - integration

@andrzej-stencel andrzej-stencel requested a review from a team as a code owner September 24, 2024 15:55
@andrzej-stencel andrzej-stencel marked this pull request as draft September 24, 2024 15:56
Copy link
Contributor

mergify bot commented Sep 24, 2024

This pull request does not have a backport label. Could you fix it @andrzej-stencel? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit

Copy link
Contributor

mergify bot commented Sep 24, 2024

backport-v8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Sep 24, 2024
@andrzej-stencel andrzej-stencel added skip-changelog and removed backport-8.x Automated backport to the 8.x branch with mergify labels Sep 25, 2024
Copy link
Contributor

mergify bot commented Sep 25, 2024

This pull request does not have a backport label. Could you fix it @andrzej-stencel? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit

Copy link
Contributor

mergify bot commented Sep 25, 2024

backport-v8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Sep 25, 2024
Copy link
Contributor

mergify bot commented Oct 1, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b add-integrations-components upstream/add-integrations-components
git merge upstream/main
git push upstream add-integrations-components

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify skip-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant