-
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
[APM] Use specific dimensions for service group creation #142201
Comments
Pinging @elastic/apm-ui (Team:APM) |
We might consider restricting the dimensions even further. If we want to make things easier for ourselves, it should be possible to retrieve alerts using the service group kql query. We can only do that if every dimension that we decide on here are also persisted for every alerts That being said, this list does look reasonably short so it's not an issue to add all of those to the APM alerts. |
@chrisdistasio Did we mean to include |
is it possible to add service.runtime.name? Accolade is using this to create groups for lambda? Alternately, they could be guided to use labels. |
Yes, this was a field identified as one in use based on telemetry. |
…143881) * [APM] Support specific fields when creating service groups (#142201) * add support to anomaly rule type to store supported service group fields in alert * address PR feedback and fixes checks * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' * [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix' * add API tests for field validation * fixes linting * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' * fixes multi_terms sort order paths, for each rule type query * adds unit tests and moves some source files * fixed back import path * PR feedback * improvements to kuery validation * fixes selecting 'All' in service.name, transaction.type fields when creating/editing APM Rules (#143861) Co-authored-by: kibanamachine <[email protected]>
* main: (41 commits) [api-docs] Daily api_docs build (elastic#144212) Add readonly view to role management (elastic#143893) [api-docs] Daily api_docs build (elastic#144208) [APM] Adds button group to navigate to "All services" (elastic#142911) Update react-query to ^4.12.0 (main) (elastic#139986) [APM] Support specific fields when creating service groups (elastic#142201) (elastic#143881) [api-docs] Daily api_docs build (elastic#144203) [ts] add stub index.d.ts in @kbn/ui-shared-deps-npm [Synthetics] Fix failing Synthetics Integration test (elastic#144175) chore(NA): remove @types/pkg link creation when generating a new package (elastic#144200) [Osquery] Update schema to v5.5.1 (elastic#144090) [ci] remove github-checks-reporter (elastic#144193) [8.6][ML Inference] Verify pipeline usage before deletion (elastic#144053) [ts] ts refs cache was removed, remove capture task Added Rollups CCS Test (elastic#144074) [auto] migrate existing plugin/package configs [ts] stop building @types packages in bootstrap skip failing test suite (elastic#142762) skip failing test suite (elastic#144186) [Fleet] Show Add Fleet Server instead of add agent when adding agent from agent policy (elastic#144105) ...
To help maintain a consistent experience in terms of performance, we'd like to use a specific list of dimensions when creating a service group. This piece of work is to update the service group creation flow so that only the following dimensions are available to query against:
Links
The text was updated successfully, but these errors were encountered: