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.
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
[One Discover] Add app menu actions for Observability projects #198987
[One Discover] Add app menu actions for Observability projects #198987
Changes from 18 commits
d619e41
c02bf21
d5e2705
8c28477
e9a679a
6cde32f
b32046d
1f0e308
6b2480d
250638f
9e271f7
9f5252f
0553ddc
8c073e2
cb44a07
e9f6c40
58eba92
73bd8ba
13646a8
b7a61fb
c22e5b3
b08d118
e333f5b
65d854d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Hi @tonyghiani,
The PR changes are looking great and the code is very clean.
I have some questions about "Create custom threshold rule" action.
For some reason I am see an error message when trying to create one (I am using a space with Observability set as the current Solution view).
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.
Hey @jughosta 👋
Yes, the custom threshold rule is an observability alert that can be applied to any data stream where the user wants to control a value.
It does work with ad-hoc views, the failure you are facing is due to the fact I was not passing the data view specs, but only the (erroneously) data view pattern, which I fixed in fix(discover): use data view specs for alert rule
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 ran into an issue where the request failed when I tried to create an SLO, seemingly because of the filter I was using in Discover:
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 reproduced it but it looks like a bug on the SLOs end, we are just embedding the creation flyout.
Could you open an issue for the SLOs team please?
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 was unable to reproduce this outside of Discover directly in the SLOs app. It seems they might be stripping the
$state
property from filters or something similar before saving:Do you know of another area in Kibana where I can create SLOs to try to reproduce it? Mainly I'm unsure if this is a bug that affects other usages too, or if the expectation is that consumers somehow modify the filters as they do before saving.
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.
Hey Davis, I tried this on Logs Explorer too and it is affected in the same way.
As you thought, the expectation is that the filters don't have the
$state
property, which is reason why it fails validating the payload sent to the server and fails the SLO creation.I stripped the property client side and it works fine now
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.
Nice, I confirmed it works now!