You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,11 +11,17 @@ Logsearch < v23.0.0 was based on Elasticsearch 1.x and Kibana 3.
11
11
12
12
Logsearch > v200 is based on Elasticsearch 2.x and Kibana 4.
13
13
14
-
There is NO upgrade path from Elasticsearch 1.x to 2.x. Sorry :(
14
+
-There is NO upgrade path from Elasticsearch 1.x to 2.x. Sorry :(
15
15
16
-
Logsearch > v204.0.0 is based on Elasticsearch 5.x and Kibana 5.
16
+
Logsearch > v204.0.0 is based on Elastic stack version 5.
17
+
18
+
- For upgrade procedure from Elasticsearch 2.x please refer to [v205.0.0 release notes](https://github.com/cloudfoundry-community/logsearch-boshrelease/releases/tag/v205.0.0#component-updates).
19
+
20
+
Logsearch > v210.0.0 is based on Elastic stack version 6.
21
+
22
+
- Elasticsearch 6.x can use indices created in Elasticsearch 5.x, but not those created in Elasticsearch 2.x or before.
23
+
-**Important**: After upgrading running 5.x cluster to 6.x all existing indicies will be available for reading data. However, writing to these indicies is not possible. In order to write data immediatelly after upgrade you have to [change index naming convention](https://github.com/cloudfoundry-community/logsearch-boshrelease/commit/2f83b41ee14dbe3141e21cc0c40df340d50e0169). As long as index names are usually based on current date, this change can be safely reverted in a day or so.
17
24
18
-
For upgrade procedure from Elasticsearch 2.x please refer to [v205.0.0 release notes](https://github.com/cloudfoundry-community/logsearch-boshrelease/releases/tag/v205.0.0#component-updates).
Copy file name to clipboardExpand all lines: deployment/operations/README.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,4 +28,10 @@ Includes [logsearch-for-cloudfoundry](https://github.com/cloudfoundry-community/
28
28
29
29
To use this extention, you have to provide following variables: `cf_admin_password`, `uaa_admin_client_secret` and `system_domain`. You can find them in your CloudFoundry deployment variables.
30
30
31
-
After deployment, please run `create-uaa-client` errand to create UAA client. After that, you will be able to login into Logsearch UI using your CloudFoundry credentials, and use `https://logs.<YOUR_DOMAIN>` endpoint to access Logsearch UI.
31
+
After deployment, please run `create-uaa-client` errand to create UAA client. After that, you will be able to login into Logsearch UI using your CloudFoundry credentials, and use `https://logs.<YOUR_DOMAIN>` endpoint to access Logsearch UI.
32
+
33
+
## cf-kibana.yml
34
+
Errand to push Kibana application into CloudFoundry as an alternative to running it as a separate job.
0 commit comments