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

[receiver/k8sobjects] Extract resource attributes from payload for events #27069

Conversation

TylerHelmuth
Copy link
Member

Description:
Updates the k8sobjects recevier to be able to extract meaningful kubernetes resource attributes from events.

Link to tracking Issue:

Related to #24242

Testing:

Added unit tests and tested locally

Documentation:

@TylerHelmuth TylerHelmuth requested a review from a team September 21, 2023 22:21
@TylerHelmuth TylerHelmuth changed the title [receiver/k8sobjects] Extract resource attributes from payload [receiver/k8sobjects] Extract resource attributes from payload for events Sep 22, 2023
@TylerHelmuth TylerHelmuth force-pushed the k8sobjects-extract-attributes branch from 5af5cfd to 5c58174 Compare September 29, 2023 21:54
@TylerHelmuth
Copy link
Member Author

/cc @jinja2

@TylerHelmuth TylerHelmuth force-pushed the k8sobjects-extract-attributes branch from f08287a to cd15e30 Compare October 5, 2023 17:49
@jinja2
Copy link
Contributor

jinja2 commented Oct 5, 2023

tests are passing now, PR lgtm!

@sathieu
Copy link

sathieu commented Oct 10, 2023

@TylerHelmuth Would you also change object.type (Normal or Warning) to a severity ?

Also I'm wondering if object.reason may be added as a label.

@TylerHelmuth
Copy link
Member Author

@sathieu good questions. Can you ask in the issue? That is the place we're collecting potential attributes.

@TylerHelmuth
Copy link
Member Author

I am going to close this for now as we need to have another discussion with the semconv sig to clarify which Kinds have a semantic convention for name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants