mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
Reverts https://github.com/elastic/kibana/pull/168553 Seeing these errors when updating existing alerts as data mappings ``` [2023-10-13T11:06:44.254-04:00][ERROR][plugins.alerting] ResponseError: illegal_argument_exception Root causes: illegal_argument_exception: can't merge a non-nested mapping [faas.trigger] with a nested mapping at KibanaTransport.request (/Users/ying/Code/kibana_prs/node_modules/@elastic/transport/src/Transport.ts:535:17) at processTicksAndRejections (node:internal/process/task_queues:95:5) ``` Needs further investigation as ECS mappings should be backwards compatible
74 lines
1.9 KiB
TypeScript
74 lines
1.9 KiB
TypeScript
/*
|
|
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
|
|
* or more contributor license agreements. Licensed under the Elastic License
|
|
* 2.0 and the Server Side Public License, v 1; you may not use this file except
|
|
* in compliance with, at your election, the Elastic License 2.0 or the Server
|
|
* Side Public License, v 1.
|
|
*/
|
|
|
|
/**
|
|
* Fields that describe the resources which container orchestrators manage or act upon.
|
|
*/
|
|
export interface EcsOrchestrator {
|
|
/**
|
|
* API version being used to carry out the action
|
|
*/
|
|
api_version?: string;
|
|
cluster?: {
|
|
/**
|
|
* Unique ID of the cluster.
|
|
*/
|
|
id?: string;
|
|
/**
|
|
* Name of the cluster.
|
|
*/
|
|
name?: string;
|
|
/**
|
|
* URL of the API used to manage the cluster.
|
|
*/
|
|
url?: string;
|
|
/**
|
|
* The version of the cluster.
|
|
*/
|
|
version?: string;
|
|
};
|
|
|
|
/**
|
|
* Namespace in which the action is taking place.
|
|
*/
|
|
namespace?: string;
|
|
/**
|
|
* Organization affected by the event (for multi-tenant orchestrator setups).
|
|
*/
|
|
organization?: string;
|
|
resource?: {
|
|
/**
|
|
* Unique ID of the resource being acted upon.
|
|
*/
|
|
id?: string;
|
|
/**
|
|
* IP address assigned to the resource associated with the event being observed. In the case of a Kubernetes Pod, this array would contain only one element: the IP of the Pod (as opposed to the Node on which the Pod is running).
|
|
*/
|
|
ip?: string[];
|
|
/**
|
|
* Name of the resource being acted upon.
|
|
*/
|
|
name?: string;
|
|
parent?: {
|
|
/**
|
|
* Type or kind of the parent resource associated with the event being observed. In Kubernetes, this will be the name of a built-in workload resource (e.g., Deployment, StatefulSet, DaemonSet).
|
|
*/
|
|
type?: string;
|
|
};
|
|
|
|
/**
|
|
* Type of resource being acted upon.
|
|
*/
|
|
type?: string;
|
|
};
|
|
|
|
/**
|
|
* Orchestrator cluster type (e.g. kubernetes, nomad or cloudfoundry).
|
|
*/
|
|
type?: string;
|
|
}
|