Skip to content

[9.3] [Entity Analytics] Adding event based telemetry for entity highlights API usage (#250101)#250258

Merged
kibanamachine merged 1 commit intoelastic:9.3from
kibanamachine:backport/9.3/pr-250101
Jan 24, 2026
Merged

[9.3] [Entity Analytics] Adding event based telemetry for entity highlights API usage (#250101)#250258
kibanamachine merged 1 commit intoelastic:9.3from
kibanamachine:backport/9.3/pr-250101

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.3:

Questions ?

Please refer to the Backport tool documentation

… 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)
@ymao1
Copy link
Copy Markdown
Contributor

ymao1 commented Jan 24, 2026

/ci

@ymao1
Copy link
Copy Markdown
Contributor

ymao1 commented Jan 24, 2026

@elasticmachine run docs-build

@kibanamachine kibanamachine merged commit 425454e into elastic:9.3 Jan 24, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants