--- title: "Create a new dashboard" method: POST path: "/v2/dashboards" tags: ["Dashboards"] --- # Create a new dashboard `POST /v2/dashboards` Creates a new dashboard from the provided definition. ## Request body - DashboardUpdateRequest - `name` string, required — The dashboard name, which is displayed at the top of the dashboard and in lists. It does not need to be unique. - `definition` Dashboard, required — A JSON object describing a dashboard. A dashboard is an array of tiles. All tiles are of type 'chart', which query data and render a chart displaying that data. Dashboards have 6 columns and as many rows as necessary to display their tiles. - `tiles` Tile[], required — The array of tiles. We currently support up to 102 tiles, which is 17 rows of 6x1 tiles. - `layout` object, required — Information about how the tile is placed on the dashboard. Examples: - a tile occupying the first half of the top row: `{ "position": { "col": 0, "row": 0 }, size: { "cols": 3, "rows": 1 } }` - a tile occupying the second half of the top row: `{ "position": { "col": 3, "row": 0 }, size: { "cols": 3, "rows": 1 } }` - `position` object, required — Position of the tile in the dashboard's grid. Numbering starts at 0, so a tile in the upper left of the dashboard will be at column 0, row 0. - `col` integer, required - `row` integer, required - `size` object, required — Number of columns and rows the tile occupies. A dashboard always has 6 columns, but has as many rows as needed to accommodate the given tiles. - `cols` integer, required - `rows` integer, required - `type` 'chart', required — The type of tile. Chart tiles must have type 'chart'. - `definition` object, required — The tile's definition, which consists of a query to fetch data and a chart to render the data. Note that some charts expect certain types of queries to render properly. The documentation for the individual chart types has more information. - `query` union, required - AdvancedQuery — A query targeting the API usage analytics datasource. - `datasource` 'api_usage', required - `metrics` string[] — List of aggregated metrics to collect across the requested time span. If no metrics are specified, request_count will be computed by default. - `dimensions` string[], nullable — List of attributes or entity types to group by. - `filters` object[] — A list of filters to apply to the query. - … - `granularity` 'tenSecondly' | 'thirtySecondly' | 'minutely' | 'fiveMinutely' | 'tenMinutely' | 'thirtyMinutely' | 'hourly' | 'twoHourly' | 'twelveHourly' | 'daily' | 'weekly' — Force time grouping into buckets of the specified duration. Only has an effect if "time" is in the "dimensions" list. The granularity of the result may be coarser than requested. The finest allowed granularity depends on the query's time range: data farther in the past may have coarser granularity. The exact result granularity will be reported in the response `meta.granularity_ms` field. If granularity is not specified and "time" is in the dimensions list, a default will be chosen based on the time range requested. Different relative times support different granularities: - 15m => tenSecondly, thirtySecondly, minutely - 1h => tenSecondly, thirtySecondly, minutely, fiveMinutely, tenMinutely - 6h => thirtySecondly, minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 12h => minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 24h => fiveMinutely, tenMinutely, thirtyMinutely, hourly - 7d => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - 30d => hourly, twoHourly, twelveHourly, daily, weekly For special time ranges: - current_week, previous_week => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - current_month, previous_month => hourly, twoHourly, twelveHourly, daily, weekly For absolute time ranges, daily will be used. - `time_range` union — The time range to query. - … - LLMQuery — A query targeting the LLM usage analytics datasource. - `datasource` 'llm_usage', required - `metrics` string[] — List of aggregated metrics to collect across the requested time span. - `dimensions` string[], nullable — List of attributes or entity types to group by. - `filters` object[] — A list of filters to apply to the query. - … - `granularity` 'tenSecondly' | 'thirtySecondly' | 'minutely' | 'fiveMinutely' | 'tenMinutely' | 'thirtyMinutely' | 'hourly' | 'twoHourly' | 'twelveHourly' | 'daily' | 'weekly' — Force time grouping into buckets of the specified duration. Only has an effect if "time" is in the "dimensions" list. The granularity of the result may be coarser than requested. The finest allowed granularity depends on the query's time range: data farther in the past may have coarser granularity. The exact result granularity will be reported in the response `meta.granularity_ms` field. If granularity is not specified and "time" is in the dimensions list, a default will be chosen based on the time range requested. Different relative times support different granularities: - 15m => tenSecondly, thirtySecondly, minutely - 1h => tenSecondly, thirtySecondly, minutely, fiveMinutely, tenMinutely - 6h => thirtySecondly, minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 12h => minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 24h => fiveMinutely, tenMinutely, thirtyMinutely, hourly - 7d => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - 30d => hourly, twoHourly, twelveHourly, daily, weekly For special time ranges: - current_week, previous_week => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - current_month, previous_month => hourly, twoHourly, twelveHourly, daily, weekly For absolute time ranges, daily will be used. - `time_range` union — The time range to query. - … - AgenticQuery — A query targeting the agentic usage analytics datasource. - `datasource` 'agentic_usage', required - `metrics` string[] — List of aggregated metrics to collect across the requested time span. - `dimensions` string[], nullable — List of attributes or entity types to group by. - `filters` object[] — A list of filters to apply to the query. - … - `granularity` 'tenSecondly' | 'thirtySecondly' | 'minutely' | 'fiveMinutely' | 'tenMinutely' | 'thirtyMinutely' | 'hourly' | 'twoHourly' | 'twelveHourly' | 'daily' | 'weekly' — Force time grouping into buckets of the specified duration. Only has an effect if "time" is in the "dimensions" list. The granularity of the result may be coarser than requested. The finest allowed granularity depends on the query's time range: data farther in the past may have coarser granularity. The exact result granularity will be reported in the response `meta.granularity_ms` field. If granularity is not specified and "time" is in the dimensions list, a default will be chosen based on the time range requested. Different relative times support different granularities: - 15m => tenSecondly, thirtySecondly, minutely - 1h => tenSecondly, thirtySecondly, minutely, fiveMinutely, tenMinutely - 6h => thirtySecondly, minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 12h => minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 24h => fiveMinutely, tenMinutely, thirtyMinutely, hourly - 7d => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - 30d => hourly, twoHourly, twelveHourly, daily, weekly For special time ranges: - current_week, previous_week => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - current_month, previous_month => hourly, twoHourly, twelveHourly, daily, weekly For absolute time ranges, daily will be used. - `time_range` union — The time range to query. - … - PlatformQuery — A query targeting the platform usage analytics datasource. - `datasource` 'platform_usage', required - `metrics` string[] — List of aggregated metrics to collect across the requested time span. - `dimensions` string[], nullable — List of attributes or entity types to group by. - `filters` PlatformFilter[] — A list of filters to apply to the query. - … - `granularity` 'daily' | 'weekly' | 'monthly' — Force time grouping into buckets of the specified duration. Only has an effect if "time" is in the "dimensions" list. If granularity is not specified and "time" is in the dimensions list, a default will be chosen based on the time range requested. Different relative times support different granularities: - 24h => daily - 7d, current_week, previous_week => daily, weekly - 30d, current_month, previous_month => daily, weekly, monthly - 90d, 180d, 365d, current_quarter, previous_quarter => daily, weekly, monthly For absolute time ranges, daily will be used. Granularity values: - `daily`: Groups data into 24-hour buckets. - `weekly`: Groups data into 7-day buckets. - `monthly`: Groups data into calendar month buckets. - `time_range` union — The time range to query for platform data. - … - `limit` number — Maximum number of group_by buckets to return. Defaults to 50, capped at 1000. Only applies when a group_by dimension is requested. - `chart` union, required — The type of chart to render. - DonutChart — A chart that can display one-dimensional data in a hollow, segmented circle. To use this chart, ensure that the query includes only one dimension (not `time`). - `chart_title` string — The title of the chart, which is displayed in the tile's header. - `type` 'donut', required - TimeseriesChart — A chart that can render timeseries data -- data from a query that has `time` as a dimension -- as lines or bars. This type of chart can support: - One or more metrics: `{ metrics: ["response_latency_p99", "response_latency_p95"], dimensions: ["time"] }` - One metric plus one non-time dimension: `{ metrics: ["request_count"], dimensions: ["time", "gateway_service"] }` Either way, ensure that `time` is in the list of query dimensions. - `chart_title` string — The title of the chart, which is displayed in the tile's header. - `type` 'timeseries_line' | 'timeseries_bar', required - `stacked` boolean — Whether to stack the bars or lines (implicitly adding them together to form a total), or leave them independent from each other. - BarChart — A chart that can display non-timeseries data as bars. This type of chart supports up to 2 dimensions (not `time`). To render a bar chart of timeseries data, use a `timeseries_bar` chart instead. - `chart_title` string — The title of the chart, which is displayed in the tile's header. - `type` 'horizontal_bar' | 'vertical_bar', required - `stacked` boolean — Whether to stack the bars (implicitly adding them together to form a total), or leave them independent from each other. - SingleValueChart — A chart that can render a single number. This chart works with a single metric and no dimensions. - `chart_title` string — The title of the chart, which is displayed in the tile's header. - `type` 'single_value', required - `decimal_points` number, nullable — The number of figures to render after the decimal. Most metrics only support up to 2 decimals, but some may support more. - ChoroplethMapChart — A chart that displays data on a world map. Each region on the map is colored based on the metric value. This chart works only with the `api_usage` datasource and requires a single metric and a single dimension of `country_code`. No additional dimensions are supported. - `chart_title` string — The title of the chart, which is displayed in the tile's header. - `type` 'choropleth_map', required - `preset_filters` AllFilterItems[] — An optional array of filters that are applied globally to all relevant tiles in the dashboard. Whether or not a preset filter applies to a tile depends on the filter's dimension. Some dimensions, like `control_plane`, are common to all datasources; other dimensions may only apply to one datasource. - `field` 'a2a_context_id' | 'a2a_error' | 'a2a_method' | 'a2a_task_id' | 'ai_plugin' | 'ai_provider' | 'ai_request_model' | 'ai_response_model' | 'api' | 'api_package' | 'api_product' | 'api_product_version' | 'application' | 'consumer' | 'control_plane' | 'control_plane_group' | 'country_code' | 'data_plane_node' | 'data_plane_node_version' | 'gateway_service' | 'llm_cache_status' | 'llm_embeddings_model' | 'llm_embeddings_provider' | 'mcp_error' | 'mcp_method' | 'mcp_session_id' | 'mcp_tool_name' | 'portal' | 'realm' | 'response_source' | 'route' | 'status_code' | 'status_code_grouped' | 'upstream_status_code' | 'upstream_status_code_grouped', required - `operator` 'in' | 'not_in' | 'empty' | 'not_empty', required - `value` unknown - `labels` Labels — Labels store metadata of an entity that can be used for filtering an entity list or for searching across entity types. Keys must be of length 1-63 characters, and cannot start with "kong", "konnect", "mesh", "kic", or "_". ## Response `201` The created dashboard, including generated fields. - DashboardResponse - `name` string, required — The dashboard name, which is displayed at the top of the dashboard and in lists. It does not need to be unique. - `definition` Dashboard, required — A JSON object describing a dashboard. A dashboard is an array of tiles. All tiles are of type 'chart', which query data and render a chart displaying that data. Dashboards have 6 columns and as many rows as necessary to display their tiles. - `tiles` Tile[], required — The array of tiles. We currently support up to 102 tiles, which is 17 rows of 6x1 tiles. - `layout` object, required — Information about how the tile is placed on the dashboard. Examples: - a tile occupying the first half of the top row: `{ "position": { "col": 0, "row": 0 }, size: { "cols": 3, "rows": 1 } }` - a tile occupying the second half of the top row: `{ "position": { "col": 3, "row": 0 }, size: { "cols": 3, "rows": 1 } }` - `position` object, required — Position of the tile in the dashboard's grid. Numbering starts at 0, so a tile in the upper left of the dashboard will be at column 0, row 0. - `col` integer, required - `row` integer, required - `size` object, required — Number of columns and rows the tile occupies. A dashboard always has 6 columns, but has as many rows as needed to accommodate the given tiles. - `cols` integer, required - `rows` integer, required - `type` 'chart', required — The type of tile. Chart tiles must have type 'chart'. - `definition` object, required — The tile's definition, which consists of a query to fetch data and a chart to render the data. Note that some charts expect certain types of queries to render properly. The documentation for the individual chart types has more information. - `query` union, required - AdvancedQuery — A query targeting the API usage analytics datasource. - `datasource` 'api_usage', required - `metrics` string[] — List of aggregated metrics to collect across the requested time span. If no metrics are specified, request_count will be computed by default. - `dimensions` string[], nullable — List of attributes or entity types to group by. - `filters` object[] — A list of filters to apply to the query. - … - `granularity` 'tenSecondly' | 'thirtySecondly' | 'minutely' | 'fiveMinutely' | 'tenMinutely' | 'thirtyMinutely' | 'hourly' | 'twoHourly' | 'twelveHourly' | 'daily' | 'weekly' — Force time grouping into buckets of the specified duration. Only has an effect if "time" is in the "dimensions" list. The granularity of the result may be coarser than requested. The finest allowed granularity depends on the query's time range: data farther in the past may have coarser granularity. The exact result granularity will be reported in the response `meta.granularity_ms` field. If granularity is not specified and "time" is in the dimensions list, a default will be chosen based on the time range requested. Different relative times support different granularities: - 15m => tenSecondly, thirtySecondly, minutely - 1h => tenSecondly, thirtySecondly, minutely, fiveMinutely, tenMinutely - 6h => thirtySecondly, minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 12h => minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 24h => fiveMinutely, tenMinutely, thirtyMinutely, hourly - 7d => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - 30d => hourly, twoHourly, twelveHourly, daily, weekly For special time ranges: - current_week, previous_week => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - current_month, previous_month => hourly, twoHourly, twelveHourly, daily, weekly For absolute time ranges, daily will be used. - `time_range` union — The time range to query. - … - LLMQuery — A query targeting the LLM usage analytics datasource. - `datasource` 'llm_usage', required - `metrics` string[] — List of aggregated metrics to collect across the requested time span. - `dimensions` string[], nullable — List of attributes or entity types to group by. - `filters` object[] — A list of filters to apply to the query. - … - `granularity` 'tenSecondly' | 'thirtySecondly' | 'minutely' | 'fiveMinutely' | 'tenMinutely' | 'thirtyMinutely' | 'hourly' | 'twoHourly' | 'twelveHourly' | 'daily' | 'weekly' — Force time grouping into buckets of the specified duration. Only has an effect if "time" is in the "dimensions" list. The granularity of the result may be coarser than requested. The finest allowed granularity depends on the query's time range: data farther in the past may have coarser granularity. The exact result granularity will be reported in the response `meta.granularity_ms` field. If granularity is not specified and "time" is in the dimensions list, a default will be chosen based on the time range requested. Different relative times support different granularities: - 15m => tenSecondly, thirtySecondly, minutely - 1h => tenSecondly, thirtySecondly, minutely, fiveMinutely, tenMinutely - 6h => thirtySecondly, minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 12h => minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 24h => fiveMinutely, tenMinutely, thirtyMinutely, hourly - 7d => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - 30d => hourly, twoHourly, twelveHourly, daily, weekly For special time ranges: - current_week, previous_week => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - current_month, previous_month => hourly, twoHourly, twelveHourly, daily, weekly For absolute time ranges, daily will be used. - `time_range` union — The time range to query. - … - AgenticQuery — A query targeting the agentic usage analytics datasource. - `datasource` 'agentic_usage', required - `metrics` string[] — List of aggregated metrics to collect across the requested time span. - `dimensions` string[], nullable — List of attributes or entity types to group by. - `filters` object[] — A list of filters to apply to the query. - … - `granularity` 'tenSecondly' | 'thirtySecondly' | 'minutely' | 'fiveMinutely' | 'tenMinutely' | 'thirtyMinutely' | 'hourly' | 'twoHourly' | 'twelveHourly' | 'daily' | 'weekly' — Force time grouping into buckets of the specified duration. Only has an effect if "time" is in the "dimensions" list. The granularity of the result may be coarser than requested. The finest allowed granularity depends on the query's time range: data farther in the past may have coarser granularity. The exact result granularity will be reported in the response `meta.granularity_ms` field. If granularity is not specified and "time" is in the dimensions list, a default will be chosen based on the time range requested. Different relative times support different granularities: - 15m => tenSecondly, thirtySecondly, minutely - 1h => tenSecondly, thirtySecondly, minutely, fiveMinutely, tenMinutely - 6h => thirtySecondly, minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 12h => minutely, fiveMinutely, tenMinutely, thirtyMinutely, hourly - 24h => fiveMinutely, tenMinutely, thirtyMinutely, hourly - 7d => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - 30d => hourly, twoHourly, twelveHourly, daily, weekly For special time ranges: - current_week, previous_week => thirtyMinutely, hourly, twoHourly, twelveHourly, daily - current_month, previous_month => hourly, twoHourly, twelveHourly, daily, weekly For absolute time ranges, daily will be used. - `time_range` union — The time range to query. - … - PlatformQuery — A query targeting the platform usage analytics datasource. - `datasource` 'platform_usage', required - `metrics` string[] — List of aggregated metrics to collect across the requested time span. - `dimensions` string[], nullable — List of attributes or entity types to group by. - `filters` PlatformFilter[] — A list of filters to apply to the query. - … - `granularity` 'daily' | 'weekly' | 'monthly' — Force time grouping into buckets of the specified duration. Only has an effect if "time" is in the "dimensions" list. If granularity is not specified and "time" is in the dimensions list, a default will be chosen based on the time range requested. Different relative times support different granularities: - 24h => daily - 7d, current_week, previous_week => daily, weekly - 30d, current_month, previous_month => daily, weekly, monthly - 90d, 180d, 365d, current_quarter, previous_quarter => daily, weekly, monthly For absolute time ranges, daily will be used. Granularity values: - `daily`: Groups data into 24-hour buckets. - `weekly`: Groups data into 7-day buckets. - `monthly`: Groups data into calendar month buckets. - `time_range` union — The time range to query for platform data. - … - `limit` number — Maximum number of group_by buckets to return. Defaults to 50, capped at 1000. Only applies when a group_by dimension is requested. - `chart` union, required — The type of chart to render. - DonutChart — A chart that can display one-dimensional data in a hollow, segmented circle. To use this chart, ensure that the query includes only one dimension (not `time`). - `chart_title` string — The title of the chart, which is displayed in the tile's header. - `type` 'donut', required - TimeseriesChart — A chart that can render timeseries data -- data from a query that has `time` as a dimension -- as lines or bars. This type of chart can support: - One or more metrics: `{ metrics: ["response_latency_p99", "response_latency_p95"], dimensions: ["time"] }` - One metric plus one non-time dimension: `{ metrics: ["request_count"], dimensions: ["time", "gateway_service"] }` Either way, ensure that `time` is in the list of query dimensions. - `chart_title` string — The title of the chart, which is displayed in the tile's header. - `type` 'timeseries_line' | 'timeseries_bar', required - `stacked` boolean — Whether to stack the bars or lines (implicitly adding them together to form a total), or leave them independent from each other. - BarChart — A chart that can display non-timeseries data as bars. This type of chart supports up to 2 dimensions (not `time`). To render a bar chart of timeseries data, use a `timeseries_bar` chart instead. - `chart_title` string — The title of the chart, which is displayed in the tile's header. - `type` 'horizontal_bar' | 'vertical_bar', required - `stacked` boolean — Whether to stack the bars (implicitly adding them together to form a total), or leave them independent from each other. - SingleValueChart — A chart that can render a single number. This chart works with a single metric and no dimensions. - `chart_title` string — The title of the chart, which is displayed in the tile's header. - `type` 'single_value', required - `decimal_points` number, nullable — The number of figures to render after the decimal. Most metrics only support up to 2 decimals, but some may support more. - ChoroplethMapChart — A chart that displays data on a world map. Each region on the map is colored based on the metric value. This chart works only with the `api_usage` datasource and requires a single metric and a single dimension of `country_code`. No additional dimensions are supported. - `chart_title` string — The title of the chart, which is displayed in the tile's header. - `type` 'choropleth_map', required - `preset_filters` AllFilterItems[] — An optional array of filters that are applied globally to all relevant tiles in the dashboard. Whether or not a preset filter applies to a tile depends on the filter's dimension. Some dimensions, like `control_plane`, are common to all datasources; other dimensions may only apply to one datasource. - `field` 'a2a_context_id' | 'a2a_error' | 'a2a_method' | 'a2a_task_id' | 'ai_plugin' | 'ai_provider' | 'ai_request_model' | 'ai_response_model' | 'api' | 'api_package' | 'api_product' | 'api_product_version' | 'application' | 'consumer' | 'control_plane' | 'control_plane_group' | 'country_code' | 'data_plane_node' | 'data_plane_node_version' | 'gateway_service' | 'llm_cache_status' | 'llm_embeddings_model' | 'llm_embeddings_provider' | 'mcp_error' | 'mcp_method' | 'mcp_session_id' | 'mcp_tool_name' | 'portal' | 'realm' | 'response_source' | 'route' | 'status_code' | 'status_code_grouped' | 'upstream_status_code' | 'upstream_status_code_grouped', required - `operator` 'in' | 'not_in' | 'empty' | 'not_empty', required - `value` unknown - `labels` Labels — Labels store metadata of an entity that can be used for filtering an entity list or for searching across entity types. Keys must be of length 1-63 characters, and cannot start with "kong", "konnect", "mesh", "kic", or "_". - `id` string, uuid — Contains a unique identifier used for this resource. - `created_by` string, uuid — Contains a unique identifier used for this resource. - `created_at` string, date-time — An ISO-8601 timestamp representation of entity creation date. - `updated_at` string, date-time — An ISO-8601 timestamp representation of entity update date. ## Other responses - `400` — Bad request; returned when the request payload was not valid. - `401` — Unauthorized - `403` — Forbidden ## Changes - **2026-06-11** `be4c4e09af62` — 7 breaking, 18 warning, 29 info - added the new required request property `definition/tiles/items/oneOf[#/components/schemas/ChartTile]/definition/query/oneOf[#/components/schemas/AgenticQuery]/filters/items/field` - added the new required request property `definition/tiles/items/oneOf[#/components/schemas/ChartTile]/definition/query/oneOf[#/components/schemas/AgenticQuery]/filters/items/operator` - removed the enum value `mcp_response_body_size_sum` of the request property `definition/tiles/items/oneOf[#/components/schemas/ChartTile]/definition/query/oneOf[#/components/schemas/AgenticQuery]/metrics/items/` - removed `#/components/schemas/MetricsA2aContextIdFilterByField, #/components/schemas/MetricsA2aErrorFilterByField, #/components/schemas/MetricsA2aMethodFilterByField, #/components/schemas/MetricsA2aTaskIdFilterByField, #/components/schemas/MetricsApiFilterByField, #/components/schemas/MetricsApiPackageFilterByField, #/components/schemas/MetricsApiProductFilterByField, #/components/schemas/MetricsApiProductVersionFilterByField, #/components/schemas/MetricsApplicationFilterByField, #/components/schemas/MetricsConsumerFilterByField, #/components/schemas/MetricsControlPlaneFilterByField, #/components/schemas/MetricsControlPlaneGroupFilterByField, #/components/schemas/MetricsCountryCodeFilterByField, #/components/schemas/MetricsDataPlaneNodeFilterByField, #/components/schemas/MetricsDataPlaneNodeVersionFilterByField, #/components/schemas/MetricsGatewayServiceFilterByField, #/components/schemas/MetricsMcpErrorFilterByField, #/components/schemas/MetricsMcpMethodFilterByField, #/components/schemas/MetricsMcpSessionIdFilterByField, #/components/schemas/MetricsMcpToolNameFilterByField, #/components/schemas/MetricsPortalFilterByField, #/components/schemas/MetricsRealmFilterByField, #/components/schemas/MetricsResponseSourceFilterByField, #/components/schemas/MetricsRouteFilterByField, #/components/schemas/MetricsStatusCodeFilterByField, #/components/schemas/MetricsStatusCodeGroupedFilterByField, #/components/schemas/MetricsUpstreamStatusCodeFilterByField, #/components/schemas/MetricsUpstreamStatusCodeGroupedFilterByField` from the `definition/tiles/items/oneOf[#/components/schemas/ChartTile]/definition/query/oneOf[#/components/schemas/AgenticQuery]/filters/items/` request property `oneOf` list - …50 more - …earlier changes not shown [Full history](https://skmtc.dev/kong/apis/konnect-api-beta/changes/v2/dashboards/post.md) --- [API](https://skmtc.dev/kong/apis/konnect-api-beta.md) · [All operations](https://skmtc.dev/kong/apis/konnect-api-beta/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/kong/konnect-api-beta/revisions/73b05fbfd2ef/schema)