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

[Fleet] add back monitoring for agentless policies #191635

Merged
merged 2 commits into from
Aug 29, 2024

Conversation

juliaElastic
Copy link
Contributor

Added back agent monitoring on agentless policies as requested. It was incorrectly removed in #189612

@juliaElastic juliaElastic added the release_note:skip Skip the PR/issue when compiling release notes label Aug 28, 2024
@juliaElastic juliaElastic self-assigned this Aug 28, 2024
@juliaElastic juliaElastic requested review from a team as code owners August 28, 2024 13:57
@botelastic botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Aug 28, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@obltmachine
Copy link

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@@ -848,7 +848,7 @@ describe('When on the package policy create page', () => {

expect(sendCreateAgentPolicy).toHaveBeenCalledWith(
expect.objectContaining({
monitoring_enabled: [],
monitoring_enabled: ['logs', 'metrics', 'traces'],
Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks @juliaElastic!
I don't think we had traces included originally

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Traces were recently added in this pr: #189908
And the logic takes all values:

monitoring_enabled: Object.values(dataTypes),

I can remove traces if we don't want it in agentless.

Copy link
Contributor

Choose a reason for hiding this comment

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

@amirbenun I remember you looked into it.
Do you think we need traces enabled?

Copy link
Contributor

Choose a reason for hiding this comment

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

Since I am not familiar with that I am not sure how it's going to affect the user.
I think it's best to have only logs and metrics which were both tested and we might add traces in the future.

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

@opauloh opauloh Aug 28, 2024

Choose a reason for hiding this comment

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

Traces may help with [Cloud Security] [Agentless] Include X-Request-ID header in all Agentless API requests and logs

logs is mainly what we need for the correlation, looking at what traces offers, it can help users detect issues with the communication with agentless, It could be useful during the agentless beta, however, I am not sure if traces would expose internal services to the users such as the agentless endpoints and requests/responses, which is something we had not initially planned.

So I tend to agree with @amirbenun to enable only logs and metrics for now and evaluate if we can enable traces in the future

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated with only logs and metrics as requested.

Copy link
Contributor

@criamico criamico left a comment

Choose a reason for hiding this comment

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

LGTM

@juliaElastic
Copy link
Contributor Author

/ci

Copy link
Contributor

@seanrathier seanrathier left a comment

Choose a reason for hiding this comment

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

Assuming the trace discussion is resolved, I approve.

@@ -848,7 +848,7 @@ describe('When on the package policy create page', () => {

expect(sendCreateAgentPolicy).toHaveBeenCalledWith(
expect.objectContaining({
monitoring_enabled: [],
monitoring_enabled: ['logs', 'metrics', 'traces'],
Copy link
Contributor

Choose a reason for hiding this comment

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

@juliaElastic
Copy link
Contributor Author

/ci

@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
fleet 1.8MB 1.8MB +16.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @juliaElastic

@juliaElastic juliaElastic merged commit 2678101 into elastic:main Aug 29, 2024
22 checks passed
@kibanamachine kibanamachine added v8.16.0 backport:skip This commit does not require backporting labels Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Fleet Team label for Observability Data Collection Fleet team v8.16.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants