-
Notifications
You must be signed in to change notification settings - Fork 2
Datadogfleetautomation extension POC #5272
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
base: prod
Are you sure you want to change the base?
Conversation
extension/datadogfleetautomationextension/fleetautomationextension.go
Outdated
Show resolved
Hide resolved
extension/datadogfleetautomationextension/fleetautomationextension.go
Outdated
Show resolved
Hide resolved
extension/datadogfleetautomationextension/fleetautomationextension.go
Outdated
Show resolved
Hide resolved
extension/datadogfleetautomationextension/fleetautomationextension_test.go
Outdated
Show resolved
Hide resolved
extension/datadogfleetautomationextension/fleetautomationextension.go
Outdated
Show resolved
Hide resolved
extension/datadogfleetautomationextension/fleetautomationextension.go
Outdated
Show resolved
Hide resolved
Addressing the golint violations |
cb116ca
to
34ae621
Compare
34ae621
to
48930cd
Compare
extension/datadogfleetautomationextension/fleetautomationextension.go
Outdated
Show resolved
Hide resolved
// Copyright The OpenTelemetry Authors | ||
// SPDX-License-Identifier: Apache-2.0 | ||
|
||
package datadogfleetautomationextension // import "github.com/open-telemetry/opentelemetry-collector-contrib/extension/datadogfleetautomationextension" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
may be name it datadogfaextension
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't care that strongly about it; should it be datadogfaextension, datadogrcextension, or just datadogextension @mx-psi @dineshg13 @ancostas
extension/datadogfleetautomationextension/fleetautomationextension.go
Outdated
Show resolved
Hide resolved
48930cd
to
9effea7
Compare
extension/datadogfleetautomationextension/fleetautomationextension.go
Outdated
Show resolved
Hide resolved
extension/datadogfleetautomationextension/fleetautomationextension.go
Outdated
Show resolved
Hide resolved
extension/datadogfleetautomationextension/fleetautomationextension.go
Outdated
Show resolved
Hide resolved
7bb0557
to
3176d4f
Compare
3176d4f
to
e7ed96a
Compare
74751e2
to
9fdf059
Compare
agreed. I will break it up into the 2-3 PRs that the collector-contrib repo requires, at a minimum. https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-new-components |
leaving open for now to use as a reference for proposing the separate PRs into upstream contrib |
a7f57cf
to
38837c8
Compare
Description
initial POC for Datadog Fleet Automation Extension
Link to tracking issue
Fixes Jira OTEL-2445
Testing
Full unit testing (todo: will open a card to write a few integration tests)
Documentation
Have only written a barebones README.md to pass checks; figured that would make sense to do after we make changes or add/remove/adjust functionality.
Additional notes
Does not yet send the new, third payload type. I am working on a separate branch to add that payload and am planning to open a second PR after this one is accepted to our fork