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

ip_range type not fully supported #23822

Closed
ghost opened this issue Oct 4, 2018 · 3 comments
Closed

ip_range type not fully supported #23822

ghost opened this issue Oct 4, 2018 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@ghost
Copy link

ghost commented Oct 4, 2018

Kibana version: 6.3.0

Elasticsearch version: 6.3.0

Server OS version: Ubuntu 16.04

Browser version: Chrome 69

Browser OS version: Windows 10

Original install method (e.g. download page, yum, from source, etc.): download page

Description of the problem including expected versus actual behavior: When defining an Elastic template with a field of type ip_range, it is expected that Kibana:

  • recognizes this field as being of type ip_range when an IP range in CIDR format is inserted in this field, - allows to search inside the range in Discover,
  • allows to add this field as a filter and
  • allows to do aggregations on it.

Instead of that the field doesn't appear to be recognized (it is shown with a question mark in Discover and as unknown in Index Patterns) but it is possible to search inside the IP range in Discover. Furthermore, it is not possible to:

  • add this field as a filter through Add a filter (it doesn't show in the Filter list) but it can be added by clicking on the asterisk next to the field in a document preview,
  • do aggregations on it.

Steps to reproduce:

  1. PUT template/test-foo
    {
    "order": 1,
    "version": 1,
    "index_patterns": ["test-foo"],
    "settings": {
    "index": {
    "refresh_interval": "30s",
    "analysis": {
    "analyzer": {
    "url_analyzer": {
    "type": "pattern",
    "pattern": "\W|
    ",
    "lowercase": true
    }
    }
    },
    "number_of_shards": "3",
    "number_of_replicas": "1"
    }
    },
    "mappings": {
    "_doc": {
    "properties": {
    "net_range": {
    "type": "ip_range"
    }
    }
    }
    }
    }
  2. PUT test-foo/_doc/1
    {
    "net_range" : "192.168.0.0/12"
    }
  3. Add test-foo as an index pattern and check in Discover
@ghost ghost changed the title ip_range type not fully handled ip_range type not fully supported Oct 4, 2018
@bhavyarm bhavyarm added bug Fixes for quality problems that affect the customer experience Feature:Discover Discover Application labels Oct 10, 2018
@bhavyarm
Copy link
Contributor

pinging @elastic/kibana-discovery

@jbudz jbudz added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Oct 10, 2018
@timroes timroes added enhancement New value added to drive a business result and removed Feature:Discover Discover Application labels Oct 19, 2018
@timroes
Copy link
Contributor

timroes commented Oct 19, 2018

Duplicate of #22619

@timroes timroes marked this as a duplicate of #22619 Oct 19, 2018
@timroes timroes closed this as completed Oct 19, 2018
@joealex
Copy link

joealex commented Sep 22, 2020

What is the plan for ip_range support in Kibana

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

4 participants