-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Lens] [Pie visualisation] incorrect visualisation for non-tsdb and tsdb data #157839
Comments
Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations) |
Is the TSDB data downsampled? |
@dej611 We are not doing anything with downsampling functionality, this is solely focused on testing the initial functionality for packages when TSDB is enabled. The scope only includes functionality in the current 8.8.0 snapshot and enabling TSDB. |
@agithomas @ritalwar can you confirm if you also see this issue? |
@tetianakravchenko Is the issue only seen for: visualisation that has Pie chart? I tried the steps below for nginx (which does not have pie chart): TSDB disabled dashboard |
Hi Kibana team, Can you confirm if there is an issue with Pie chat while mixing TSDB and non-TSDB data? |
@dej611 can you take a look when you have some time? |
I also tested it for MSSQL and, like Lalit, I am not experiencing this issue, which may be because it doesn't involve any pie chart. |
@tetianakravchenko provided an instance to reproduce the issue. The data has started coming at If the
The following is the query used in the visualization (note query timing is UTC, consider 2 hours shift, so the time interval is crossing the rollover): {
"aggs": {
"0": {
"terms": {
"field": "kubernetes.apiserver.request.resource",
"order": {
"1-bucket>1-metric[kubernetes.apiserver.etcd.object.count]": "desc"
},
"size": 10,
"shard_size": 25
},
"aggs": {
"1-bucket": {
"filter": {
"bool": {
"must": [],
"filter": [
{
"bool": {
"should": [
{
"exists": {
"field": "kubernetes.apiserver.etcd.object.count"
}
}
],
"minimum_should_match": 1
}
}
],
"should": [],
"must_not": []
}
},
"aggs": {
"1-metric": {
"top_metrics": {
"metrics": {
"field": "kubernetes.apiserver.etcd.object.count"
},
"size": 1,
"sort": {
"@timestamp": "desc"
}
}
}
}
}
}
}
},
"size": 0,
"fields": [
{
"field": "@timestamp",
"format": "date_time"
},
{
"field": "event.ingested",
"format": "date_time"
},
{
"field": "kubernetes.container.start_time",
"format": "date_time"
},
{
"field": "kubernetes.event.metadata.timestamp.created",
"format": "date_time"
},
{
"field": "kubernetes.event.timestamp.first_occurrence",
"format": "date_time"
},
{
"field": "kubernetes.event.timestamp.last_occurrence",
"format": "date_time"
},
{
"field": "kubernetes.node.start_time",
"format": "date_time"
},
{
"field": "kubernetes.pod.start_time",
"format": "date_time"
},
{
"field": "kubernetes.service.created",
"format": "date_time"
},
{
"field": "kubernetes.storageclass.created",
"format": "date_time"
},
{
"field": "kubernetes.system.start_time",
"format": "date_time"
},
{
"field": "process.cpu.start_time",
"format": "date_time"
},
{
"field": "system.process.cpu.start_time",
"format": "date_time"
}
],
"script_fields": {},
"stored_fields": [
"*"
],
"runtime_mappings": {},
"_source": {
"excludes": []
},
"query": {
"bool": {
"must": [],
"filter": [
{
"match_phrase": {
"data_stream.dataset": "kubernetes.apiserver"
}
},
{
"range": {
"@timestamp": {
"format": "strict_date_optional_time",
"gte": "2023-05-16T14:13:00.122Z",
"lte": "2023-05-16T14:25:44.122Z"
}
}
}
],
"should": [],
"must_not": []
}
}
} The response for the query above is the following: {
"took": 1808,
"timed_out": false,
"_shards": {
"total": 34,
"successful": 34,
"skipped": 0,
"failed": 0
},
"hits": {
"total": {
"value": 10000,
"relation": "gte"
},
"max_score": null,
"hits": []
},
"aggregations": {
"0": {
"doc_count_error_upper_bound": -1,
"sum_other_doc_count": 8282,
"buckets": [
{
"key": "allowlistedworkloads",
"doc_count": 88,
"1-bucket": {
"doc_count": 0,
"1-metric": {
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:23:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": null
}
}
]
}
},
{
"key": "apiservices",
"doc_count": 242,
"1-bucket": {
"doc_count": 0,
"1-metric": {
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:23:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": null
}
}
]
}
},
{
"key": "backendconfigs",
"doc_count": 44,
"1-bucket": {
"doc_count": 0,
"1-metric": {
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:23:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": null
}
}
]
}
},
{
"key": "certificatesigningrequests",
"doc_count": 132,
"1-bucket": {
"doc_count": 0,
"1-metric": {
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:23:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": null
}
}
]
}
},
{
"key": "clusterrolebindings",
"doc_count": 198,
"1-bucket": {
"doc_count": 0,
"1-metric": {
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:23:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": null
}
}
]
}
},
{
"key": "clusterroles",
"doc_count": 198,
"1-bucket": {
"doc_count": 0,
"1-metric": {
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:23:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": null
}
}
]
}
},
{
"key": "componentstatuses",
"doc_count": 44,
"1-bucket": {
"doc_count": 0,
"1-metric": {
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:23:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": null
}
}
]
}
},
{
"key": "cronjobs",
"doc_count": 88,
"1-bucket": {
"doc_count": 0,
"1-metric": {
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:23:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": null
}
}
]
}
},
{
"key": "csidrivers",
"doc_count": 88,
"1-bucket": {
"doc_count": 0,
"1-metric": {
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:23:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": null
}
}
]
}
},
{
"key": "csinodes",
"doc_count": 242,
"1-bucket": {
"doc_count": 0,
"1-metric": {
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:23:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": null
}
}
]
}
}
]
}
}
} Now if I change the {
"took": 2728,
"timed_out": false,
"_shards": {
"total": 34,
"successful": 34,
"skipped": 0,
"failed": 0
},
"hits": {
"total": {
"value": 10000,
"relation": "gte"
},
"max_score": null,
"hits": []
},
"aggregations": {
"0": {
"doc_count_error_upper_bound": -1,
"sum_other_doc_count": 5776,
"buckets": [
{
"key": "clusterroles.rbac.authorization.k8s.io",
"doc_count": 16,
"1-bucket": {
"doc_count": 16,
"1-metric": {
"hits": {
"total": {
"value": 16,
"relation": "eq"
},
"max_score": null,
"hits": [
{
"_index": "xxxxxxx",
"_id": "yyyyyyyy",
"_score": null,
"fields": {
"kubernetes.apiserver.etcd.object.count": [
100
]
},
"sort": [
1684246844010
]
}
]
}
}
},
"0-orderAgg": {
"top": [
{
"sort": [
"2023-05-16T14:20:44.010Z"
],
"metrics": {
"kubernetes.apiserver.etcd.object.count": 100
}
}
]
}
},
...
]
}
}
} |
Not clear what is the exact issue? Is this issue applicable only for Pie charts or other visualisations also?
@martijnvg, Can you help confirm if this elasticsearch problem? |
Any query/visualization with a |
The integrations i have been testing does not have any pie-cart to verify this. So, couldn't find a usecase yet to verify. |
@dej611 This looks strange and is unexpected. Can you open an ES issue? Does the search response returns shards failures? |
@martijnvg no shards failures. |
Could you share mappings for the index? At least for the two fields involved...resource and count. Probably they are keyword and counter. |
It would be helpful also to have the setting for both involved indices. |
@constanca-m can you liaise with @salvatore-campagna to make this info available? |
@salvatore-campagna , the resource is a keyword:
And the count is of type gauge:
|
Had to attach both mappings and settings as txt as they were too big. |
As described in elastic/elasticsearch#96192 I tried to reproduce this issue using a YAML test but I did not manage. I wonder if there is any chance to look at Elasticsearch logs and see if there is anything there which might help. |
Would it be possible to run the query using |
We should consider to rename this issue into something closer to the actual problem. |
@dej611 do you think we can close it as it is not a kibana issue and it will be solved when ES fixes it? |
I would rather prefer to keep it open but with a meaningful title and labels to track it. |
Discussed offline and decided to close this and track only the ES one. |
Kibana version:
8.8.0-SNAPSHOT
Elasticsearch version:
8.8.0-SNAPSHOT
Server OS version:
Browser version:
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.):
elastic-package local setup
Describe the bug:
Pie visualisation that contains non-TSDB and TSDB data does not provide correct data
Steps to reproduce:
Expected behavior:
For Non-TSDB data, for Non-TSDB and TSDB data, and for only TSDB data behavior is the same and correct
Screenshots (if relevant):
explanation:
Screen.Recording.2023-05-16.at.10.14.56.mov
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
The text was updated successfully, but these errors were encountered: