[EDR Workflows][API] Gate Agent Tamper Protection setting on Agent Policy Settings #174400

szwarckonrad · 2024-01-05T20:33:23Z

This PR is part of an effort to limit EDR Workflow features to the Endpoint Complete tier on serverless and focuses on server skde part of gating Agent Tamper Protection.

Related PRs:

#174278
#175129

We decided to stick with the existing Fleet privileges for this component, and no extra changes are needed RBAC wise (confirmed with @roxana-gheorghe).

Plugin/Policy Watcher Changes:
To monitor agent policies for a downgrade in tier (from complete to essentials) and disable agent protections if enabled, the following steps have been taken:

A new app feature, endpoint_agent_tamper_protection, has been introduced and linked to the endpoint:complete tier.
An additional method, bumpRevision, has been exposed in the fleet's agent policy service. This method utilizes the service's internal update function and includes a disable_protection flag, allowing it to be used without further modifications.
The security solution side calls this method upon successful fleet plugin setup. If the endpoint_agent_tamper_protection app feature is not enabled, it retrieves all agent policies with is_protected: true and updates these policies with is_protected: false.

API Changes:
To respond to attempts to activate agent protection via the API by users on the Essentials tier, the following steps have been taken:

External callback functionality has been added to the agentPolicy service, following the implementation in packagePolicy.
Update and create agent policy callbacks have been registered in the security solution. These callbacks check for the enabled status of the endpoint_agent_tamper_protection app feature. If disabled, the callback throws an error.
External callback execution has been added to the update and create methods in agent policy route handlers.

szwarckonrad · 2024-01-16T16:04:15Z

/ci

…fix'

szwarckonrad · 2024-01-25T13:53:30Z

/ci

szwarckonrad · 2024-01-25T15:37:08Z

/ci

szwarckonrad · 2024-01-25T20:55:35Z

/ci

szwarckonrad · 2024-01-26T09:36:21Z

/ci

…ed-agent-tamper-api

szwarckonrad · 2024-01-26T10:32:55Z

x-pack/plugins/fleet/server/services/agent_policy.ts

@@ -254,7 +294,7 @@ class AgentPolicyService {
      id: options.id,
      savedObjectType: AGENT_POLICY_SAVED_OBJECT_TYPE,
    });
-
+    await this.runExternalCallbacks('agentPolicyCreate', agentPolicy);
    this.checkTamperProtectionLicense(agentPolicy);


Can be moved to sec sol side to an external callback

szwarckonrad · 2024-01-26T10:33:09Z

x-pack/plugins/fleet/server/services/agent_policy.ts

    this.checkTamperProtectionLicense(agentPolicy);
    await this.checkForValidUninstallToken(agentPolicy, id);


Can be moved to sec sol side to an external callback

semd

The AppFeature config LGTM

paul-tavares

Did not run it locally, but went through the code and left feedback.

Also - could you add cypress tests on our end that can validate the API responds as appropriate for the different PLIs?

paul-tavares · 2024-01-30T17:30:37Z

x-pack/plugins/fleet/server/types/extensions.ts

+  | ExternalCallbackAgentPolicyCreate
+  | ExternalCallbackAgentPolicyUpdate;
+
+export type ExternalCallbackType = ExternalCallback | ExternalCallbackAgentPolicy;


Why create this? why not just add The two new types directly to the ExternalCallback type, which is already a union of all available external callbacks that can be registered.

Ultimately, I'll defer to the Fleet team on this, but this (IMO 😄 ) feels unnecessary and will just cause more union to be used in other places of the code

Excellent question! Removed as it was a leftover from poc phase I did ;). Thanks!

paul-tavares · 2024-01-30T17:33:59Z

x-pack/plugins/fleet/server/plugin.ts

