opendistro-for-elasticsearch / index-management-kibana-plugin Goto Github PK

There's a lot of duplication in this file and the HistogramAndMetrics file

Originally posted by @dbbaughe in #128 (comment)

There are many duplicate elements in RollupDetails/components/AggregationAnsMetricsSettings and in CreateRollup/components/HistogramAndMetrics file.

Screenshot of the HistogramAndMetrics component (title "Aggregation and metrics setting")

Screenshot of the AggregationAndMetrics component (title "Aggregation and metrics settings")

I built docker images for Kibana with "opendistro-build" scripts.
And Kibana can't start and throws below error:
{"type":"log","@timestamp":"2019-11-30T19:48:51Z","tags":["fatal","root"],"pid":1,"message":"ReferenceError: regeneratorRuntime is not defined\n at regeneratorRuntime (/usr/share/kibana/plugins/opendistro_index_management_kibana/server/services/IndexService.js:32:5)\n at new IndexService (/usr/share/kibana/plugins/opendistro_index_management_kibana/server/services/IndexService.js:29:3)\n at Plugin.init [as externalInit] (/usr/share/kibana/plugins/opendistro_index_management_kibana/index.js:49:28)\n at Object.register (/usr/share/kibana/src/legacy/server/plugins/lib/plugin.js:96:20)\n at internals.Server.register (/usr/share/kibana/node_modules/hapi/lib/server.js:431:35)\n at Plugin.init (/usr/share/kibana/src/legacy/server/plugins/lib/plugin.js:100:28)\n at Plugin.init (/usr/share/kibana/node_modules/lodash/index.js:7411:25)\n at callPluginHook (/usr/share/kibana/src/legacy/server/plugins/lib/call_plugin_hook.js:53:25)"}

Also, there are a lot of messages like below during Kibana start:

  `@babel/polyfill` is deprecated. Please, use required parts of `core-js`
  and `regenerator-runtime/runtime` separately

The index names are ellipsed when over a certain length. A tooltip was added to show them, but it would be better if they were just shown in full and wrapped to the next line as needed.

I had install Elasticsearch-OSS 7.8.0 and Kibana-OSS 7.8.0 and ODES index management plugins along with scheduler, alerting and security.

Steps to reproduce the behavior:

1. Install Elasticsearch-OSS 7.8.0, Kibana-OSS 7.8.0
2. Install all plugin as mentioned in below link in same order for Elasticsearch and Kibana.

https://opendistro.github.io/for-elasticsearch-docs/docs/install/plugins/#install-plugins
Security
Job Scheduler
Alerting
Index State Management

https://opendistro.github.io/for-elasticsearch-docs/docs/kibana/plugins/
SECURITY
ALERTING
INDEX STATE MANAGEMENT

3. We start Kibana and get below Error.

FATAL Error: Optimizations failure.
2278 modules

ERROR in ./plugins/opendistro_index_management_kibana/public/pages/CreatePolicy/components/DefinePolicy/DefinePolicy.js
Module not found: Error: Can't resolve 'brace/mode/json' in '/usr/share/kibana/plugins/opendistro_index_management_kibana/public/pages/CreatePolicy/components/DefinePolicy'

ERROR in ./plugins/opendistro_index_management_kibana/public/pages/CreatePolicy/components/DefinePolicy/DefinePolicy.js
Module not found: Error: Can't resolve 'brace/theme/github' in '/usr/share/kibana/plugins/opendistro_index_management_kibana/public/pages/CreatePolicy/components/DefinePolicy'

After removing opendistro index_management kibana plugin, Kibana works perfectly fine. Please find attached images and log file for further details.

kibana-ism-error-log.txt

• Elasticsearch-OSS 7.8.0
• Kibana-OSS 7.8.0
• open distro plugin version 1.9.0
• OS: RHEL 7.8
• JDK : OpenJDK 8

Let me know if more details are required.

Is your feature request related to a problem? Please describe.
It would be nice to be able to perform some operations on an index other than just assigning a policy, in particular delete

Describe the solution you'd like
In the indices view, when an index is selected, other buttons than assign policies could be added to perform operations on this index, like delete but also close, set readonly...

Hi,

I tried to build plugin from source:

git clone --depth 1 --branch v7.10.0 https://github.com/elastic/kibana.git
cd kibana

wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash
. $HOME/.nvm/nvm.sh || true
nvm install $(cat .nvmrc)
nvm use
npm install -g yarn

cd plugins

git clone --depth 1 --branch v1.12.0.0 https://github.com/opendistro-for-elasticsearch/index-management-kibana-plugin.git
cd index-management-kibana-plugin
yarn kbn bootstrap
yarn build

Result of last command:

ERROR [single_version_dependencies] Multiple version ranges for the same dependency
      were found declared across different package.json files. Please consolidate
      those to match across all package.json files. Different versions for the
      same dependency is not supported.

      If you have questions about this please reach out to the operations team.

      The conflicting dependencies are:

        cypress
          ^5.0.0 => x-pack
          4.3.0 => opendistro_index_management_kibana
        ts-loader
          ^7.0.5 => x-pack
          ^6.2.1 => opendistro_index_management_kibana

Is this a bug or I'm doing something wrong?

#33

Should be able to sort by different columns and filter by different column values

Describe the bug
The managed indices page caps index names at 21 character, compared to 30 characters on the indices page. The broader solution here is likely to have resizable columns, but in the meantime, it seems reasonable to give index name the same amount of space as the other page and constrict the other columns proportionally.

