-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Infra UI] Implement telemetry for the asset details flyout #163078
[Infra UI] Implement telemetry for the asset details flyout #163078
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀 I am able to see the view event and also click events in the browser. I added some questions regarding tracking different render modes ( if we have a different issue for the assets details page telemetry we can ignore it here )
@@ -5,4 +5,5 @@ | |||
* 2.0. | |||
*/ | |||
|
|||
export const ASSET_DETAILS_FLYOUT_COMPONENT_NAME = 'infraAssetDetailsFlyout'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to have a different name in case it's open as page? Maybe I am missing something but I don't see a different component
value or passing renderMode
to this event 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. the name will be different. Probably infraAssetDetailsPage
const telemetry = service.start(); | ||
|
||
telemetry.reportAssetDetailsFlyoutViewed({ | ||
componentName: 'infraAssetDetailsFlyout', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we also want to pass the render mode here? Or to have infraAssetDetailsFlyout
and infraAssetDetailsPage
to know when a the flyout/details page is rendered
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this:
Or to have infraAssetDetailsFlyout and infraAssetDetailsPage to know when a the flyout/details page is rendered
@@ -4,6 +4,17 @@ http.enabled: true | |||
http.host: "0.0.0.0" | |||
|
|||
metricbeat.modules: | |||
- module: system | |||
- module: nginx |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Q: This is not part of the telemetry right? it's nice to have it in the docs tho 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooops. thanks for catching it.
@@ -107,7 +101,7 @@ export const Page = PageTemplate.bind({}); | |||
export const Flyout = FlyoutTemplate.bind({}); | |||
Flyout.args = { | |||
renderMode: { | |||
showInFlyout: true, | |||
mode: 'flyout', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I realized that this will conflict with my changes in my PR where I use showInFlyout
as a boolean. I can adapt that once this PR is merged. It is all good, I am just curious now if it is somehow used in the telemetry object or not yet (I don't see the mode when I check it just want to be sure that I am not missing something)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
renderMode
will only be used to determine the componentName
attribute. I changed it because this way seems more explanatory to differentiate between render mode: page
vs flyout
. Not sure if you agree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, got it! Yeah, it makes sense, we can also extend with other modes that way! I used the boolean to have the "default" view and "flyout" view so the consumer should add a prop only in case a flyout is needed, but your change is good, thanks for explaining 👍
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
* main: (108 commits) [Telemetry Schema Validation] Allow `null` on `string` (elastic#163499) [Search] Add Slack and Gmail connectors (elastic#163321) [ML] Provide hints for empty fields in dropdown options in Anomaly detection & Transform creation wizards, Change point detection view (elastic#163371) chore(slo): Add response required fields (elastic#163430) [AO] Fix add_to_case functional test (elastic#163155) unskip license type functional test (elastic#163199) fix(NA): yarn env vars for node_modules mirrors (elastic#163549) [Response Ops][Task Manager] Expose SLI metrics in HTTP API (elastic#162178) [Logs UI] Adapt test to ES highlighting changes and unskip (elastic#163592) [Infra UI] Implement Telemetry on 'Show' buttons within Inventory (elastic#163587) [Enterprise Search]Migrate all usages of EuiPage*_Deprecated (elastic#163482) fix(slo): settings and access for serverless (elastic#163514) [Infra UI] Implement telemetry for the asset details flyout (elastic#163078) [Fleet] Add a banner to the top of the Kafka Output UI to say that Elastic Defend integration is not supported (elastic#163579) [Fleet] Re-enable and fix Fleet policy secret integration tests (elastic#163428) [Fleet] add managed to imported saved object (elastic#163526) [Index Management] Disable index actions using contextRef (elastic#163475) [Discover] Inline shard failures warnings (elastic#161271) [Security Solution][Detection engine] skips geo_point non-ecs validation (elastic#163487) Update EUI layout components in bfetch example plugin (elastic#163490) ...
Summary
This PR adds proper
data-test-subj
attributes to the Asset Details component and adds a new custom telemetry eventBesides that, I've renamed 2 props,
node
->asset
andnodeType
->assetType
, to make naming consistent with what we're naming these attributes across asset-related stuff.How to test
Infrastructure
>Hosts
Asset Details Flyout Viewed
should be present inkibana-browser
requestkibana-browser
requestsdata-component-name
anddata-asset-type
attributes