Skip to content

Conversation

@alisonelizabeth
Copy link
Contributor

@alisonelizabeth alisonelizabeth commented May 4, 2020

This PR updates copy in the Ingest Node Pipelines app.

Screenshots

Screen Shot 2020-05-04 at 2 17 14 PM

Screen Shot 2020-05-04 at 4 17 59 PM

create

Screen Shot 2020-05-04 at 9 26 51 PM

Screen Shot 2020-05-04 at 9 28 54 PM

Screen Shot 2020-05-04 at 9 30 42 PM

@alisonelizabeth alisonelizabeth added v8.0.0 Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t// release_note:skip Skip the PR/issue when compiling release notes v7.8.0 Feature:Ingest Node Pipelines Ingest node pipelines management labels May 4, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@alisonelizabeth alisonelizabeth force-pushed the ingest_pipelines/copy branch from 5ef63d8 to 4878cde Compare May 5, 2020 01:31
@alisonelizabeth alisonelizabeth marked this pull request as ready for review May 5, 2020 01:34
@alisonelizabeth alisonelizabeth requested a review from a team as a code owner May 5, 2020 01:34
<FormattedMessage
id="xpack.ingestPipelines.testPipelineFlyout.outputTab.descriptionText"
defaultMessage="The output of the executed pipeline. {runLink}"
defaultMessage="View the final output data, or see how each processor affects the ingest document as it passes through the pipeline. {runLink}"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gchaps Let me know what you think of this (screenshot in initial PR comment). This differs from your original suggestion, as the View verbose output is actually disabled by default.

Copy link
Contributor

@cjcenizal cjcenizal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great overall! I had a couple minor concerns which I think we should address before merging.

