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

Handle user.name/system_cmdline if not present #42

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

ishleenk17
Copy link
Contributor

In some scenarios, we have observed that the user.name is not fetched since ots corresponding OTEL metric(process.owner) is not present.
But the absence of user.name leads to the process tab not working in Curated UI's. Hecne adding default value of "undefined" in case not present.
The same is done for system_cmdline for the same reasons

@ishleenk17 ishleenk17 requested a review from lahsivjar July 8, 2024 11:26
@ishleenk17 ishleenk17 self-assigned this Jul 8, 2024
@ishleenk17 ishleenk17 requested a review from a team as a code owner July 8, 2024 11:26
Copy link
Contributor

@lahsivjar lahsivjar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I am slightly concerned that this may cause some confusion with the users and we may be better off dropping such data but I guess with PID populated it would still be beneficial.

@ishleenk17
Copy link
Contributor Author

but I guess with PID populated it would still be beneficial.

Yes, if we drop the document, no information about the process is there. With this, at least the user would know that a process with a particular pid is present in their system.

@ishleenk17 ishleenk17 merged commit 996ceaa into elastic:main Jul 8, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants