Skip to content

[Security Solution] Add detection rules customization status for telemetry snapshot#237583

Merged
banderror merged 1 commit intoelastic:mainfrom
jkelas:140369_req_2_customization_status_telemetry
Oct 14, 2025
Merged

[Security Solution] Add detection rules customization status for telemetry snapshot#237583
banderror merged 1 commit intoelastic:mainfrom
jkelas:140369_req_2_customization_status_telemetry

Conversation

@jkelas
Copy link
Contributor

@jkelas jkelas commented Oct 6, 2025 •
edited by kibanamachine
Loading

Partially addresses: #140369

Summary

This is another PR from of a series of PRs I am planning to create to cover the requirements in the #140369 ticket.

The requirement covered in this PR is: " Breakdown of which fields are being customized."

Testing:

Display the snapshot:

POST kbn:/internal/telemetry/clusters/_stats?apiVersion=2
{ "unencrypted": true, "refreshCache": true }

Send the snapshot to staging telemetry cluster.

POST kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true
{}

@jkelas jkelas force-pushed the 140369_req_2_customization_status_telemetry branch 6 times, most recently from 96cc9de to c91b984 Compare October 6, 2025 10:27
@jkelas jkelas changed the title [Security Solution] Add customization status for telemetry snapshot [Security Solution] Add detection rules customization status for telemetry snapshot Oct 6, 2025
@jkelas jkelas self-assigned this Oct 6, 2025
@jkelas jkelas added release_note:skip Skip the PR/issue when compiling release notes Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Rule Management Security Detection Rule Management Team Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area backport:version Backport to applied version labels v9.2.0 v9.3.0 v8.18.9 v8.19.6 labels Oct 6, 2025
@jkelas jkelas marked this pull request as ready for review October 6, 2025 12:07
@jkelas jkelas requested review from a team as code owners October 6, 2025 12:07
@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 6, 2025

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 6, 2025

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 6, 2025

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

@jkelas jkelas requested review from a team and maximpn October 6, 2025 12:08
@banderror banderror mentioned this pull request Oct 6, 2025
Closed
36 tasks
@jkelas jkelas force-pushed the 140369_req_2_customization_status_telemetry branch from c91b984 to 9c5fee8 Compare October 7, 2025 10:24
maximpn
maximpn reviewed Oct 8, 2025
View reviewed changes
Copy link
Contributor

@maximpn maximpn left a comment

Choose a reason for hiding this comment

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

@jkelas Thanks for adding a snapshot telemetry for customized fields 🙏

I left some comments and haven't tested the PR yet.

@banderror
Copy link
Contributor

banderror commented Oct 14, 2025

@elasticmachine run docs-build

@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 14, 2025

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

✅ unchanged

History

cc @jkelas

@banderror banderror removed the v9.0.9 label Oct 14, 2025
@banderror banderror force-pushed the 140369_req_2_customization_status_telemetry branch from 7f5b4f3 to ca4c8b0 Compare October 14, 2025 15:25
@banderror
Copy link
Contributor

banderror commented Oct 14, 2025

/ci

@banderror
Copy link
Contributor

banderror commented Oct 14, 2025

@elasticmachine run docs-build

ddillinger
ddillinger approved these changes Oct 14, 2025
View reviewed changes
Copy link
Contributor

@ddillinger ddillinger left a comment

Choose a reason for hiding this comment

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

telemetry schema ✅

@banderror banderror enabled auto-merge (squash) October 14, 2025 17:05
@banderror banderror merged commit 1f41564 into elastic:main Oct 14, 2025
12 checks passed
@kibanamachine
Copy link
Contributor

kibanamachine commented Oct 14, 2025

Starting backport for target branches: 8.18, 8.19, 9.1, 9.2