@@ -218,7 +220,7 @@ export interface FleetStartContract {
   * Register callbacks for inclusion in fleet API processing
   * @param args
   */
-  registerExternalCallback: (...args: ExternalCallback) => void;
+  registerExternalCallback: (...args: ExternalCallback | ExternalCallbackAgentPolicy) => void;


See my comment further below. This union can be avoided by just adding the new types to the existing ExternalCallback type.

paul-tavares · 2024-01-30T17:38:32Z

x-pack/plugins/security_solution/server/endpoint/migrations/turn_off_agent_policy_features.ts

+  }
+
+  log.info(
+    `App feature [${AppFeatureSecurityKey.endpointAgentTamperProtection}] is disabled. Checking endpoint integration policies for compliance`


is this message accurate? I think it should say "Checking fleet agent policies" not endpoint integrations

Nice catch, changed.

paul-tavares · 2024-01-30T17:43:27Z

x-pack/plugins/security_solution/server/endpoint/migrations/turn_off_agent_policy_features.ts

+    await pMap(updates, async (update) => {
+      try {
+        return await agentPolicyService.bumpRevision(internalSoClient, esClient, update.id, {
+          user: { username: 'elastic' } as AuthenticatedUser,
+          removeProtection: true,
+        });
+      } catch (error) {
+        policyUpdateErrors.push({ error, id: update.id });
+      }
+    });


this is not very efficient for an env. having large amount of policies. Can we add a method to the agentPolicyService that can do bulk updates instead doing one-by-one?

Also - I will be merging a PR soon that will allow you to easily create an AsynIterator that could further improve the performance around the updates that need to be done.

Agree that this is not efficient. I saw it being done this way in couple places though, example. Gonna reach out to Fleet team and ask if there is a reason AgentPolicySrvc doesn't expose bulkUpdate.

Agree about doing this in bulk so we don't have to update the SO one by one. That being said, there is no method on agentPolicySerice that supports bulk currently. If Fleet team agrees on, we can add a new one trying to mimic what the package policy service does for bulkUpdate here: https://github.com/elastic/kibana/blob/main/x-pack/plugins/fleet/server/services/package_policy.ts#L942

As this not only updates the SO and it does a lot of other stuff before doing the final update, it might be complex but worth if we can do it and speed this up.

@paul-tavares @kpollich
Do you think it would be better to add bulkUpdate in the current PR or create a new PR and issue just for that?

I'm good with that @szwarckonrad . Thanks

paul-tavares · 2024-01-30T17:45:07Z

x-pack/plugins/security_solution/server/endpoint/migrations/turn_off_agent_policy_features.ts

+      policyUpdateErrors.forEach((e) =>
+        logger.error(`Policy [${e.id}] failed to update due to error: ${e.error}`)
+      );


Could you output only 1 error that includes all of the messages instead of individual message?

paul-tavares · 2024-01-30T17:49:43Z

x-pack/plugins/security_solution/server/endpoint/migrations/turn_off_agent_policy_features.ts

+      logger.error(`Done. ${policyUpdateErrors.length} out of ${updates.length}`);
+      policyUpdateErrors.forEach((e) =>
+        logger.error(`Policy [${e.id}] failed to update due to error: ${e.error}`)
+      );


I would clarify the message here and also, there is no need to output one log entry per errror encountered.

Here is my suggestion:

logger.error( `Done - ${policyUpdateErrors.length} out of ${updates.length} were successful. Errors encountered:\n${ policyUpdateErrors.map(e => `Policy [${e.id}] failed to update due to error: ${e.error}`).join('\n') }` );

Way better, thanks :)

paul-tavares · 2024-01-30T17:51:32Z

x-pack/plugins/security_solution/server/fleet_integration/fleet_integration.test.ts

@@ -382,6 +384,123 @@ describe('ingest_integration tests ', () => {
    });
  });

