Oh hey there @bm11100!
As you mentioned, since cases are stored as SO's you'll need to query the .kibana
directly if you want to perform aggregations on them (since SO aggs aren't supported within Kibana Visualizations yet). Heavy caveat here though that the .kibana
index is a system index
and there are future plans to restrict direct access by default, and that modifying anything directly within this index can result in serious problems.
That said, these appear to be all the different case
related SO types:
So you should be able to query for each of these in dev tools ala:
GET .kibana*/_search
{
"size": 10000,
"query": {
"term": {
"type": {
"value": "cases"
}
}
}
}
and get a response with cases like:
#! this request accesses system indices: [.kibana_8.1.0_001], but in a future major version, direct access to system indices will be prevented by default
{
"took": 0,
"timed_out": false,
"_shards": {
"total": 1,
"successful": 1,
"skipped": 0,
"failed": 0
},
"hits": {
"total": {
"value": 1,
"relation": "eq"
},
"max_score": 6.728628,
"hits": [
{
"_index": ".kibana_8.1.0_001",
"_id": "cases:2c174a70-6ff4-11ec-97eb-6b110029d6b5",
"_score": 6.728628,
"_source": {
"cases": {
"type": "individual",
"title": "New Case From Alert",
"tags": [
"case'"
],
"description": "Hope all has been well Brent! :)",
"settings": {
"syncAlerts": true
},
"owner": "securitySolution",
"closed_at": null,
"closed_by": null,
"created_at": "2022-01-07T19:58:24.408Z",
"created_by": {
"username": "elastic",
"email": null,
"full_name": null
},
"status": "open",
"updated_at": "2022-01-07T19:58:26.189Z",
"updated_by": {
"full_name": null,
"email": null,
"username": "elastic"
},
"connector": {
"name": "none",
"type": ".none",
"fields": []
},
"external_service": null
},
"type": "cases",
"references": [],
"namespaces": [
"default"
],
"migrationVersion": {
"cases": "8.0.0"
},
"coreMigrationVersion": "8.1.0",
"updated_at": "2022-01-07T19:58:26.192Z"
}
},
]
}
}
Hope this helps!
Cheers!
Garrett