[Entity Analytics] Adding event based telemetry for entity highlights API usage#250101
Merged
ymao1 merged 2 commits intoelastic:mainfrom Jan 23, 2026
Merged
[Entity Analytics] Adding event based telemetry for entity highlights API usage#250101ymao1 merged 2 commits intoelastic:mainfrom
ymao1 merged 2 commits intoelastic:mainfrom
Conversation
ymao1
added
release_note:skip
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
💚 Build Succeeded
Metrics [docs]
History
cc @ymao1 |
Contributor
|
Pinging @elastic/security-entity-analytics (Team:Entity Analytics) |
CAWilson94
approved these changes
Jan 23, 2026
Contributor
CAWilson94
left a comment
CAWilson94
left a comment
There was a problem hiding this comment.
Desk tested - LGTM, can see documents generating as described. 🚀
ymao1
added
backport:version
Contributor
|
Starting backport for target branches: 9.3 https://github.com/elastic/kibana/actions/runs/21294295443 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 23, 2026
… API usage (elastic#250101) Resolves elastic#249234 ## Summary Adds call to report event when entity details highlight API is called. ## To Verify 1. Add `telemetry.localShipper: true` to your Kibana config 2. Start ES and Kibana 3. Generate some entity data 4. For each entity, open the flyout and generate a summary 5. Repeat for a few different entities 6. In Dev Tools, perform the following query ``` GET ebt-kibana-server/_search { "query": { "bool": { "filter": [ { "term": { "event_type": "entity_highlights_usage" } } ] } } } ``` 7. You should see a document for each time you generated a summary with the entity type and space ID properties populated correctly Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 48d5a6d)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Jan 24, 2026
…lights API usage (#250101) (#250258) # Backport This will backport the following commits from `main` to `9.3`: - [[Entity Analytics] Adding event based telemetry for entity highlights API usage (#250101)](#250101) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ying Mao","email":"ying.mao@elastic.co"},"sourceCommit":{"committedDate":"2026-01-23T17:01:53Z","message":"[Entity Analytics] Adding event based telemetry for entity highlights API usage (#250101)\n\nResolves https://github.com/elastic/kibana/issues/249234\n\n## Summary\n\nAdds call to report event when entity details highlight API is called.\n\n## To Verify\n1. Add `telemetry.localShipper: true` to your Kibana config\n2. Start ES and Kibana\n3. Generate some entity data\n4. For each entity, open the flyout and generate a summary\n5. Repeat for a few different entities\n6. In Dev Tools, perform the following query\n\n```\nGET ebt-kibana-server/_search\n{\n \"query\": {\n \"bool\": {\n \"filter\": [\n {\n \"term\": {\n \"event_type\": \"entity_highlights_usage\"\n }\n }\n ]\n }\n }\n}\n```\n\n7. You should see a document for each time you generated a summary with\nthe entity type and space ID properties populated correctly\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"48d5a6d746635f4afaf6734d7414aeb4da86ac16","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Entity Analytics","backport:version","v9.3.0","v9.4.0"],"title":"[Entity Analytics] Adding event based telemetry for entity highlights API usage","number":250101,"url":"https://github.com/elastic/kibana/pull/250101","mergeCommit":{"message":"[Entity Analytics] Adding event based telemetry for entity highlights API usage (#250101)\n\nResolves https://github.com/elastic/kibana/issues/249234\n\n## Summary\n\nAdds call to report event when entity details highlight API is called.\n\n## To Verify\n1. Add `telemetry.localShipper: true` to your Kibana config\n2. Start ES and Kibana\n3. Generate some entity data\n4. For each entity, open the flyout and generate a summary\n5. Repeat for a few different entities\n6. In Dev Tools, perform the following query\n\n```\nGET ebt-kibana-server/_search\n{\n \"query\": {\n \"bool\": {\n \"filter\": [\n {\n \"term\": {\n \"event_type\": \"entity_highlights_usage\"\n }\n }\n ]\n }\n }\n}\n```\n\n7. You should see a document for each time you generated a summary with\nthe entity type and space ID properties populated correctly\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"48d5a6d746635f4afaf6734d7414aeb4da86ac16"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/250101","number":250101,"mergeCommit":{"message":"[Entity Analytics] Adding event based telemetry for entity highlights API usage (#250101)\n\nResolves https://github.com/elastic/kibana/issues/249234\n\n## Summary\n\nAdds call to report event when entity details highlight API is called.\n\n## To Verify\n1. Add `telemetry.localShipper: true` to your Kibana config\n2. Start ES and Kibana\n3. Generate some entity data\n4. For each entity, open the flyout and generate a summary\n5. Repeat for a few different entities\n6. In Dev Tools, perform the following query\n\n```\nGET ebt-kibana-server/_search\n{\n \"query\": {\n \"bool\": {\n \"filter\": [\n {\n \"term\": {\n \"event_type\": \"entity_highlights_usage\"\n }\n }\n ]\n }\n }\n}\n```\n\n7. You should see a document for each time you generated a summary with\nthe entity type and space ID properties populated correctly\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"48d5a6d746635f4afaf6734d7414aeb4da86ac16"}}]}] BACKPORT--> Co-authored-by: Ying Mao <ying.mao@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #249234
Summary
Adds call to report event when entity details highlight API is called.
To Verify
telemetry.localShipper: trueto your Kibana config