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

[cmd/telemetrygen] migrate log to use go sdk #18902

Closed
fatsheep9146 opened this issue Feb 24, 2023 · 3 comments · Fixed by #34104
Closed

[cmd/telemetrygen] migrate log to use go sdk #18902

fatsheep9146 opened this issue Feb 24, 2023 · 3 comments · Fixed by #34104
Labels
cmd/telemetrygen telemetrygen command enhancement New feature or request never stale Issues marked with this label will be never staled and automatically removed priority:p3 Lowest

Comments

@fatsheep9146
Copy link
Contributor

Component(s)

cmd/telemetrygen

Is your feature request related to a problem? Please describe.

For now, since the log of go sdk is now frozen. So the telemetrygen can only use pdata and other package to create log data.

When go log sdk is ready, we could check whether it is sufficient for telemetrygen to generate log data.

Describe the solution you'd like

None

Describe alternatives you've considered

No response

Additional context

No response

@fatsheep9146 fatsheep9146 added enhancement New feature or request needs triage New item requiring triage labels Feb 24, 2023
@github-actions github-actions bot added the cmd/telemetrygen telemetrygen command label Feb 24, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@atoulme atoulme added priority:p3 Lowest and removed needs triage New item requiring triage labels Mar 7, 2023
@github-actions
Copy link
Contributor

github-actions bot commented May 8, 2023

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.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label May 8, 2023
@mx-psi mx-psi removed the Stale label May 8, 2023
@github-actions
Copy link
Contributor

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.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jul 10, 2023
@mx-psi mx-psi removed the Stale label Jul 10, 2023
@codeboten codeboten added the never stale Issues marked with this label will be never staled and automatically removed label Aug 18, 2023
codeboten added a commit that referenced this issue Jul 16, 2024
This updates telemetrygen to use the otel go SDK for logs instead of
pdata for the logging signal. This aligns with the tracing and metrics
signal.

Fixes #18902

---------

Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
Co-authored-by: Matthew Wear <matthew.wear@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmd/telemetrygen telemetrygen command enhancement New feature or request never stale Issues marked with this label will be never staled and automatically removed priority:p3 Lowest
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants