* Remove skip for testing on server. Unable to repro locally
* run kibana-ciGroup2 40 times per build
* Temporarily skip 'geo map' check
* Left out 'Rendering Test: ' in filter string
* Revert "run kibana-ciGroup2 40 times per build"
This reverts commit 103a5c9c6e.
* Review feedback. Remove 'Flaky' test ref
Attempts to make KQL syntax errors more sensical to the average user.
I initially tried to use a similar solution to the one we used for detecting usage of old lucene syntax. In other words, I tried to create rules in the grammar that would match strings containing common mistakes the user might make and throw custom error messages for each situation. This proved to be more difficult for detecting errors in the regular language. While the Lucene rules could be completely separated from the main grammar, the KQL error rules had to be mixed into the main grammar which made it much more complex and had a lot of unintended side effects.
So instead I decided to lean more heavily on PEG's built in error reporting. Giving certain rules human readable names allows the parser to use those names in the error reporting instead of auto generating a long list of possible characters that might be expected based on the matching rules. Since the PEG errors contain location information I was also able to add ascii art that points the user to exactly where the error occurred in their query string. While this approach is not quite as nice as bespoke error messages that tell the user exactly what is wrong in plain English, it's much more maintainable and I think it still results in much better error messages compared to what we have today.
I've also removed the old original kuery grammar (for queries like is(response, 200)). We were only using it to display an error if I user was still using the old syntax. This version of kuery hasn't existed since 6.3 and we've had error messages telling users this since then. I think it's safe to remove the legacy parser at this point, which greatly reduces the complexity of our error reporting.
Negated filters disregarded the "NOT" when using custom labels. Therefore it was not possible to differentiate between the 2 filter states. This fix for #34979 adds the "NOT" also to custom labels
* Exploring a useUrlParams hook separate from useLocation
* Refactors url params hook into context + hook
* Fixes unmount async bugs in some components
* Rewrites datepicker tests
* Fixes some import reference problems
* Moves urlParams logic out of store and into context directory, updates references
* Makes urlParams context update itself on location changes
* Adds url params tests
* Removed left-over debug additions
* Small improvement for types based on review feedback 👍
* Converts url params to hooks for ErrorGroupDetails component
* Converts url params to hooks for ServiceDetails component
* Converts url params to hooks for ServiceOverview component
* Converts url params to hooks for TraceOverview component
* Converts url params to hooks for TransactionDetails component
* Converts url params to hooks for KueryBar component (plus TS convert)
* Cleanup removing redux
* Fixes tests after removing redux
* Updates type reference to use ui/ import
* Moves selectors folder into public and deletes store folder
* Removes unnecessary mountWithRouterAndStore
* Correctly orders imports to satisfy lint gods
* Removes unused imports
* [TSVB] The problem with fast changing the panel settings
Fix: #35136
* [TSVB] The problem with fast changing the panel settings #35142
* [TSVB] The problem with fast changing the panel settings
* [TSVB] The problem with fast changing the panel settings - fix PR comments
The interval parameter is used to fill the gaps between missing buckets. If we are using a calendar interval it not always correspond correctly to his milliseconds representation. E.g. 1y interval can correspond to 365 or 366 days depending on the interval and. If transformed to milliseconds it can get one of those two values depending of the interval start and end. The same happens for months.
Add a new esarchive with 7 years of data, used for those functional tests
Removed angular dependency from zero injection
* Adding token auth docs
* Revising based on Aleh's input
* Restructuring the token docs a bit
* Linking from the bullets
* More revisions, thanks Gail!!
* Whoops, accidentally added intead of replaced a sentence
* Clarifying the behavior when using both basic and token auth
* Added sorting to all columns
* Added sorting to table wrapper instead
* Fixed condition
* Removed default sorting value
* Removed a log statement
* Converted beats directive into a controller
