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

where do i create default index pattern? #7504

Closed
babatundebusari opened this issue Jun 20, 2016 · 9 comments
Closed

where do i create default index pattern? #7504

babatundebusari opened this issue Jun 20, 2016 · 9 comments

Comments

@babatundebusari
Copy link

babatundebusari commented Jun 20, 2016

i am trying to setup ELK stack with collectd on Ubuntu 16.04 LTS (so pretty much latest version of stack available)
kibana is behind nginx proxy (followed this guide https://www.digitalocean.com/community/tutorials/how-to-install-elasticsearch-logstash-and-kibana-elk-stack-on-ubuntu-16-04)

and all looking good up until going to kibana dashboard

Index Patterns 

Warning No default index pattern. You must select or create one to continue.
unable to fetch mapping do you have indices matching the pattern

ELK stack is on one server so everything on localhost

kibana1

:~# curl 127.0.0.1:9200`
{
  "name" : "Flex",
  "cluster_name" : "elk-00",
  "version" : {
    "number" : "2.3.3",
    "build_hash" : "218bdf10790eef486ff2c41a3df5cfa32dadcfde",
    "build_timestamp" : "2016-05-17T15:40:04Z",
    "build_snapshot" : false,
    "lucene_version" : "5.5.0"
  },
  "tagline" : "You Know, for Search"
:~# service logstash configtest
Configuration OK

kibana2

My question, very specific

1. How do i create defualt index file?
2. What is path of this default index file or located? also i hear about .kibana, where is this file .kibana located?
3. Why wasn't this index file automatically created for me? What do i do to make sure it automatically works without manually doing anything else?

@Bargs
Copy link
Contributor

Bargs commented Jun 20, 2016

@babatundebusari I would suggest reading through the getting started guide (https://www.elastic.co/guide/en/kibana/current/getting-started.html). This will explain what a default index pattern is.

In a nutshell: it's not a file. You need to add data to elasticsearch. Once you have, you can configure an index pattern from the first screen you posted, which will tell Kibana where to look for you data in Elasticsearch.

If you have further issues, feel free to ask questions in our Discussion forums: https://discuss.elastic.co/c/kibana

@Bargs Bargs closed this as completed Jun 20, 2016
@babatundebusari
Copy link
Author

so just load random data?

Also in this tutorial, where did the person load data to elasticsearch but their own setup worked.
Maybe they omitted that part but how come tutorials online never show the step to load data into elastic search?

Also do i just load "random" data into elasticsearch? just to let kibana work? i mean is that what is required?

@Bargs
Copy link
Contributor

Bargs commented Jun 20, 2016

Kibana is a tool for visualizing data in Elasticsearch, so yes, you need data in Elasticsearch to work with Kibana.

The docs page I linked you to specifically shows you how to load data.

@Mohammadtrabelsi
Copy link

I think that link my help create-pattern

@viveksamaga
Copy link

@babatundebusari were you able to load the index? Am facing the same issue too!
have installed filebeat and configured everything.

@shershen08
Copy link

If you've followed the steps described in - https://www.elastic.co/guide/en/kibana/current/getting-started.html) and after doing Loading Sample Data you see on http://localhost:9200/_cat/indices?v
the same (or simmilar)

health status index uuid pri rep docs.count docs.deleted store.size pri.store.size yellow open shakespeare 38xy7pxLQtq7Yr2IAKvUPQ 5 1 111396 0 27.6mb 27.6mb

then you can place the name of the index in that form
screenshot from 2017-09-25 12-46-39

@sangeetawakhale
Copy link

I followed the steps described in - https://www.elastic.co/guide/en/kibana/current/getting-started.html) and after doing Loading Sample Data I see on http://localhost:9200/_cat/indices?v

health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
yellow open shakespeare WRq2dTy8SEywC0RXXyqi0A 5 1 0 0 1.2kb 1.2kb
yellow open logstash-2015.05.20 6EA6TdEyS5SndNCNKwgEIA 5 1 0 0 1.2kb 1.2kb
yellow open bank 6FH3tOJTT9eOA8Pz0MUZUg 5 1 1000 0 496.7kb 496.7kb
yellow open .kibana RePbtsq3QRGhouDc7l_43g 1 1 1 0 3.6kb 3.6kb
yellow open logstash-2015.05.18 ZapQFYbBQw2pBbNxMHODQg 5 1 0 0 1.2kb 1.2kb
yellow open logstash-2015.05.19 vOT8Yg0PQ5WEg94mOb7ptA 5 1 0 0 1.2kb 1.2kb

then when I place the name of the index in that form as shakespeare and click on create button then nothing happens.
image

@sangeetawakhale
Copy link

I was able to resolve this. The elasticsearch logs showed:
[o.e.c.r.a.DiskThresholdMonitor] [6orZRcf] high disk watermark [90%]
This was because all indexes get locked when the disk threshold is reached and never get unlocked when space is freed.
To unlock all indexes manually:
curl -XPUT -H "Content-Type: application/json" https://[YOUR_ELASTICSEARCH_ENDPOINT]:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'
Got from : #13685

@apoorvkhare07
Copy link

@sangeetawakhale I am getting facing the same issue right now.
Even after creating a new index its says "No default index pattern. You must select or create one to continue.". Can you help with this ?

cee-chen added a commit that referenced this issue Feb 20, 2024
`v93.0.0` ⏩ `v93.1.1`

---

## [`v93.1.1`](https://github.com/elastic/eui/releases/v93.2.0)

**This is a patch release primarily intended for use by Kibana.**

- Added top-level `EuiTreeView.Item` export
([#7526](elastic/eui#7526))

## [`v93.1.0`](https://github.com/elastic/eui/releases/v93.1.0)

- Added `index` glyph to `EuiIcon`
([#7498](elastic/eui#7498))
- Updated `EuiHighlight` to accept an array of `search` strings, which
allows highlighting multiple, separate words within its children. This
new type and behavior *only* works if `highlightAll` is also set to
true. ([#7496](elastic/eui#7496))
- Updated `EuiContextMenu` with a new `panels.items.renderItem`
property, which allows rendering completely custom items next to
standard `EuiContextMenuItem` objects
([#7510](elastic/eui#7510))
- `EuiSuperDatePicker` updates:
- Updated `EuiSuperDatePicker` with a new `refreshIntervalUnits` prop.
Passing this prop allows controlling and overriding the default unit
rounding behavior. ([#7501](elastic/eui#7501))
- Updated `EuiAutoRefresh` and `EuiRefreshInterval` with a new
`intervalUnits` prop. Passing this prop allows controlling and
overriding the default unit rounding behavior.
([#7501](elastic/eui#7501))
- Updated `onRefreshChange` to pass back a new `intervalUnits` key that
contains the current interval unit format (seconds, minutes, or hours).
([#7501](elastic/eui#7501))
- Updated `EuiSuperDatePicker` with a new `canRoundRelativeUnits` prop,
which defaults to true (current behavior). To preserve displaying the
unit that users select for relative time, set this to false.
([#7502](elastic/eui#7502))
- Updated `EuiSuperDatePicker` with a new `refreshMinInterval` prop,
which accepts a minimum number in milliseconds
([#7516](elastic/eui#7516))
- Updated `EuiAutoRefresh` and `EuiRefreshInterval` with a new
`minInterval` prop, which accepts a minimum number in milliseconds
([#7516](elastic/eui#7516))

**Bug fixes**

- Fixed `EuiHighlight` to not parse `search` strings as regexes
([#7496](elastic/eui#7496))
- Fixed `EuiSuperDatePicker` submit bug when used within `<form>`
elements ([#7504](elastic/eui#7504))
- Fixed an `EuiTreeView` bug where `aria-expanded` was being applied to
items without expandable children
([#7513](elastic/eui#7513))

**CSS-in-JS conversions**

- Converted `EuiTreeView` to Emotion. Updates as part of the conversion:
([#7513](elastic/eui#7513))
  - Removed `.euiTreeView__wrapper` div node
  - Enforced consistent `icon` size based on `display` size
fkanout pushed a commit to fkanout/kibana that referenced this issue Mar 4, 2024
`v93.0.0` ⏩ `v93.1.1`

---

## [`v93.1.1`](https://github.com/elastic/eui/releases/v93.2.0)

**This is a patch release primarily intended for use by Kibana.**

- Added top-level `EuiTreeView.Item` export
([elastic#7526](elastic/eui#7526))

## [`v93.1.0`](https://github.com/elastic/eui/releases/v93.1.0)

- Added `index` glyph to `EuiIcon`
([elastic#7498](elastic/eui#7498))
- Updated `EuiHighlight` to accept an array of `search` strings, which
allows highlighting multiple, separate words within its children. This
new type and behavior *only* works if `highlightAll` is also set to
true. ([elastic#7496](elastic/eui#7496))
- Updated `EuiContextMenu` with a new `panels.items.renderItem`
property, which allows rendering completely custom items next to
standard `EuiContextMenuItem` objects
([elastic#7510](elastic/eui#7510))
- `EuiSuperDatePicker` updates:
- Updated `EuiSuperDatePicker` with a new `refreshIntervalUnits` prop.
Passing this prop allows controlling and overriding the default unit
rounding behavior. ([elastic#7501](elastic/eui#7501))
- Updated `EuiAutoRefresh` and `EuiRefreshInterval` with a new
`intervalUnits` prop. Passing this prop allows controlling and
overriding the default unit rounding behavior.
([elastic#7501](elastic/eui#7501))
- Updated `onRefreshChange` to pass back a new `intervalUnits` key that
contains the current interval unit format (seconds, minutes, or hours).
([elastic#7501](elastic/eui#7501))
- Updated `EuiSuperDatePicker` with a new `canRoundRelativeUnits` prop,
which defaults to true (current behavior). To preserve displaying the
unit that users select for relative time, set this to false.
([elastic#7502](elastic/eui#7502))
- Updated `EuiSuperDatePicker` with a new `refreshMinInterval` prop,
which accepts a minimum number in milliseconds
([elastic#7516](elastic/eui#7516))
- Updated `EuiAutoRefresh` and `EuiRefreshInterval` with a new
`minInterval` prop, which accepts a minimum number in milliseconds
([elastic#7516](elastic/eui#7516))

**Bug fixes**

- Fixed `EuiHighlight` to not parse `search` strings as regexes
([elastic#7496](elastic/eui#7496))
- Fixed `EuiSuperDatePicker` submit bug when used within `<form>`
elements ([elastic#7504](elastic/eui#7504))
- Fixed an `EuiTreeView` bug where `aria-expanded` was being applied to
items without expandable children
([elastic#7513](elastic/eui#7513))

**CSS-in-JS conversions**

- Converted `EuiTreeView` to Emotion. Updates as part of the conversion:
([elastic#7513](elastic/eui#7513))
  - Removed `.euiTreeView__wrapper` div node
  - Enforced consistent `icon` size based on `display` size
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants