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

Sunburst pulls the wrong data for one index #3

Open
maggiedeblock opened this issue Jan 15, 2017 · 5 comments
Open

Sunburst pulls the wrong data for one index #3

maggiedeblock opened this issue Jan 15, 2017 · 5 comments

Comments

@maggiedeblock
Copy link

maggiedeblock commented Jan 15, 2017

Good evening,

I'm having an issue with the Sunburst plugin displaying the wrong information for one particular index (sent over from ntopng). Whenever I use the IPV4 SRC / DST addresses as a ring on this diagram, it shows the "key" instead of the actual IP address. However, in the table you pull up from the bottom of the diagram, it shows the correct information in the column. This is the only visualization that has this issue with my ntopng output. See below for the actual request / response:

Request:

{
  "size": 0,
  "query": {
    "filtered": {
      "query": {
        "query_string": {
          "analyze_wildcard": true,
          "query": "*"
        }
      },
      "filter": {
        "bool": {
          "must": [
            {
              "range": {
                "@timestamp": {
                  "gte": 1484391657358,
                  "lte": 1484478057358,
                  "format": "epoch_millis"
                }
              }
            }
          ],
          "must_not": []
        }
      }
    }
  },
  "aggs": {
    "2": {
      "terms": {
        "field": "IPV4_DST_ADDR",
        "size": 5,
        "order": {
          "_count": "desc"
        }
      }
    }
  }
}

Response:

{
  "took": 4,
  "timed_out": false,
  "_shards": {
    "total": 5,
    "successful": 5,
    "failed": 0
  },
  "hits": {
    "total": 16576,
    "max_score": 0,
    "hits": []
  },
  "aggregations": {
    "2": {
      "doc_count_error_upper_bound": 78,
      "sum_other_doc_count": 7296,
      "buckets": [
        {
          "key": 3232236306,
          "key_as_string": "192.168.3.18",
          "doc_count": 3569
        },
        {
          "key": 4026531834,
          "key_as_string": "239.255.255.250",
          "doc_count": 2264
        },
        {
          "key": 3232236543,
          "key_as_string": "192.168.3.255",
          "doc_count": 2101
        },
        {
          "key": 3232236289,
          "key_as_string": "192.168.3.1",
          "doc_count": 542
        },
        {
          "key": 3232236380,
          "key_as_string": "192.168.3.92",
          "doc_count": 278
        }
      ]
    }
  }
}
@JuanCarniglia
Copy link
Owner

JuanCarniglia commented Jan 16, 2017 via email

@maggiedeblock
Copy link
Author

Here is the chart itself with the configuration off to the left:
sunburst_chart
Here is the table showing the correct values:
sunburst_table

@JuanCarniglia
Copy link
Owner

JuanCarniglia commented Jan 18, 2017 via email

@maggiedeblock
Copy link
Author

It appears to be doing a conversion to INT at some point, going off the results of that calculator. Would that be on the end of the visualization, ES or the ntopng software?

@maggiedeblock
Copy link
Author

I'm not sure if it's on the visualization end or my end. It displays properly in all other Visualizations, just not Sunburst. The only other time I've had an issue is with the Elastic Graph plugin not liking the same field.

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

2 participants