+  describe('agent policy update callback', () => {
+    it('AppFeature disabled - returns an error if higher tier features are turned on in the policy', async () => {
+      const logger = loggingSystemMock.create().get('ingest_integration.test');


There is quite a bit of duplication of test setup between all of these tests... perhaps consolidate some of that into describe() level variables that are initialized via beforeEach()?

Cleaned up.

paul-tavares · 2024-01-30T17:57:39Z

x-pack/plugins/security_solution/server/fleet_integration/fleet_integration.ts

+      agentPolicy.is_protected &&
+      !appFeatures.isEnabled(AppFeatureSecurityKey.endpointAgentTamperProtection)
+    ) {
+      const error = new Error('Agent Tamper Protection requires Complete Endpoint Security tier');


Suggestion: do not reference the tier required in serverless in order to use this functionality. Instead just return a more generic message like Agent Tamper Protection is not allowed in current environment. If you like, you could log a message to the kibana logs indicating that the deployment does not meet the needed tier, but I would not return that back in the API (this message is being returned in the API, correct?)

Also - what HTTP code is returned when this is triggered?

It should be a 403 - I think Fleet has a way for us to defined the return code on the Error that is returned by an external callback, so you can use that to set it as such.

Agent Tamper Protection is not allowed in current environment sounds good. It returns 403 and Ive added cypress'

juliaElastic

Fleet changes LGTM

tomsonpl

LGTM!

paul-tavares

Looks good. I left a comment, but its optional and should not hold this PR back. 👍

paul-tavares · 2024-02-01T16:50:57Z

x-pack/plugins/security_solution/server/endpoint/migrations/turn_off_agent_policy_features.ts

+    await pMap(updates, async (update) => {
+      try {
+        return await agentPolicyService.bumpRevision(internalSoClient, esClient, update.id, {
+          user: { username: 'elastic' } as AuthenticatedUser,
+          removeProtection: true,
+        });
+      } catch (error) {
+        policyUpdateErrors.push({ error, id: update.id });
+      }
+    });


I'm good with that @szwarckonrad . Thanks

paul-tavares · 2024-02-01T16:54:02Z

x-pack/plugins/security_solution/server/fleet_integration/fleet_integration.ts

+  // Agent Policy Service will check for apiPassThrough and rethrow. Route handler will check for statusCode and overwrite.
+  agentTamperProtectionUnavailableError.statusCode = 403;
+  agentTamperProtectionUnavailableError.apiPassThrough = true;
+  logger.error('Agent Tamper Protection requires Complete Endpoint Security tier');


This message could be improved for debugging purposes by including the agent policy ID (and maybe name as well) in the error log message. so that we get an idea which one triggered the issue.

@roxana-gheorghe

…icy Settings (#174278) This PR is part of an effort to limit EDR Workflow features to the Endpoint Complete tier on serverless and focuses on UI part of gating Agent Tamper Protection. Related PRs: - [Agent Tamper Protection API](#174400) - [Protection updates](#175129) Currently, the Agent tamper protection switch is in Fleet's agent policy settings. Right now (for ESS and Serverless), we only control access to this field with a license check (platinum). This PR adds an extra check for AppFeature, which is included in the Complete tier PLI config. We decided to stick with the existing Fleet privileges for this component, and no extra changes are needed RBAC wise (confirmed with @roxana-gheorghe). Changes: 1. Added `endpointAgentTamperProtection` appFeature and linked it to the endpoint:complete tier. 2. Made an upselling component and registered it with the Upselling Service. 3. Passed the upselling component to Fleet using UIExtension. 4. Added Cypress end-to-end coverage for Essentials showing the upselling component and Complete showing the form component. ![Screenshot 2024-01-24 at 15 52 17](https://github.com/elastic/kibana/assets/29123534/6cdc3197-7bd0-4607-9323-ae4318493653)

# Conflicts: # x-pack/plugins/security_solution/server/fleet_integration/fleet_integration.ts

kibana-ci · 2024-02-01T21:35:41Z

💚 Build Succeeded

Buildkite Build
Commit: 527a332

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
`fleet`	1104	1109	+5

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
`fleet`	49	51	+2

Unknown metric groups

API count

id	before	after	diff
`fleet`	1222	1227	+5

History

💔 Build #190841 failed 06c9bc9
💛 Build #190591 was flaky 557791f
💔 Build #190492 failed b3c6937
💔 Build #190444 failed 63b86df
💛 Build #190115 was flaky b18a7b4

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

cc @szwarckonrad

@roxana-gheorghe

…icy Settings (elastic#174278) This PR is part of an effort to limit EDR Workflow features to the Endpoint Complete tier on serverless and focuses on UI part of gating Agent Tamper Protection. Related PRs: - [Agent Tamper Protection API](elastic#174400) - [Protection updates](elastic#175129) Currently, the Agent tamper protection switch is in Fleet's agent policy settings. Right now (for ESS and Serverless), we only control access to this field with a license check (platinum). This PR adds an extra check for AppFeature, which is included in the Complete tier PLI config. We decided to stick with the existing Fleet privileges for this component, and no extra changes are needed RBAC wise (confirmed with @roxana-gheorghe). Changes: 1. Added `endpointAgentTamperProtection` appFeature and linked it to the endpoint:complete tier. 2. Made an upselling component and registered it with the Upselling Service. 3. Passed the upselling component to Fleet using UIExtension. 4. Added Cypress end-to-end coverage for Essentials showing the upselling component and Complete showing the form component. ![Screenshot 2024-01-24 at 15 52 17](https://github.com/elastic/kibana/assets/29123534/6cdc3197-7bd0-4607-9323-ae4318493653)

@roxana-gheorghe

…licy Settings (elastic#174400) This PR is part of an effort to limit EDR Workflow features to the Endpoint Complete tier on serverless and focuses on server skde part of gating Agent Tamper Protection. Related PRs: elastic#174278 elastic#175129 **We decided to stick with the existing Fleet privileges for this component, and no extra changes are needed RBAC wise (confirmed with @roxana-gheorghe).** **Plugin/Policy Watcher Changes**: To monitor agent policies for a downgrade in tier (from complete to essentials) and disable agent protections if enabled, the following steps have been taken: 1. A new app feature, `endpoint_agent_tamper_protection`, has been introduced and linked to the `endpoint:complete` tier. 2. An additional method, `bumpRevision`, has been exposed in the fleet's agent policy service. This method utilizes the service's internal update function and includes a `disable_protection` flag, allowing it to be used without further modifications. 3. The security solution side calls this method upon successful fleet plugin setup. If the `endpoint_agent_tamper_protection` app feature is not enabled, it retrieves all agent policies with `is_protected: true` and updates these policies with `is_protected: false`. **API Changes**: To respond to attempts to activate agent protection via the API by users on the Essentials tier, the following steps have been taken: 1. External callback functionality has been added to the agentPolicy service, following the implementation in packagePolicy. 2. Update and create agent policy callbacks have been registered in the security solution. These callbacks check for the enabled status of the `endpoint_agent_tamper_protection` app feature. If disabled, the callback throws an error. 3. External callback execution has been added to the update and create methods in agent policy route handlers. --------- Co-authored-by: kibanamachine <[email protected]>

@roxana-gheorghe

…icy Settings (elastic#174278) This PR is part of an effort to limit EDR Workflow features to the Endpoint Complete tier on serverless and focuses on UI part of gating Agent Tamper Protection. Related PRs: - [Agent Tamper Protection API](elastic#174400) - [Protection updates](elastic#175129) Currently, the Agent tamper protection switch is in Fleet's agent policy settings. Right now (for ESS and Serverless), we only control access to this field with a license check (platinum). This PR adds an extra check for AppFeature, which is included in the Complete tier PLI config. We decided to stick with the existing Fleet privileges for this component, and no extra changes are needed RBAC wise (confirmed with @roxana-gheorghe). Changes: 1. Added `endpointAgentTamperProtection` appFeature and linked it to the endpoint:complete tier. 2. Made an upselling component and registered it with the Upselling Service. 3. Passed the upselling component to Fleet using UIExtension. 4. Added Cypress end-to-end coverage for Essentials showing the upselling component and Complete showing the form component. ![Screenshot 2024-01-24 at 15 52 17](https://github.com/elastic/kibana/assets/29123534/6cdc3197-7bd0-4607-9323-ae4318493653)

@roxana-gheorghe

…licy Settings (elastic#174400) This PR is part of an effort to limit EDR Workflow features to the Endpoint Complete tier on serverless and focuses on server skde part of gating Agent Tamper Protection. Related PRs: elastic#174278 elastic#175129 **We decided to stick with the existing Fleet privileges for this component, and no extra changes are needed RBAC wise (confirmed with @roxana-gheorghe).** **Plugin/Policy Watcher Changes**: To monitor agent policies for a downgrade in tier (from complete to essentials) and disable agent protections if enabled, the following steps have been taken: 1. A new app feature, `endpoint_agent_tamper_protection`, has been introduced and linked to the `endpoint:complete` tier. 2. An additional method, `bumpRevision`, has been exposed in the fleet's agent policy service. This method utilizes the service's internal update function and includes a `disable_protection` flag, allowing it to be used without further modifications. 3. The security solution side calls this method upon successful fleet plugin setup. If the `endpoint_agent_tamper_protection` app feature is not enabled, it retrieves all agent policies with `is_protected: true` and updates these policies with `is_protected: false`. **API Changes**: To respond to attempts to activate agent protection via the API by users on the Essentials tier, the following steps have been taken: 1. External callback functionality has been added to the agentPolicy service, following the implementation in packagePolicy. 2. Update and create agent policy callbacks have been registered in the security solution. These callbacks check for the enabled status of the `endpoint_agent_tamper_protection` app feature. If disabled, the callback throws an error. 3. External callback execution has been added to the update and create methods in agent policy route handlers. --------- Co-authored-by: kibanamachine <[email protected]>

@roxana-gheorghe

…icy Settings (elastic#174278) This PR is part of an effort to limit EDR Workflow features to the Endpoint Complete tier on serverless and focuses on UI part of gating Agent Tamper Protection. Related PRs: - [Agent Tamper Protection API](elastic#174400) - [Protection updates](elastic#175129) Currently, the Agent tamper protection switch is in Fleet's agent policy settings. Right now (for ESS and Serverless), we only control access to this field with a license check (platinum). This PR adds an extra check for AppFeature, which is included in the Complete tier PLI config. We decided to stick with the existing Fleet privileges for this component, and no extra changes are needed RBAC wise (confirmed with @roxana-gheorghe). Changes: 1. Added `endpointAgentTamperProtection` appFeature and linked it to the endpoint:complete tier. 2. Made an upselling component and registered it with the Upselling Service. 3. Passed the upselling component to Fleet using UIExtension. 4. Added Cypress end-to-end coverage for Essentials showing the upselling component and Complete showing the form component. ![Screenshot 2024-01-24 at 15 52 17](https://github.com/elastic/kibana/assets/29123534/6cdc3197-7bd0-4607-9323-ae4318493653)

@roxana-gheorghe

…licy Settings (elastic#174400) This PR is part of an effort to limit EDR Workflow features to the Endpoint Complete tier on serverless and focuses on server skde part of gating Agent Tamper Protection. Related PRs: elastic#174278 elastic#175129 **We decided to stick with the existing Fleet privileges for this component, and no extra changes are needed RBAC wise (confirmed with @roxana-gheorghe).** **Plugin/Policy Watcher Changes**: To monitor agent policies for a downgrade in tier (from complete to essentials) and disable agent protections if enabled, the following steps have been taken: 1. A new app feature, `endpoint_agent_tamper_protection`, has been introduced and linked to the `endpoint:complete` tier. 2. An additional method, `bumpRevision`, has been exposed in the fleet's agent policy service. This method utilizes the service's internal update function and includes a `disable_protection` flag, allowing it to be used without further modifications. 3. The security solution side calls this method upon successful fleet plugin setup. If the `endpoint_agent_tamper_protection` app feature is not enabled, it retrieves all agent policies with `is_protected: true` and updates these policies with `is_protected: false`. **API Changes**: To respond to attempts to activate agent protection via the API by users on the Essentials tier, the following steps have been taken: 1. External callback functionality has been added to the agentPolicy service, following the implementation in packagePolicy. 2. Update and create agent policy callbacks have been registered in the security solution. These callbacks check for the enabled status of the `endpoint_agent_tamper_protection` app feature. If disabled, the callback throws an error. 3. External callback execution has been added to the update and create methods in agent policy route handlers. --------- Co-authored-by: kibanamachine <[email protected]>

upsell on essential

cb3c9b2

szwarckonrad added release_note:skip Skip the PR/issue when compiling release notes Team:Defend Workflows “EDR Workflows” sub-team of Security Solution labels Jan 5, 2024

szwarckonrad self-assigned this Jan 5, 2024

szwarckonrad added 3 commits January 15, 2024 11:09

Merge branch 'main' into gated-agent-tamper-api

db8b0e5

Merge branch 'main' into gated-agent-tamper-api

dd697bd

upsell on essential

0c4e21a

kibanamachine and others added 2 commits January 16, 2024 16:11

[CI] Auto-commit changed files from 'node scripts/lint_ts_projects --…

65ad15e

…fix'

Merge branch 'main' into gated-agent-tamper-api

cb5d3c1

szwarckonrad mentioned this pull request Jan 24, 2024

[EDR Workflows][UI] Gate Agent Tamper Protection setting on Agent Policy Settings #174278

Merged

szwarckonrad added 2 commits January 25, 2024 11:17

Merge branch 'main' into gated-agent-tamper-api

63ac984

upsell on essential

77666a8

upsell on essential

30f54d0

Merge branch 'main' into gated-agent-tamper-api

255b23a

Merge branch 'main' into gated-agent-tamper-api

03ec056

szwarckonrad added 2 commits January 26, 2024 11:31

upsell on essential

fa11c4b

Merge remote-tracking branch 'origin/gated-agent-tamper-api' into gat…

d01cb0a

…ed-agent-tamper-api

szwarckonrad commented Jan 26, 2024

View reviewed changes

szwarckonrad requested review from dasansol92, semd and paul-tavares January 26, 2024 10:35

szwarckonrad marked this pull request as ready for review January 26, 2024 10:35

szwarckonrad requested review from a team as code owners January 26, 2024 10:35

semd approved these changes Jan 30, 2024

View reviewed changes

paul-tavares reviewed Jan 30, 2024

View reviewed changes

szwarckonrad added 3 commits January 31, 2024 14:07

Merge branch 'main' into gated-agent-tamper-api

14c1f7b

cr changes

63b86df

cr changes

b3c6937

juliaElastic approved these changes Jan 31, 2024

View reviewed changes

Merge branch 'main' into gated-agent-tamper-api

557791f

tomsonpl approved these changes Feb 1, 2024

View reviewed changes

paul-tavares approved these changes Feb 1, 2024

View reviewed changes

szwarckonrad added 5 commits February 1, 2024 18:24

Merge branch 'main' into gated-agent-tamper-api

f7c342f

cr changes

06c9bc9

cr changes

b63e686

Merge branch 'main' into gated-agent-tamper-api

34c9de8

# Conflicts: # x-pack/plugins/security_solution/server/fleet_integration/fleet_integration.ts

Merge branch 'main' into gated-agent-tamper-api

527a332

szwarckonrad enabled auto-merge (squash) February 1, 2024 20:19

szwarckonrad merged commit 8166d18 into elastic:main Feb 1, 2024
37 checks passed

kibanamachine added v8.13.0 backport:skip This commit does not require backporting labels Feb 1, 2024

		this.checkTamperProtectionLicense(agentPolicy);
		await this.checkForValidUninstallToken(agentPolicy, id);

[EDR Workflows][API] Gate Agent Tamper Protection setting on Agent Policy Settings #174400

[EDR Workflows][API] Gate Agent Tamper Protection setting on Agent Policy Settings #174400

Conversation

szwarckonrad commented Jan 5, 2024 • edited Loading

szwarckonrad commented Jan 16, 2024

szwarckonrad commented Jan 25, 2024

szwarckonrad commented Jan 25, 2024

szwarckonrad commented Jan 25, 2024

szwarckonrad commented Jan 26, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

semd left a comment

Choose a reason for hiding this comment

paul-tavares left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

juliaElastic left a comment

Choose a reason for hiding this comment

tomsonpl left a comment

Choose a reason for hiding this comment

paul-tavares left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kibana-ci commented Feb 1, 2024

💚 Build Succeeded

Metrics [docs]

Public APIs missing comments

Public APIs missing exports

API count

History

szwarckonrad commented Jan 5, 2024 •

edited

Loading