To Reproduce
Steps to reproduce the behavior:

1. Open Kibana
2. Add some data.
3. Go to ISM / Indices / Managed Indices.

Expected behavior
Both sections use the same default spacing for index names.

Screenshots

Desktop (please complete the following information):

• macOS Mojave
• Microsoft Edge 79

Additional context
Originally reported as opendistro/for-elasticsearch-docs#261.

We experienced a failure on the Infra side when they testing our build artifact with binary Kibana OSS.

We can capture this earlier by having an CI integration test which pulls down binary Kibana OSS and install our released build artifact for a sanity test.

#32

Plugin installation was unsuccessful due to error "Plugin opendistro_index_management_kibana [7.9.1] is incompatible with Kibana [7.9.3]"

index-management-kibana-plugin-1.10.1.0.zip

State and state transitions are confusing (State Action Status Info)

Is your feature request related to a problem? Please describe.
Currently opendistro is at version 7.2.1 and the released packages do not support it (only either 7.1.1 or 7.3.2) 7.3.2 is not released yet on opendistro docker packages.

Related to the discussion on #63 this makes it hard for us to test without downgrading

This issue was opened to track the release so that the other issue is not taken out of context

Describe the solution you'd like
@qreshi has mentioned on Related to the discussion on #63
I did notice that there are no releases made for Index Management 1.2 (both the backend and Kibana plugin) which is likely causing the confusion of missing support for ES 7.2. I'll go ahead and create those shortly but you can also build them manually using the opendistro-1.2 branches.

Plugin currently adds full name as "Index Management Kibana" in the menu of Kibana. Kibana portion is redundant and can be removed.

Describe the bug
After upgrade from 1.12 to 1.13: go to Indexmanagement / index policies: exception occurs:

But after a while the error disappeared. Also got a similar error at Managed Indices tab, that also disappeared after a while.

Can not reproduce anymore.

Other plugins installed
None

To Reproduce

Expected behavior
No error

Screenshots

Desktop (please complete the following information):
OD Docker 1.13

Additional context

Describe the bug
If you have indices named for example "my-index-001", you are not able to search using hyphens. When you type "my-" on filters it shows nothing on results despite the index really exists.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Index Management'
2. Click on 'Managed Indices'
3. Try to filter using hyphen.
4. It shows no results.

Expected behavior
It should print indices named with hyphens on results.

Additional context
Using ODFE 1.7.0.

Currently, ISM Kibana plugin directly reads .opendistro_ism_config index to show managed indices in the UI.
This issue tracks the changes to ISM Kibana to use ISM REST API

• GET opendistro-im/_ism/explain
• GET opendistro-im/_ism/policies

Is your feature request related to a problem? Please describe.
It would be great if there is a a one click option to copy the index name of the indices.

Describe the solution you'd like
A copy to clipboard option would suffice the use-case. Either it can be an individual icon for each of the index or a single one for all with a checkbox beside each index name.

Proposed design screenshot
Add any other context or screenshots about the feature request here.

like the xpack in Kibana 7.x

Describe the bug
When we try to add an index pattern for cross-cluster search Kibana fails to find fields for the indices. The cross-cluster connection seems to work as we can see the indices dev:* when querying using the Kibana dev tools. The issue also seems to break previously added index patterns as we cannot update fields

Other plugins installed
Using managed AWS Elasticsearch Service so using the plugins provided by that

To Reproduce
Steps to reproduce the behavior:

1. Set up cross-cluster connection using the Kibana and Elasticsearch versions provided
2. Attempt to add an index pattern för cross-cluster search (e.g. ccs:*)
3. Index pattern is created but no fields are found

Expected behavior
Index pattern should be added with fields.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]: Ubuntu 20.04
• Browser [e.g. chrome, safari]: Chrome Version 90.0.4430.93 (Official Build) (64-bit)
• Version [e.g. 22]: Elasticsearch 7.10.2, Kibana 7.10

Additional context
Made an issue on the Kibana project first, but this might be a better place to ask?

Original issue: elastic/kibana#99573

Describe the bug
I'm trying to define a policy that deletes an "old" index at midnight.

I'm using Opendistro 1.4 and from the documentation I see it would be possible to use CRON expressions ( Transitions )

But when I try t save it gives me an error

[illegal_argument_exception] Unknown schedule type expression

Other plugins installed
No other plugin installed

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Index Management'
2. Click on 'Create Policy'
3. Insert 'delete_at_midnight' in the 'Policy ID' field
4. Paste the following definition

 {
    "policy": {
        "policy_id": "delete_at_midnight",
        "description": "A simple default policy that deletes old indicies after 1 days.",
        "default_state": "open",
        "states": [
            {
                "name": "open",
                "actions": [
                    {
                        "open": {}
                    }
                ],
                "transitions": [
                    {
                        "state_name": "delete",
                        "conditions": {
                            "cron": {
                                "expression":"1 0 * * *",
                                "timezone":"CET"
                            }
                        }
                    }
                ]
            },
            {
                "name": "delete",
                "actions": [
                    {
                        "delete": {}
                    }
                ],
                "transitions": []
            }
        ]
    }
}

5. See error

Expected behavior
Kibana saves the policy

Desktop (please complete the following information):

• OS: Ubuntu 18.04.4 LTS
• Browser: chrome
• Version 81.0.4044.92