github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 17:59:23 -04:00
Code Issues Projects Releases Packages Wiki Activity

[6.8] Fixing typo in Stack Monitoring error message (#42889) (#42955)

Browse source 
* Fixing typo

* Updating jest snapshots

* Adding missing trailing whitespace :|
This commit is contained in:
Shaunak Kashyap 2019-08-08 10:19:32 -07:00 • committed by GitHub
parent 2eff7f959e
commit 6dfb7adaef
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
x-pack/plugins/monitoring/public/components/no_data/explanations/exporters/__tests__/__snapshots__/exporters.test.js.snap
View file

@ -58,7 +58,7 @@ Array [
.
</p>
<p>
Using monitoring exporters ship the monitoring data to a remote monitoring cluster is highly recommended as it keeps the integrity of the monitoring data safe no matter what the state of the production cluster. However, as this instance of Kibana could not find any monitoring data, there seems to be a problem with the
Using monitoring exporters to ship the monitoring data to a remote monitoring cluster is highly recommended as it keeps the integrity of the monitoring data safe no matter what the state of the production cluster. However, as this instance of Kibana could not find any monitoring data, there seems to be a problem with the
<span
class="euiCodeBlock euiCodeBlock--fontSmall euiCodeBlock--paddingLarge euiCodeBlock--inline"
>

2
x-pack/plugins/monitoring/public/components/no_data/explanations/exporters/exporters.js
View file

@ -36,7 +36,7 @@ export function ExplainExporters({ context, property, data }) {
<p>
<FormattedMessage
id="xpack.monitoring.noData.explanations.exporters.problemWithConfigDescription"
defaultMessage="Using monitoring exporters ship the monitoring data to a remote
defaultMessage="Using monitoring exporters to ship the monitoring data to a remote
monitoring cluster is highly recommended as it keeps the integrity of
the monitoring data safe no matter what the state of the production
cluster. However, as this instance of Kibana could not find any

2
x-pack/plugins/monitoring/public/components/no_data/reasons/__tests__/__snapshots__/reason_found.test.js.snap
View file

@ -141,7 +141,7 @@ Array [
.
</p>
<p>
Using monitoring exporters ship the monitoring data to a remote monitoring cluster is highly recommended as it keeps the integrity of the monitoring data safe no matter what the state of the production cluster. However, as this instance of Kibana could not find any monitoring data, there seems to be a problem with the
Using monitoring exporters to ship the monitoring data to a remote monitoring cluster is highly recommended as it keeps the integrity of the monitoring data safe no matter what the state of the production cluster. However, as this instance of Kibana could not find any monitoring data, there seems to be a problem with the
<span
class="euiCodeBlock euiCodeBlock--fontSmall euiCodeBlock--paddingLarge euiCodeBlock--inline"
>