-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[processor/schematransformerprocessor] Initial PR #8371
[processor/schematransformerprocessor] Initial PR #8371
Conversation
6ac440e
to
5e039b9
Compare
I have avoided adding any implementation detail here to keep the high level PR in, this PR can should be fine to merge in and run (since it will only just validate the configuration, passthrough exactly what it receives). Not entirely sure how to resolve the issue within the After this initial PR goes in, the next logical flow I have in mind is:
|
b1483ad
to
e5136ea
Compare
You'll also need to add a |
a7abf33
to
b532668
Compare
Thanks @Aneurysm9, it looks like it managed to get past the |
Nobody move... the load tests somehow passed. @codeboten , @jpkrohling, @Aneurysm9 , if you have time to have a look over this pull request? |
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.
Sorry about that, but we just had a new release, so, the go.mod/sum files here have to be changed.
// See the License for the specific language governing permissions and | ||
// limitations under the License. | ||
|
||
package schematransformerprocessor_test |
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.
Are tests coming to this file in the next PR?
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.
Yes, since the transformer is currently just an empty struct, I wasn't exactly sure how the transformer would look like so I didn't want to burden reviewers with more work than required.
processor/schematransformerprocessor/internal/schema/indentifer.go
Outdated
Show resolved
Hide resolved
processor/schematransformerprocessor/internal/schema/indentifer_test.go
Outdated
Show resolved
Hide resolved
f6d815f
to
73551e6
Compare
Lame, the loadtest flaked out on me. |
81c7ae5
to
c1006e6
Compare
The stairs have aligned once again! Once I get a chance, I will have a stab to see if I can help reduce the flake in the those tests. |
processor/schematransformerprocessor/internal/schema/indentifer.go
Outdated
Show resolved
Hide resolved
processor/schematransformerprocessor/internal/schema/indentifer_test.go
Outdated
Show resolved
Hide resolved
c1006e6
to
8e293cd
Compare
b19fafd
to
e2c8a9b
Compare
Sorry @tigrannajaryan, Finally got a chance to get back to this :) |
5b48af9
to
8c4d72f
Compare
401ff1b
to
d364da8
Compare
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.
Just a couple of suggestions and questions. Please add a note about what constitutes a family in the readme file, it can be a copy paste of the definition in the schema overview, but i think it will help users of this processor
processor/schemaprocessor/README.md
Outdated
|
||
## Caching Schema Translation Files | ||
|
||
In order to improve effeicency of the processor, the `precache` option allows the processor to start downloading and preparing |
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.
In order to improve effeicency of the processor, the `precache` option allows the processor to start downloading and preparing | |
In order to improve efficency of the processor, the `precache` option allows the processor to start downloading and preparing |
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.
Not sure if that was a mistake, but misspell
is reporting it as a typo.
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.
LGTM. Just clarify to users what happens when conflicting versions of the schemas are used, and fix a couple of typos.
Retracting, due to the changelog changes.
Sorry, I'm retracting my approval because of the unwanted changes to the changelog. |
4dfbbae
to
8ada9d1
Compare
9cd8112
to
92b91ad
Compare
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.
Apart from the couple of typos, LGTM!
92b91ad
to
6610e95
Compare
6610e95
to
2be9365
Compare
@jpkrohling 🙏🏽 Could I get this merged please? |
I tried to update this branch, but got an error :-( The changelog needs updating, and there's a conflict with the go.sum versions. Once this is fixed and the build is green, I'll merge (if this happens today). |
@MovieStoreGuy ping me when the conflicts are resolved, I will merge. |
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.
Thanks for addressing my comments, please rebase and we'll get this merge right away
2be9365
to
64ccae4
Compare
This is the initial commit into the collector to add in the component to help enforce a standard semantic convention for all signals.
64ccae4
to
5f83e82
Compare
Thank you @MovieStoreGuy |
**Description:** As part of the [accepted specification](https://github.com/open-telemetry/opentelemetry-specification/blob/e16e1a781bdf62a8fcfa1a12963844749de23e7a/specification/schemas/overview.md#collector-assisted-schema-transformation), there needs to be a processor within the collector that is able to allow for transformations of semantic convention versions . This is my initial draft, I wrote this before https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/8344/files shared their solution to it. **Link to tracking Issue:** open-telemetry#8495 Original raised in the collector but should be shifted to the contrib a I can tell. **Testing:** It currently does nothing and there is the initial testing set up within the components. **Documentation:** Added a minimal README, will expand upon it once more work has been added to the collector.
@MovieStoreGuy do you plan to continue working on the schema processor? |
Yes, sorry. I have been meaning to get back into it but I have been working on rollout infra changes to adopt the otel collector for resource metrics, so that has taken a lot of brain space atm. I intend to get back to this this week |
Sounds good, thanks! |
Description:
As part of the accepted specification, there needs to be a processor within the collector that is able to allow for transformations of semantic convention versions . This is my initial draft, I wrote this before https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/8344/files shared their solution to it.
Link to tracking Issue:
#8495
Original raised in the collector but should be shifted to the contrib a I can tell.
Testing:
It currently does nothing and there is the initial testing set up within the components.
Documentation:
Added a minimal README, will expand upon it once more work has been added to the collector.