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

[Monitoring] Added a case for Alerting if security/ssl is disabled #71846

Merged
merged 6 commits into from
Jul 17, 2020

Conversation

igoristic
Copy link
Contributor

Fixes: #71798

This was a slight oversight on our part with alerting. This basically ensures that the Monitoring ui still works if the security (or ssl) is disabled

@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring (Team:Monitoring)

Copy link
Contributor

@chrisronline chrisronline left a comment

Choose a reason for hiding this comment

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

Awesome, great work so far! I added a few suggestions/requests

@igoristic igoristic requested a review from chrisronline July 16, 2020 01:15
@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

async chunks size

id value diff baseline
monitoring 1.2MB +5.0KB 1.2MB

History

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

<div>
<p>
{i18n.translate('xpack.monitoring.healthCheck.tlsAndEncryptionError', {
defaultMessage: `You must enable Transport Layer Security between Kibana and Elasticsearch
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 we probably want to modify this message slightly since the user didn't do any explicit actions to enable alerting and will probably have no context.

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! What do you think about:

Alerting features are not working, because your security is currently insufficient. Please enable Transport Layer Security between Kibana and Elasticsearch, and configure an encryption key in your kibana.yml file.

Any suggestions would be helpful

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure honestly. cc @ravikesarwani @lcawl @gchaps for help here

text: toMountPoint(
<div role="banner">
{i18n.translate('xpack.monitoring.healthCheck.encryptionErrorBeforeKey', {
defaultMessage: 'To create an alert, set a value for ',
Copy link
Contributor

Choose a reason for hiding this comment

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

Again, like before, the user will not understand what this means because they aren't consciously enabling or interacting with alerts

Copy link
Contributor Author

@igoristic igoristic Jul 16, 2020

Choose a reason for hiding this comment

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

Ah you're right!

Wondering if we should just use one generic message from https://github.com/elastic/kibana/pull/71846/files#r455776054 if any of the two requirements (isSufficientlySecure, and hasPermanentEncryptionKey) are false?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yea I'm not sure what we want to say here. Something like "out of the box alerts require x, y, z. See {link} on how to configure this". Honestly, I'd default to @ravikesarwani @lcawl @gchaps for help here on the messaging

Copy link
Contributor

Choose a reason for hiding this comment

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

Worked with @lcawl on the text. Does this work:

Alerting requires Transport Layer Security between Kibana and Elasticsearch and an encryption key in your kibana.yml file. Learn how to enable TLS.

where "Lean how to enable TLS" links to the documentation.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yea, I think that works. i'll open a new PR for this

Copy link
Contributor

Choose a reason for hiding this comment

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

See #72310

Copy link
Contributor

@chrisronline chrisronline left a comment

Choose a reason for hiding this comment

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

This functionally works, so let's merge it in. Can you create a follow up ticket to update the copy?

@chrisronline
Copy link
Contributor

I'm going to merge this in so it's in the next BC

@chrisronline chrisronline merged commit 39381ca into elastic:master Jul 17, 2020
chrisronline pushed a commit to chrisronline/kibana that referenced this pull request Jul 17, 2020
…lastic#71846)

* Added a case for Alerting if security/ssl is disabled

* Code feedback

* Fixed types
chrisronline added a commit that referenced this pull request Jul 17, 2020
…71846) (#72297)

* Added a case for Alerting if security/ssl is disabled

* Code feedback

* Fixed types

Co-authored-by: igoristic <igor.zaytsev.dev@gmail.com>
chrisronline added a commit that referenced this pull request Jul 17, 2020
…71846) (#72295)

* Added a case for Alerting if security/ssl is disabled

* Code feedback

* Fixed types

Co-authored-by: igoristic <igor.zaytsev.dev@gmail.com>
@chrisronline
Copy link
Contributor

Backport:

7.x: d3073f3
7.9: 8d5b16d

gmmorris added a commit to gmmorris/kibana that referenced this pull request Jul 17, 2020
* master:
  [Maps] 7.9 documenation updates (elastic#71893)
  docs: ✏️ add "Explore underlying data" user docs (elastic#70807)
  [Security Solution][Exceptions] - Remove initial add exception item button in builder (elastic#72215)
  Fix indentation level in code exploration doc (elastic#72274)
  register graph usage (elastic#72041)
  [Monitoring] Added a case for Alerting if security/ssl is disabled (elastic#71846)
@igoristic igoristic deleted the fix_alerting_security branch July 20, 2020 04:35
gmmorris added a commit to gmmorris/kibana that referenced this pull request Jul 20, 2020
* master:
  [Observability] Remove app logos (elastic#72259)
  Fix float percentiles line chart (elastic#71902)
  update chromedriver to 84 (elastic#72228)
  [esArchiver] actually re-delete the .kibana index if we lose recreate race (elastic#72354)
  [Maps] convert SavedGisMap to TS (elastic#72286)
  [DOCS] Removes occurrences of X-Pack Security and Reporting (elastic#72302)
  use WORKSPACE env var for stack_functional_integration tests, fix navigate path (elastic#71908)
  [Monitoring] Fix issue with ES node detail status (elastic#72298)
  [SIEM] Updates consumer in export_rule archive (elastic#72324)
  [kbn/dev-utils] add RunWithCommands utility (elastic#72311)
  [Security Solution][Endpoint][Exceptions] Only write manifest to policy when there are changes (elastic#72000)
  skip flaky suite (elastic#72339)
  [ML] Fix annotations pagination & change labels from letters to numbers (elastic#72204)
  [Lens] Fix switching with layers (elastic#71982)
  [Maps] 7.9 documenation updates (elastic#71893)
  docs: ✏️ add "Explore underlying data" user docs (elastic#70807)
  [Security Solution][Exceptions] - Remove initial add exception item button in builder (elastic#72215)
  Fix indentation level in code exploration doc (elastic#72274)
  register graph usage (elastic#72041)
  [Monitoring] Added a case for Alerting if security/ssl is disabled (elastic#71846)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Monitoring] Account for SSL not being enabled before calling the alerting api
5 participants