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

[exporter/sematext] New component: Sematext Exporter #37161

Open
wants to merge 42 commits into
base: main
Choose a base branch
from

Conversation

AkhigbeEromo
Copy link

Description

First PR of New component: Sematext Exporter.

Link to tracking issue

#36465

Copy link
Member

@andrzej-stencel andrzej-stencel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great start! Perhaps we can simplify the first PR by removing the configuration?

.chloggen/sematextexporter-new-component.yaml Outdated Show resolved Hide resolved
exporter/sematextexporter/metadata.yaml Outdated Show resolved Hide resolved
exporter/sematextexporter/metadata.yaml Outdated Show resolved Hide resolved
exporter/sematextexporter/README.md Show resolved Hide resolved
usLogsEndpoint = "https://logsene-receiver.sematext.com"
)

type Config struct {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please review (if you haven't already) the docs for adding new components:

I propose to split the code in the following way:

  • First PR: empty Config struct
  • Second PR: metrics config and functionality (initial minimum functionality if possible, to make reviewing easier)
  • Third PR: logs config and functionality (initial minimum functionality if possible, to make reviewing easier)

I believe this will help greatly with the reviews.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this okay? @andrzej-stencel

@atoulme atoulme added the Accepted Component New component has been sponsored label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Component New component has been sponsored
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants