-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Infrastructure UI] Telemetry: Host limit #155567
Labels
beta
Required for a feature to move to beta
Feature:Metrics UI
Metrics UI feature
Feature:ObsHosts
Hosts feature within Observability
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
Comments
crespocarlos
added
Feature:Metrics UI
Metrics UI feature
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
Feature:ObsHosts
Hosts feature within Observability
beta
Required for a feature to move to beta
and removed
needs-team
Issues missing a team label
labels
Apr 21, 2023
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
crespocarlos
added a commit
that referenced
this issue
May 11, 2023
closes: #155567 ## Summary This PR adds a new custom event to track the total number of hosts, as well as adjusts a few `data-test-subj` attribute values to meet the naming convention defined in the observability-dev [docs](https://github.com/elastic/observability-dev/blob/main/docs/how-we-work/telemetry/telemetry-convention.md#naming-convention) ### For Reviewers An option for not allowing yet a new custom event in FS could be triggering the new custom events only for self-managed customers, and in FS watch the element that holds the total number of hosts. But for now, I decided to allow the new custom event in FS for consistency --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
May 11, 2023
closes: elastic#155567 ## Summary This PR adds a new custom event to track the total number of hosts, as well as adjusts a few `data-test-subj` attribute values to meet the naming convention defined in the observability-dev [docs](https://github.com/elastic/observability-dev/blob/main/docs/how-we-work/telemetry/telemetry-convention.md#naming-convention) ### For Reviewers An option for not allowing yet a new custom event in FS could be triggering the new custom events only for self-managed customers, and in FS watch the element that holds the total number of hosts. But for now, I decided to allow the new custom event in FS for consistency --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 937912b)
kibanamachine
referenced
this issue
May 11, 2023
# Backport This will backport the following commits from `main` to `8.8`: - [[Infrastructure UI] Host limit telemetry (#155726)](#155726) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Carlos Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-11T15:44:38Z","message":"[Infrastructure UI] Host limit telemetry (#155726)\n\ncloses: https://github.com/elastic/kibana/issues/155567\r\n\r\n## Summary\r\n\r\nThis PR adds a new custom event to track the total number of hosts, as\r\nwell as adjusts a few `data-test-subj` attribute values to meet the\r\nnaming convention defined in the observability-dev\r\n[docs](https://github.com/elastic/observability-dev/blob/main/docs/how-we-work/telemetry/telemetry-convention.md#naming-convention)\r\n\r\n\r\n### For Reviewers\r\n\r\nAn option for not allowing yet a new custom event in FS could be\r\ntriggering the new custom events only for self-managed customers, and in\r\nFS watch the element that holds the total number of hosts. But for now,\r\nI decided to allow the new custom event in FS for consistency\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"937912b056f5876247f27a7baad5314401e65939","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Metrics UI","Team:Infra Monitoring UI","release_note:skip","backport:prev-minor","Feature:ObsHosts","v8.9.0"],"number":155726,"url":"https://github.com/elastic/kibana/pull/155726","mergeCommit":{"message":"[Infrastructure UI] Host limit telemetry (#155726)\n\ncloses: https://github.com/elastic/kibana/issues/155567\r\n\r\n## Summary\r\n\r\nThis PR adds a new custom event to track the total number of hosts, as\r\nwell as adjusts a few `data-test-subj` attribute values to meet the\r\nnaming convention defined in the observability-dev\r\n[docs](https://github.com/elastic/observability-dev/blob/main/docs/how-we-work/telemetry/telemetry-convention.md#naming-convention)\r\n\r\n\r\n### For Reviewers\r\n\r\nAn option for not allowing yet a new custom event in FS could be\r\ntriggering the new custom events only for self-managed customers, and in\r\nFS watch the element that holds the total number of hosts. But for now,\r\nI decided to allow the new custom event in FS for consistency\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"937912b056f5876247f27a7baad5314401e65939"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/155726","number":155726,"mergeCommit":{"message":"[Infrastructure UI] Host limit telemetry (#155726)\n\ncloses: https://github.com/elastic/kibana/issues/155567\r\n\r\n## Summary\r\n\r\nThis PR adds a new custom event to track the total number of hosts, as\r\nwell as adjusts a few `data-test-subj` attribute values to meet the\r\nnaming convention defined in the observability-dev\r\n[docs](https://github.com/elastic/observability-dev/blob/main/docs/how-we-work/telemetry/telemetry-convention.md#naming-convention)\r\n\r\n\r\n### For Reviewers\r\n\r\nAn option for not allowing yet a new custom event in FS could be\r\ntriggering the new custom events only for self-managed customers, and in\r\nFS watch the element that holds the total number of hosts. But for now,\r\nI decided to allow the new custom event in FS for consistency\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>","sha":"937912b056f5876247f27a7baad5314401e65939"}}]}] BACKPORT--> Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
beta
Required for a feature to move to beta
Feature:Metrics UI
Metrics UI feature
Feature:ObsHosts
Hosts feature within Observability
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
35
,150
or83,000
Would like to be able to compare which fields (and also what is most common - asc or desc...and for which field...basically, we probably want 'field' and 'direction' as explicit params to track
5
,10
or20
1,
2
,3
The text was updated successfully, but these errors were encountered: