Skip to content
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

Edit text strings and links in add logstash output UI #129551

Merged

Conversation

dedemorton
Copy link
Contributor

@dedemorton dedemorton commented Apr 6, 2022

Summary

Closes elastic/observability-docs#1767.

Related to #129131

@nchaulet Gail and I came up with most of these edits together. i want her to confirm my changes before you review this. I wasn't sure if I was supposed to update the test files, too. I did, but might have missed some.

Checklist

Open issues:

  • How will users provide feedback and report bugs? Discuss? GitHub? We already have a Send feedback link on the page, so we should direct users to that unless we prefer the discuss forum.
  • The links here go to the same page. We should remove one. I think we should remove the button.
    image
  • I'm not sure if my "Invalid logstash host..." edit is correct because I couldn't understand the original message. IMO it's better to tell users what they should do, not what they shouldn't do.

Possible bugs:

  • When you edit the output and change the type to Logstash, the URL specified is invalid. I think this might be a bug because the field has the Elasticsearch URL--maybe the field is not being reset.
    image
  • If you try to select the URL from here ^^ by dragging and highlighting, the whole flyout closes.

Deferred for later:

  • Users need more guidance about what is valid in the certs fields. Do we expect them to paste in a block? Provide a path? Can we show an example? There's a different issue to track this work for 8.2, so I am marking this off.
  • There are quite a few places in the Fleet UI where we use really generic links. I want to go through the UI at some point, evaluate the links, and identify any content gaps that are causing us to create awkward links.
  • Edit validation errors (add periods).

Updated screen

image

@dedemorton dedemorton requested a review from gchaps April 6, 2022 02:34
@dedemorton dedemorton self-assigned this Apr 6, 2022
@dedemorton dedemorton requested a review from nchaulet April 6, 2022 02:37
@nchaulet
Copy link
Member

nchaulet commented Apr 6, 2022

The default URL shown for the Logstash host field is invalid. We need to change the default or fix the validation:

Yes we need to change the placeholder, there is no protocol for logstash host

Users need more guidance about what is valid in the certs fields. Do we expect them to paste in a block? Provide a path? Can we show an example?

We expect them to paste the certificate block something like, I guess we can update the placeholder with more info

---BEGIN RSA
certificate...
---END RSA

The links here go to the same page. We should remove one. I think we should remove the button

Yes I think removing the button make sense too @dborodyansky does it make sense to you?

I'm not sure if my "Invalid logstash host..." edit is correct because I couldn't understand the original message. IMO it's better to tell users what they should do, not what they shouldn't do.

The logstash host should be a domain or ip + port, there is no protocol, I think your message make sense (maybe not use the URL term as there is no protocol)

Validation errors need to end in a period, but I didn't make the updates because the errors are consistent with other parts of the Fleet UI. We should fix it all at once.

What do you mean here? if you correct the validation error it should disappear.

@dborodyansky
Copy link
Contributor

The links here go to the same page. We should remove one. I think we should remove the button

Yes I think removing the button make sense too @dborodyansky does it make sense to you?

Agree

@dedemorton
Copy link
Contributor Author

@nchaulet Re:

Validation errors need to end in a period, but I didn't make the updates because the errors are consistent with other parts of the Fleet UI. We should fix it all at once.

What do you mean here? if you correct the validation error it should disappear.

I was commenting on a style issue. Validation messages should end with a period (.) for punctuation. :-) But I didn't fix this because it's better to just do all the validation messages in one edit so they are consistent across the UI.

@dedemorton
Copy link
Contributor Author

This is ready for review, though the CI might fail...if it does, I'll fix it. Just wanted to get this up for review.

@dedemorton dedemorton marked this pull request as ready for review April 7, 2022 01:56
@dedemorton dedemorton requested review from a team as code owners April 7, 2022 01:56
@dedemorton dedemorton requested a review from gchaps April 7, 2022 01:56
@botelastic botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Apr 7, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

Copy link
Member

@nchaulet nchaulet left a comment

Choose a reason for hiding this comment

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

LGTM 🚀 (I took the liberty to push a commit to fix tests)

@nchaulet nchaulet added release_note:skip Skip the PR/issue when compiling release notes auto-backport Deprecated - use backport:version if exact versions are needed v8.2.0 v8.3.0 labels Apr 7, 2022
@dedemorton
Copy link
Contributor Author

Ah, I see the problem here. I will fix it.

Copy link
Contributor

@gchaps gchaps left a comment

Choose a reason for hiding this comment

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

LGTM

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
fleet 684.6KB 684.3KB -270.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
core 318.7KB 318.8KB +54.0B

History

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

cc @dedemorton

@dedemorton dedemorton merged commit a583edc into elastic:main Apr 7, 2022
@dedemorton dedemorton deleted the edit_add_logstash_output_strings branch April 7, 2022 20:27
kibanamachine pushed a commit that referenced this pull request Apr 7, 2022
* Edit text strings and links in add logstash output UI

* fix test to match

* Add changes from review

* Fix tests

* Fix type

* Fix I18N error

Co-authored-by: Nicolas Chaulet <[email protected]>
Co-authored-by: gchaps <[email protected]>
(cherry picked from commit a583edc)
@kibanamachine
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
8.2

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Apr 7, 2022
)

* Edit text strings and links in add logstash output UI

* fix test to match

* Add changes from review

* Fix tests

* Fix type

* Fix I18N error

Co-authored-by: Nicolas Chaulet <[email protected]>
Co-authored-by: gchaps <[email protected]>
(cherry picked from commit a583edc)

Co-authored-by: DeDe Morton <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed release_note:skip Skip the PR/issue when compiling release notes Team:Fleet Team label for Observability Data Collection Fleet team v8.2.0 v8.3.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Request] Edit text strings for new add logstash output UI
7 participants