Widget

Cortex XSOAR API

Widget describe a widget component used to get statistics requests, based on parameters such as dataType and widgetType. A widget can be a part of widgets collection inside a dashboard.
Cache
optional
Cache of join functions
accounts
optional
Accounts list of accounts to query the widget data from
cacheVersn
optional
format: int64
category
optional
Category the widget is related to. Used to display in widget library under category or dataType if empty.
commitMessage
optional
created
optional
format: date-time
dataType
optional
Data type of the widget. Describes what data does the widget query. supporting data types "incidents","messages","system","entries","tasks", "audit".
dateRange
optional
DateRange
definition
optional
GenericObjectDefinition
definitionId
optional
description
optional
The description of the widget's usage and data representation.
fromServerVersion
optional
Version
highlight
optional
id
optional
ignoreWorkers
optional
Do not use workers mechanism while searching bleve
indexName
optional
isPredefined
optional
Is the widget a system widget.
itemVersion
optional
Version
locked
optional
Is the widget locked for editing.
modified
optional
format: date-time
name
required
Default name of the widget.
numericId
optional
format: int64
packID
optional
packName
optional
packPropagationLabels
optional
page
optional
0-based page format: int64
params
optional
Additional parameters for this widget, depends on widget type and data.
prevName
optional
The previous name of the widget.
primaryTerm
optional
format: int64
propagationLabels
optional
query
optional
Query to search on the dataType.
remote
optional
searchAfter
optional
Efficient next page, pass max sort value from previous page
searchAfterElastic
optional
Efficient next page, pass max ES sort value from previous page
searchAfterMap
optional
Map accounts search after values - stores next page sort values per account. There is no need to store searchBeforeMap as [current page searchBefore] equals to [prev page searchAfter] More, there is no way to generate correct searchBefore from current page as some tenants may not appear at all. The map is relevant in proxy mode and used by tenants, each tenant extracts the searchAfter keys from the map.
searchAfterMapOrder
optional
format: int64
searchBefore
optional
Efficient prev page, pass min sort value from next page
searchBeforeElastic
optional
Efficient prev page, pass min ES sort value from next page
sequenceNumber
optional
format: int64
shouldCommit
optional
size
optional
Size is limited to 1000, if not passed it defaults to 0, and no results will return format: int64
sizeInBytes
optional
format: int64
skipAggregateAccounts
optional
SkipAggregateAccounts flag that indicates whether to skip aggregate accounts results
sort
optional
array[Order] The sort order
sortValues
optional
syncHash
optional
toServerVersion
optional
Version
vcShouldIgnore
optional
vcShouldKeepItemLegacyProdMachine
optional
version
optional
format: int64
widgetType
required
Widget type describes how does the widget should recieve the data, and display it. Supporting types: "bar", "column", "pie", "list", "number", "trend", "text", "duration", "image", "line", and "table".