Conversation
|
Pinging @elastic/uptime (Team:uptime) |
andrewvc
left a comment
There was a problem hiding this comment.
Thanks so much for adding these. Looks like there's an extra image file named Screen Shot 2020-05-11 at 2.44.25 PM.png . Left some additional comments as well. Would be great to get @bmorelli25 's feedback as well.
docs/uptime/certificates.asciidoc
Outdated
There was a problem hiding this comment.
Our docs generally use the active voice ( I can't find a citation, but maybe @bmorelli25 has one?) . This could be written: "Use the certificates page to visualize all of your TLS certificates..."
There was a problem hiding this comment.
The Elastic guide to writing style talks about active voice.
There was a problem hiding this comment.
Please have a look at 24ff319 where I've tried to prefer active voice as much as I could. I also tried to simplify a large chunk of the copy I had added.
docs/uptime/settings.asciidoc
Outdated
There was a problem hiding this comment.
Active voice: "Specify thresholds for all TLS certificates on the settings page"
docs/uptime/settings.asciidoc
Outdated
There was a problem hiding this comment.
I don't think we need to be this descriptive, that part of the app is self explanatory. IMHO we shouldn't document the obvious. Would like @bmorelli25 's thoughts here.
Perhaps the content would be better if it described what the fields vs. documenting their existence. Rephrasing this as: "Use the certificate maximum age field to control the number of days before expiration Uptime should display the certificate as being in a warning state. Warnings for maximum certificate age can also be set here. Some user agents and browsers consider certificates invalid after a certain amount of time.
There was a problem hiding this comment.
Agreed. But looking at the screenshot, I only see "Expiration threshold" and "Age limit" as options. The docs should match those names. I'd alter Andrew's recommendation to something like this:
The settings page also allows you to specify thresholds for displaying and alerting on TLS certificates. Use the expiration threshold to specify <>, and the age limit field to control the <>. Some user agents and browsers consider certificates invalid after a certain amount of time.
docs/uptime/settings.asciidoc
Outdated
There was a problem hiding this comment.
This could be moved up IMHO to make the importance more clear.
There was a problem hiding this comment.
Yes, this should be in the first paragraph
…ersion of this after we merge updated defaults for age limit threshold.
fad4c40 to
2ecbbfd
Compare
This was supposed to be a draft but I guess I marked it as ready 😿 I left that as a placeholder to remind me to re-take that screenshot after #66135 was merged. I have subsequently added commits that fix this. |
docs/uptime/settings.asciidoc
Outdated
| For example, you may want to make sure that none of your organization's TLS certificates have been | ||
| valid for longer than one year. This is becoming a common security requirement. Modifying the `Age limit` |
There was a problem hiding this comment.
| For example, you may want to make sure that none of your organization's TLS certificates have been | |
| valid for longer than one year. This is becoming a common security requirement. Modifying the `Age limit` | |
| For example, a common security requirement is to make sure that none of your organization's TLS certificates have been valid for longer than one year. Modifying the `Age limit` |
@bmorelli25 I updated the copy in 141c28e. Thanks! Feel free to comment on any more of the copy I've added, these recommendations are super helpful. |
| @@ -0,0 +1,26 @@ | |||
| [role="xpack"] | |||
There was a problem hiding this comment.
When I view the documentation preview for this page, I'm presented with two images without any context: http://kibana_66118.docs-preview.app.elstc.co/guide/en/kibana/7.8/uptime-alerting.html
I think we should move the paragraphs (context) above each of the screenshots.
| == Uptime alerting | ||
|
|
There was a problem hiding this comment.
Should we add an alerting overview here? Something like:
The Uptime app integrates with Kibana's {kibana-ref}/alerting-getting-started.html[alerting and actions] feature. It provides a set of built-in actions and Uptime specific threshold alerts for you to use
and enables central management of all alerts from <<management,Kibana Management>>.
|
@elasticmachine merge upstream |
|
Hi @justinkambic Would it be possible to merge this PR before Wednesday? Next week, as part of the Observability docs restructuring, I plan to move the Uptime documentation in the Kibana reference to the Uptime guide and it would be great to include this new content. Thanks! |
|
@elasticmachine merge upstream |
* Refresh existing docs images. * Add tls-related images. * Add certificates page to docs. * Update settings page with explanation of cert threshold fields. * Add placeholder image of updated settings page. Will need finalized version of this after we merge updated defaults for age limit threshold. * Add new alerting docs page. * Refresh settings page image. * Implement feedback and re-write/simplify some sections. * Clean up words. * Implement feedback on sentence structure. * Improve copy on alerting page. * Improve copy on settings page. * Update layout on alerting page. Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Refresh existing docs images. * Add tls-related images. * Add certificates page to docs. * Update settings page with explanation of cert threshold fields. * Add placeholder image of updated settings page. Will need finalized version of this after we merge updated defaults for age limit threshold. * Add new alerting docs page. * Refresh settings page image. * Implement feedback and re-write/simplify some sections. * Clean up words. * Implement feedback on sentence structure. * Improve copy on alerting page. * Improve copy on settings page. * Update layout on alerting page. Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
Adds docs to 7.8. We'll forward-port this change to
masterafter merging.Checklist
Delete any items that are not applicable to this PR.
For maintainers