-
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
[Discover] Only show logs profiles for O11y solution view #199255
Merged
davismcphee
merged 19 commits into
elastic:main
from
davismcphee:logs-profiles-o11y-only
Nov 18, 2024
Merged
Changes from 12 commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
027b23a
Only show logs profiles for O11y solution view
davismcphee 42d9800
Add jest tests
davismcphee 1be22ed
Update functional tests
davismcphee fe66899
Cleanup
davismcphee 2362b4a
Moving files to observability folder
davismcphee 4a6daf9
Update subprofile IDs
davismcphee ec25ffe
Fix functional tests
davismcphee 97ea182
Merge branch 'main' into logs-profiles-o11y-only
davismcphee 726a1f9
Merge branch 'main' into logs-profiles-o11y-only
davismcphee 25bca72
Updated CODEOWNERS
davismcphee 81c084c
[CI] Auto-commit changed files from 'make api-docs'
kibanamachine bbe4bd0
Merge branch 'main' into logs-profiles-o11y-only
davismcphee 5658e92
[CI] Auto-commit changed files from 'make api-docs'
kibanamachine 1a6d95e
Allow accessing ContextWithProfileId within profile resolve methods
davismcphee a41d43e
Update o11y logs profiles to check profileId instead of solutionType
davismcphee 28c4f97
Merge branch 'main' into logs-profiles-o11y-only
davismcphee 6a68792
Revert "[CI] Auto-commit changed files from 'make api-docs'"
davismcphee 0b0d350
[CI] Auto-commit changed files from 'make api-docs'
kibanamachine a9a5e70
Merge branch 'main' into logs-profiles-o11y-only
davismcphee File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Validating CODEOWNERS rules …
This file contains 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
File renamed without changes.
File renamed without changes.
This file contains 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
This file contains 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
This file contains 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
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
80 changes: 80 additions & 0 deletions
80
...file_providers/observability/logs_data_source_profile/sub_profiles/create_resolve.test.ts
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,80 @@ | ||
/* | ||
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one | ||
* or more contributor license agreements. Licensed under the "Elastic License | ||
* 2.0", the "GNU Affero General Public License v3.0 only", and the "Server Side | ||
* Public License v 1"; you may not use this file except in compliance with, at | ||
* your election, the "Elastic License 2.0", the "GNU Affero General Public | ||
* License v3.0 only", or the "Server Side Public License, v 1". | ||
*/ | ||
|
||
import { createEsqlDataSource } from '../../../../../../common/data_sources'; | ||
import { | ||
DataSourceCategory, | ||
DataSourceProfileProviderParams, | ||
RootContext, | ||
SolutionType, | ||
} from '../../../../profiles'; | ||
import { createResolve } from './create_resolve'; | ||
|
||
describe('createResolve', () => { | ||
const VALID_INDEX_PATTERN = 'valid'; | ||
const INVALID_INDEX_PATTERN = 'invalid'; | ||
const ROOT_CONTEXT: RootContext = { solutionType: SolutionType.Observability }; | ||
const RESOLUTION_MATCH = { | ||
isMatch: true, | ||
context: { category: DataSourceCategory.Logs }, | ||
}; | ||
const RESOLUTION_MISMATCH = { | ||
isMatch: false, | ||
}; | ||
const resolve = createResolve(VALID_INDEX_PATTERN); | ||
|
||
it('should match a valid index pattern', () => { | ||
const result = resolve({ | ||
rootContext: ROOT_CONTEXT, | ||
dataSource: createEsqlDataSource(), | ||
query: { esql: `FROM ${VALID_INDEX_PATTERN}` }, | ||
}); | ||
expect(result).toEqual(RESOLUTION_MATCH); | ||
}); | ||
|
||
it('should not match an invalid index pattern', () => { | ||
const result = resolve({ | ||
rootContext: ROOT_CONTEXT, | ||
dataSource: createEsqlDataSource(), | ||
query: { esql: `FROM ${INVALID_INDEX_PATTERN}` }, | ||
}); | ||
expect(result).toEqual(RESOLUTION_MISMATCH); | ||
}); | ||
|
||
it('should not match when the solution type is not Observability', () => { | ||
const params: Omit<DataSourceProfileProviderParams, 'rootContext'> = { | ||
dataSource: createEsqlDataSource(), | ||
query: { esql: `FROM ${VALID_INDEX_PATTERN}` }, | ||
}; | ||
expect( | ||
resolve({ | ||
...params, | ||
rootContext: ROOT_CONTEXT, | ||
}) | ||
).toEqual(RESOLUTION_MATCH); | ||
expect( | ||
resolve({ | ||
...params, | ||
rootContext: { solutionType: SolutionType.Default }, | ||
}) | ||
).toEqual(RESOLUTION_MISMATCH); | ||
expect( | ||
resolve({ | ||
...params, | ||
rootContext: { solutionType: SolutionType.Search }, | ||
}) | ||
).toEqual(RESOLUTION_MISMATCH); | ||
expect( | ||
resolve({ | ||
...params, | ||
rootContext: { solutionType: SolutionType.Security }, | ||
}) | ||
).toEqual(RESOLUTION_MISMATCH); | ||
}); | ||
}); |
This file contains 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
File renamed without changes.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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.
Tip
Non-blocking suggestion, as this would work perfectly 👌
This condition should probably reflect how we resolve the O11y root profile, which means this needs to change and be aligned every time we update the logic for the O11y root profile resolution.
I don't expect that to change often, but we might miss some corner cases if we forget to update the logic also here and anywhere else this is implemented in this PR.
Have you considered to use the root profile resolve declaration to keep the resolution logic centralized and inherit it here?
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.
As we discussed offline, while we can't re-execute the root profile resolution logic (since it's async while document profile resolution is sync), I've updated the
rootContext
checks to look atprofileId
instead ofsolutionType
, which has the same effect of protecting against future changes: a41d43e.