return (
<>
{acc}{' '}
<FormattedMessage
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's worth checking with the i18n folks, but I don't think that we can depend on all languages following the English structure of using a word ("and" in the case of English) to join the last item onto a list. It might be safer to use the original pattern of simply joining on a comma.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good point. I reverted the change to the original implementation. This also follows the pattern we're using in Snapshot + Restore, so it will be consistent.

title={
<FormattedMessage
id="xpack.ingestPipelines.list.loadErrorTitle"
defaultMessage="Unable to load pipelines. Try {reloadLink} the page."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The way this text is phrased, it seems like clicking the reload link will reload the page, which I think of as a browser page refresh. But clicking this link will actually just resend the request to load the pipelines. Can we align text with action more closely by phrasing this as "Try reloading them"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point! I went with Gail's suggestion: "Try again".

@alisonelizabeth alisonelizabeth removed the request for review from jloleysens May 5, 2020 16:34
@gchaps
Copy link
Contributor

gchaps commented May 5, 2020

I'm going to rescind one of my earlier comments. I think the text reads better as "Provide an array of documents for the pipeline to ingest."

Per @cjcenizal, how about:

Unable to load pipelines. Try again.

and make "Try again" the link.

The text in the Output screen felt a little too long for me. How about we go back to using an intro and tooltip:

Intro: View the final output data.
Tooltip: See how each processor affects the document as it passes through the pipeline.

@cjcenizal
Copy link
Contributor

Unable to load pipelines. Try again.

RGTM!

The text in the Output screen felt a little too long for me. How about we go back to using an intro and tooltip:

I'm not sure the intro/tooltip option is equivalent with what we currently have. The current text offers the user two exclusive options: final output data or data per-processor. But your suggestion makes it sound like the tooltip text is an elaboration upon the intro text.

@cchaos
Copy link
Contributor

cchaos commented May 5, 2020

Hey @alisonelizabeth I just glanced at your screenshots and have one request. Can you separate create a single empty state panel instead of putting the empty state underneath the title for the listing page? It just creates a weird hierarchy as it is and then you can explain more of what a pipeline is and duplicate the docs link inside of it.

81028241-8a78fe80-8e4e-11ea-9e75-2affa6fa304d

@alisonelizabeth
Copy link
Contributor Author

alisonelizabeth commented May 5, 2020

@cchaos thanks for the catch! I will open up a separate PR and address this. I went ahead and addressed in this PR.

@gchaps
Copy link
Contributor

gchaps commented May 5, 2020

Empty state

How about using "Learn more" followed by an icon to let users know they are going to an outside doc.

Output

I'm not sure the intro/tooltip option is equivalent with what we currently have.

We could keep the intro (I removed a few words) and then use a space to separate the intro from the Refresh link so it doesn't feel so crowded)

View the output data, or see how each processor affects the document as it passes through the pipeline.

Failure processors

What about adding the word "alternate". Some choices:

  • The alternate processors to execute after a processor fails.
  • The alternate processors to execute after the pipeline stops because of a failure.
  • The alternate processors to execute after an original processor in the pipeline fails.

@alisonelizabeth
Copy link
Contributor Author

@gchaps @cjcenizal I believe I addressed all of your feedback. Thanks for the review! Updated screenshots:

Empty prompt
Screen Shot 2020-05-05 at 3 56 41 PM

Output tab - I'm not sure if I'm sold on the "Refresh output" link on its own line. @cchaos WDYT?
Screen Shot 2020-05-05 at 4 01 54 PM

Create form
Screen Shot 2020-05-05 at 4 03 06 PM

Error
Screen Shot 2020-05-05 at 12 45 45 PM

@cchaos
Copy link
Contributor

cchaos commented May 5, 2020

Thanks @alisonelizabeth for going ahead and tackling the empty screen! Could you also add a small line break before the "Learn more" link? Just to ensure that there isn't a line break inside of the link itself.

Image 2020-05-05 at 5 31 20 PM

As for the refresh button. AFAICT, It refreshes the code block below? If it's crammed up with the description text above then it seems more like a link than a button. I would even go further and maybe make it a proper button (the borderd, but small kind).

You could also put the refresh button and the toggle in the same line with the toggle on the far right. So then it looks like a toolbar for the code output.

Image 2020-05-05 at 5 32 06 PM

@gchaps
Copy link
Contributor

gchaps commented May 5, 2020

Text looks good. I have one small comment. For the error message, can we use "Try again"?

@alisonelizabeth
Copy link
Contributor Author

Text looks good. I have one small comment. For the error message, can we use "Try again"?

@gchaps oops! The screenshot I added was outdated. The text is "Try again" now.

@alisonelizabeth
Copy link
Contributor Author

alisonelizabeth commented May 6, 2020

Thanks @cchaos! I added a line break to the empty prompt and also applied your suggestion regarding the "Reload" functionality. I think this looks a lot better now - thanks!

Screen Shot 2020-05-05 at 9 05 33 PM

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@cjcenizal
Copy link
Contributor

I’m going to merge this so we make FF.

@cjcenizal cjcenizal merged commit 9d88805 into elastic:master May 6, 2020
cjcenizal pushed a commit to cjcenizal/kibana that referenced this pull request May 6, 2020
gmmorris added a commit to gmmorris/kibana that referenced this pull request May 6, 2020
* master: (72 commits)
  add tsvb tests to Firefox suite (elastic#65425)
  Fix flaky ServerMetricsCollector integration test (elastic#65420)
  [APM] Custom links section inside the Actions menu is showing outside of the menu (elastic#65428)
  [ML] Adds docs_per_second to transform edit form. (elastic#65365)
  update apm index pattern (elastic#65424)
  add direct build command (elastic#65431)
  [ML] Adding daily_model_snapshot_retention_after_days to types and schemas (elastic#65417)
  [chore] Improve request cancelation handling in vis embeddable (elastic#65057)
  [Alerting] migrates acceptance and functional test fixtures to KP (elastic#64888)
  [ML] Fixes reordering in view by selection when overall cell selected (elastic#65290)
  Additional branding updates (elastic#64712)
  Remove redundant formatting of percentage column (elastic#64948)
  [SIEM][CASE] Configuration pages UI redesign (elastic#65355)
  New nav (elastic#64018)
  [Ingest pipelines] Address copy feedback (elastic#65175)
  bug fixing (elastic#65387)
  skip whole suite blocking snapshots (elastic#65377)
  add related event generation to ancestor nodes (fixes a bug) (elastic#64950)
  [Canvas] move files from legacy/plugins to plugins (elastic#65283)
  [SIEM] template timeline UI (elastic#64439)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature:Ingest Node Pipelines Ingest node pipelines management release_note:skip Skip the PR/issue when compiling release notes Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t// v7.8.0 v8.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants