Clarifying report date-math syntax expressions in watch #38924
Closed
Conversation
This file contains hidden or 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
I added an example of using a csv report Generation URL that contains date-math in the URL, which can cause the watch to fail if not properly formatted. This can arise when copying the csv URL from Kibana but not removing the curly brackets or properly URL-encoding the required characters, and the resulting watch `parse_exception` can be hard to track down. Users should be aware that the working report URL they copy from Kibana may not work in the watch without adjusting things like this. I wasn't sure if the example expression was too much or too specific to include in a Note format, and am open to re-working if the presentation could be improved.
Contributor
|
Pinging @elastic/kibana-docs |
adoerrES
added
the
zDeprecated Feature:Reporting
Contributor
💚 Build Succeeded |
lcawl
added
release_note:skip
lcawl
approved these changes
Jun 14, 2019
Contributor
lcawl
left a comment
lcawl
left a comment
There was a problem hiding this comment.
LGTM and builds successfully
Contributor
|
Closing in favor of #53628 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I added an example of using a csv report Generation URL that contains date-math in the URL, which can cause the watch to fail if not properly formatted. This can arise when copying the csv URL from Kibana but not removing the curly brackets or properly URL-encoding the required characters, and the resulting watch
parse_exceptioncan be hard to track down. Users should be aware that the working report URL they copy from Kibana may not work in the watch without adjusting things like this.I wasn't sure if the example expression was too much or too specific to include in a Note format, and am open to re-working if the presentation could be improved.
Summary
Summarize your PR. If it involves visual changes include a screenshot or gif.
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.- [ ] This was checked for cross-browser compatibility, including a check against IE11- [ ] Documentation was added for features that require explanation or tutorials- [ ] Unit or functional tests were updated or added to match the most common scenariosFor maintainers