https://github.com/elastic/kibana/actions/runs/18505607358

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Oct 14, 2025
@jkelas @banderror
[Security Solution] Add detection rules customization status for tele…
005d33b 
…metry snapshot (elastic#237583)

**Partially addresses: elastic#140369**

## Summary

This is another PR from of a series of PRs I am planning to create to
cover the requirements in the
elastic#140369 ticket.

The requirement covered in this PR is: " Breakdown of which fields are
being customized."

Testing:

Display the snapshot:
```
POST kbn:/internal/telemetry/clusters/_stats?apiVersion=2
{ "unencrypted": true, "refreshCache": true }
```

Send the snapshot to staging telemetry cluster.
```
POST kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true
{}
```

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
(cherry picked from commit 1f41564)
@kibanamachine kibanamachine mentioned this pull request Oct 14, 2025
Merged
@kibanamachine
Copy link
Contributor

kibanamachine commented Oct 14, 2025

💔 Some backports could not be created

Status Branch Result
❌ 8.18 Backport failed because of merge conflicts
❌ 8.19 Backport failed because of merge conflicts

You might need to backport the following PRs to 8.19:
- [ska] relocation security_solution_* FTR tests (#231416)
❌ 9.1 Backport failed because of merge conflicts
✅ 9.2

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 237583

Questions ?

Please refer to the Backport tool documentation

ersin-erdal pushed a commit to ersin-erdal/kibana that referenced this pull request Oct 15, 2025
@jkelas @banderror @ersin-erdal
[Security Solution] Add detection rules customization status for tele…
a3ef1b5 
…metry snapshot (elastic#237583)

**Partially addresses: elastic#140369**

## Summary

This is another PR from of a series of PRs I am planning to create to
cover the requirements in the
elastic#140369 ticket.


The requirement covered in this PR is: " Breakdown of which fields are
being customized."

Testing:

Display the snapshot:
```
POST kbn:/internal/telemetry/clusters/_stats?apiVersion=2
{ "unencrypted": true, "refreshCache": true }
```

Send the snapshot to staging telemetry cluster.
```
POST kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true
{}
```

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
banderror pushed a commit to banderror/kibana that referenced this pull request Oct 15, 2025
@jkelas
[Security Solution] Add detection rules customization status for tele…
baaa396 
…metry snapshot (elastic#237583)

**Partially addresses: elastic#140369**

## Summary

This is another PR from of a series of PRs I am planning to create to
cover the requirements in the
elastic#140369 ticket.

The requirement covered in this PR is: " Breakdown of which fields are
being customized."

Testing:

Display the snapshot:
```
POST kbn:/internal/telemetry/clusters/_stats?apiVersion=2
{ "unencrypted": true, "refreshCache": true }
```

Send the snapshot to staging telemetry cluster.
```
POST kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true
{}
```

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
(cherry picked from commit 1f41564)

# Conflicts:
#	x-pack/solutions/security/plugins/security_solution/server/usage/detections/ml_jobs/get_metrics.mocks.ts
#	x-pack/solutions/security/plugins/security_solution/server/usage/detections/rules/get_initial_usage.ts
#	x-pack/solutions/security/test/security_solution_api_integration/test_suites/detections_response/telemetry/trial_license_complete_tier/usage_collector/detection_rule_upgrade_status.ts
@banderror banderror mentioned this pull request Oct 15, 2025
Merged
banderror pushed a commit to banderror/kibana that referenced this pull request Oct 15, 2025
@jkelas
[Security Solution] Add detection rules customization status for tele…
2edbe8e 
…metry snapshot (elastic#237583)

**Partially addresses: elastic#140369**

## Summary

This is another PR from of a series of PRs I am planning to create to
cover the requirements in the
elastic#140369 ticket.

The requirement covered in this PR is: " Breakdown of which fields are
being customized."

Testing:

Display the snapshot:
```
POST kbn:/internal/telemetry/clusters/_stats?apiVersion=2
{ "unencrypted": true, "refreshCache": true }
```

Send the snapshot to staging telemetry cluster.
```
POST kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true
{}
```

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
(cherry picked from commit 1f41564)

# Conflicts:
#	x-pack/solutions/security/plugins/security_solution/server/usage/detections/ml_jobs/get_metrics.mocks.ts
#	x-pack/solutions/security/plugins/security_solution/server/usage/detections/rules/get_initial_usage.ts
#	x-pack/solutions/security/test/security_solution_api_integration/test_suites/detections_response/telemetry/trial_license_complete_tier/usage_collector/detection_rule_upgrade_status.ts
@banderror banderror mentioned this pull request Oct 15, 2025
Closed
@banderror
Copy link
Contributor

banderror commented Oct 15, 2025

💔 Some backports could not be created

Status Branch Result
✅ 9.1
✅ 8.19
❌ 8.18 Conflict resolution was aborted by the user

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 237583

Questions ?

Please refer to the Backport tool documentation

@banderror
Copy link
Contributor

banderror commented Oct 15, 2025

Not backporting to 8.18 as it doesn't seem there are any more patch releases planned for 8.18 + the main and 8.18 branches have diverged too much to backport it in a reasonable time.

@banderror banderror removed the v8.18.9 label Oct 15, 2025
kibanamachine added a commit that referenced this pull request Oct 15, 2025
@kibanamachine @banderror
[9.2] [Security Solution] Add detection rules customization status fo…
b1d7ea1 
…r telemetry snapshot (#237583) (#238993)

# Backport

This will backport the following commits from `main` to `9.2`:
- [[Security Solution] Add detection rules customization status for
telemetry snapshot
(#237583)](#237583)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Jacek
Kolezynski","email":"jacek.kolezynski+gh@gmail.com"},"sourceCommit":{"committedDate":"2025-10-14T18:00:01Z","message":"[Security
Solution] Add detection rules customization status for telemetry
snapshot (#237583)\n\n**Partially addresses: #140369**\n\n##
Summary\n\nThis is another PR from of a series of PRs I am planning to
create to\ncover the requirements in
the\nhttps://github.com//issues/140369 ticket.\n\n\nThe
requirement covered in this PR is: \" Breakdown of which fields
are\nbeing customized.\"\n\nTesting:\n\nDisplay the snapshot:\n```\nPOST
kbn:/internal/telemetry/clusters/_stats?apiVersion=2\n{ \"unencrypted\":
true, \"refreshCache\": true }\n```\n\nSend the snapshot to staging
telemetry cluster.\n```\nPOST
kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true\n{}\n```\n\nCo-authored-by:
Georgii Gorbachev
<georgii.gorbachev@elastic.co>","sha":"1f4156499ff9f0e74efeac99e05fa8c2d54bf7e8","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v9.2.0","v9.3.0","v9.1.6","v8.18.9","v8.19.6"],"title":"[Security
Solution] Add detection rules customization status for telemetry
snapshot","number":237583,"url":"https://github.com/elastic/kibana/pull/237583","mergeCommit":{"message":"[Security
Solution] Add detection rules customization status for telemetry
snapshot (#237583)\n\n**Partially addresses: #140369**\n\n##
Summary\n\nThis is another PR from of a series of PRs I am planning to
create to\ncover the requirements in
the\nhttps://github.com//issues/140369 ticket.\n\n\nThe
requirement covered in this PR is: \" Breakdown of which fields
are\nbeing customized.\"\n\nTesting:\n\nDisplay the snapshot:\n```\nPOST
kbn:/internal/telemetry/clusters/_stats?apiVersion=2\n{ \"unencrypted\":
true, \"refreshCache\": true }\n```\n\nSend the snapshot to staging
telemetry cluster.\n```\nPOST
kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true\n{}\n```\n\nCo-authored-by:
Georgii Gorbachev
<georgii.gorbachev@elastic.co>","sha":"1f4156499ff9f0e74efeac99e05fa8c2d54bf7e8"}},"sourceBranch":"main","suggestedTargetBranches":["9.2","9.1","8.18","8.19"],"targetPullRequestStates":[{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/237583","number":237583,"mergeCommit":{"message":"[Security
Solution] Add detection rules customization status for telemetry
snapshot (#237583)\n\n**Partially addresses: #140369**\n\n##
Summary\n\nThis is another PR from of a series of PRs I am planning to
create to\ncover the requirements in
the\nhttps://github.com//issues/140369 ticket.\n\n\nThe
requirement covered in this PR is: \" Breakdown of which fields
are\nbeing customized.\"\n\nTesting:\n\nDisplay the snapshot:\n```\nPOST
kbn:/internal/telemetry/clusters/_stats?apiVersion=2\n{ \"unencrypted\":
true, \"refreshCache\": true }\n```\n\nSend the snapshot to staging
telemetry cluster.\n```\nPOST
kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true\n{}\n```\n\nCo-authored-by:
Georgii Gorbachev
<georgii.gorbachev@elastic.co>","sha":"1f4156499ff9f0e74efeac99e05fa8c2d54bf7e8"}},{"branch":"9.1","label":"v9.1.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.9","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
@banderror
Copy link
Contributor

banderror commented Oct 16, 2025

Not backporting to 8.19 as this telemetry is based on #234793 which has only been backported to 9.2 and 9.1

@banderror banderror removed the v8.19.6 label Oct 16, 2025
banderror added a commit that referenced this pull request Oct 16, 2025
@banderror
[9.1] [Security Solution] Add detection rules customization status fo…
5bb83da 
…r telemetry snapshot (#237583) (#239200)

# Backport

This will backport the following commits from `main` to `9.1`:
- [[Security Solution] Add detection rules customization status for
telemetry snapshot
(#237583)](#237583)

<!--- Backport version: 10.0.2 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Jacek
Kolezynski","email":"jacek.kolezynski+gh@gmail.com"},"sourceCommit":{"committedDate":"2025-10-14T18:00:01Z","message":"[Security
Solution] Add detection rules customization status for telemetry
snapshot (#237583)\n\n**Partially addresses: #140369**\n\n##
Summary\n\nThis is another PR from of a series of PRs I am planning to
create to\ncover the requirements in
the\nhttps://github.com//issues/140369 ticket.\n\n\nThe
requirement covered in this PR is: \" Breakdown of which fields
are\nbeing customized.\"\n\nTesting:\n\nDisplay the snapshot:\n```\nPOST
kbn:/internal/telemetry/clusters/_stats?apiVersion=2\n{ \"unencrypted\":
true, \"refreshCache\": true }\n```\n\nSend the snapshot to staging
telemetry cluster.\n```\nPOST
kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true\n{}\n```\n\nCo-authored-by:
Georgii Gorbachev
<georgii.gorbachev@elastic.co>","sha":"1f4156499ff9f0e74efeac99e05fa8c2d54bf7e8","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection Rule
Management","Feature:Prebuilt Detection
Rules","backport:version","v9.2.0","v9.3.0","v9.1.6","v8.18.9","v8.19.6"],"title":"[Security
Solution] Add detection rules customization status for telemetry
snapshot","number":237583,"url":"https://github.com/elastic/kibana/pull/237583","mergeCommit":{"message":"[Security
Solution] Add detection rules customization status for telemetry
snapshot (#237583)\n\n**Partially addresses: #140369**\n\n##
Summary\n\nThis is another PR from of a series of PRs I am planning to
create to\ncover the requirements in
the\nhttps://github.com//issues/140369 ticket.\n\n\nThe
requirement covered in this PR is: \" Breakdown of which fields
are\nbeing customized.\"\n\nTesting:\n\nDisplay the snapshot:\n```\nPOST
kbn:/internal/telemetry/clusters/_stats?apiVersion=2\n{ \"unencrypted\":
true, \"refreshCache\": true }\n```\n\nSend the snapshot to staging
telemetry cluster.\n```\nPOST
kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true\n{}\n```\n\nCo-authored-by:
Georgii Gorbachev
<georgii.gorbachev@elastic.co>","sha":"1f4156499ff9f0e74efeac99e05fa8c2d54bf7e8"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.18","8.19"],"targetPullRequestStates":[{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/238993","number":238993,"state":"OPEN"},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/237583","number":237583,"mergeCommit":{"message":"[Security
Solution] Add detection rules customization status for telemetry
snapshot (#237583)\n\n**Partially addresses: #140369**\n\n##
Summary\n\nThis is another PR from of a series of PRs I am planning to
create to\ncover the requirements in
the\nhttps://github.com//issues/140369 ticket.\n\n\nThe
requirement covered in this PR is: \" Breakdown of which fields
are\nbeing customized.\"\n\nTesting:\n\nDisplay the snapshot:\n```\nPOST
kbn:/internal/telemetry/clusters/_stats?apiVersion=2\n{ \"unencrypted\":
true, \"refreshCache\": true }\n```\n\nSend the snapshot to staging
telemetry cluster.\n```\nPOST
kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true\n{}\n```\n\nCo-authored-by:
Georgii Gorbachev
<georgii.gorbachev@elastic.co>","sha":"1f4156499ff9f0e74efeac99e05fa8c2d54bf7e8"}},{"branch":"9.1","label":"v9.1.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.9","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.6","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
mgadewoll pushed a commit to tkajtoch/kibana that referenced this pull request Oct 17, 2025
@jkelas @banderror @mgadewoll
[Security Solution] Add detection rules customization status for tele…
3d2e0f3 
…metry snapshot (elastic#237583)

**Partially addresses: elastic#140369**

## Summary

This is another PR from of a series of PRs I am planning to create to
cover the requirements in the
elastic#140369 ticket.


The requirement covered in this PR is: " Breakdown of which fields are
being customized."

Testing:

Display the snapshot:
```
POST kbn:/internal/telemetry/clusters/_stats?apiVersion=2
{ "unencrypted": true, "refreshCache": true }
```

Send the snapshot to staging telemetry cluster.
```
POST kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true
{}
```

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
rylnd pushed a commit to rylnd/kibana that referenced this pull request Oct 17, 2025
@jkelas @banderror
[Security Solution] Add detection rules customization status for tele…
6870e78 
…metry snapshot (elastic#237583)

**Partially addresses: elastic#140369**

## Summary

This is another PR from of a series of PRs I am planning to create to
cover the requirements in the
elastic#140369 ticket.


The requirement covered in this PR is: " Breakdown of which fields are
being customized."

Testing:

Display the snapshot:
```
POST kbn:/internal/telemetry/clusters/_stats?apiVersion=2
{ "unencrypted": true, "refreshCache": true }
```

Send the snapshot to staging telemetry cluster.
```
POST kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true
{}
```

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
nickpeihl pushed a commit to nickpeihl/kibana that referenced this pull request Oct 23, 2025
@jkelas @banderror @nickpeihl
[Security Solution] Add detection rules customization status for tele…
a14cfdc 
…metry snapshot (elastic#237583)

**Partially addresses: elastic#140369**

## Summary

This is another PR from of a series of PRs I am planning to create to
cover the requirements in the
elastic#140369 ticket.


The requirement covered in this PR is: " Breakdown of which fields are
being customized."

Testing:

Display the snapshot:
```
POST kbn:/internal/telemetry/clusters/_stats?apiVersion=2
{ "unencrypted": true, "refreshCache": true }
```

Send the snapshot to staging telemetry cluster.
```
POST kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true
{}
```

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
NicholasPeretti pushed a commit to NicholasPeretti/kibana that referenced this pull request Oct 27, 2025
@jkelas @banderror @NicholasPeretti
[Security Solution] Add detection rules customization status for tele…
b1592ef 
…metry snapshot (elastic#237583)

**Partially addresses: elastic#140369**

## Summary

This is another PR from of a series of PRs I am planning to create to
cover the requirements in the
elastic#140369 ticket.


The requirement covered in this PR is: " Breakdown of which fields are
being customized."

Testing:

Display the snapshot:
```
POST kbn:/internal/telemetry/clusters/_stats?apiVersion=2
{ "unencrypted": true, "refreshCache": true }
```

Send the snapshot to staging telemetry cluster.
```
POST kbn:/internal/telemetry/force_send?apiVersion=1&elasticInternalOrigin=true
{}
```

Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@szaffarano szaffarano szaffarano approved these changes

@maximpn maximpn maximpn approved these changes

@banderror banderror banderror approved these changes

+1 more reviewer

@ddillinger ddillinger ddillinger approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@jkelas jkelas

Labels

backport:version Backport to applied version labels Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area release_note:skip Skip the PR/issue when compiling release notes Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v9.1.6 v9.2.0 v9.3.0

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@jkelas @elasticmachine @banderror @kibanamachine @szaffarano @ddillinger @maximpn