Skip to content

Implement Windows Service Receiver #38619

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.

Sign up for GitHub

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

Jump to bottom
Open
1 of 4 tasks
shalper2 opened this issue Mar 13, 2025 · 2 comments · May be fixed by #40043
Open
1 of 4 tasks

Implement Windows Service Receiver #38619

shalper2 opened this issue Mar 13, 2025 · 2 comments · May be fixed by #40043
Labels
receiver/windowsservice

Comments

@shalper2
Copy link
Contributor

shalper2 commented Mar 13, 2025 •
edited
Loading

Component(s)

receiver/windowsservice

Describe the issue you're reporting

The Windows Service Receiver is an in-development component which is attempting to reach parity with the telegraf input of the same name. This issue is meant to track the implementation of the receiver component as it graduates from development to alpha status. Below is a list of component pieces that are required before graduation.

  • Configuration and metadata information
  • Detailed README
  • Core functionality: scraping and emission of metric signals
  • Test code (should be written concurrently with other component pieces)
@shalper2 shalper2 added the needs triage New item requiring triage label Mar 13, 2025
@crobert-1 crobert-1 mentioned this issue Mar 13, 2025
Closed
@github-actions GitHub Actions
Copy link
Contributor

Pinging code owners for receiver/windowsservice: @pjanotti @shalper2. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

@crobert-1
Copy link
Member

Issue filed by code owner, removing needs triage.

@crobert-1 crobert-1 removed the needs triage New item requiring triage label Mar 13, 2025
@github-actions github-actions bot mentioned this issue Mar 18, 2025
Closed
@shalper2 shalper2 mentioned this issue Mar 20, 2025
Merged
atoulme pushed a commit that referenced this issue Mar 25, 2025
@shalper2
[receiver/windowsservice] 38619 add config (#38827)
fa9afe8 
#### Description
Adds a `config.go` to the Windows Service Receiver. This is the first
piece in the component implementation and will work as the foundation on
which the rest of the components are to be implemented.

At this stage there is no custom validation code for the config so
`config_test` will remain empty.

#### Link to tracking issue
Related to
[38619](#38619)

#### Testing
No custom validation for configuration at this stage.

#### Documentation
configuration details are documented in the `README.yaml`
@shalper2 shalper2 mentioned this issue Apr 14, 2025
Closed
Fiery-Fenix pushed a commit to Fiery-Fenix/opentelemetry-collector-contrib that referenced this issue Apr 24, 2025
@shalper2 @Fiery-Fenix
[receiver/windowsservice] 38619 add config (open-telemetry#38827)
4976333 
#### Description
Adds a `config.go` to the Windows Service Receiver. This is the first
piece in the component implementation and will work as the foundation on
which the rest of the components are to be implemented.

At this stage there is no custom validation code for the config so
`config_test` will remain empty.

#### Link to tracking issue
Related to
[38619](open-telemetry#38619)

#### Testing
No custom validation for configuration at this stage.

#### Documentation
configuration details are documented in the `README.yaml`
@shalper2 shalper2 linked a pull request May 13, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
receiver/windowsservice
Projects
None yet
Milestone
No milestone
2 participants
@crobert-1 @shalper2