container、jvm探针meta文件中相同实体的不同表中定义的key不一致

根据最初对观测实体的设计约定：相同观测实体类型的key字段需要保持一致，以便用于全局唯一标识一个观测实体。
当前的container、jvm的meta文件定义中存在多个table_name设置了不同的key的情况，这会导致后续使用（生成拓扑图、异常检测）出现无法唯一标识一个观测实体的问题。

```
       table_name: "container_blkio",
        entity_name: "container",
        fields:
        (
            {
                description: "container id",
                type: "key",
                name: "container_id",
            },
            {
                description: "device",
                type: "key",
                name: "device",
            },
            {
                description: "major",
                type: "key",
                name: "major",
            },

table_name: "container_cpu",
        entity_name: "container",
        fields:
        (
            {
                description: "container id",
                type: "key",
                name: "container_id",
            },
            {
                description: "cpu",
                type: "key",
                name: "cpu",
            },
```
```
    {
        table_name: "jvm_mem",
        entity_name: "jvm",
        fields:
        (
            {
                description: "ID of current java process.",
                type: "key",
                name: "tgid",
            },
            {
                description: "Name of JVM Main Class.",
                type: "label",
                name: "name",
            },
            {
                description: "type of JVM memory type: heap or noheap.",
                type: "key",
                name: "area",
            },

table_name: "jvm_thread",
        entity_name: "jvm",
        fields:
        (
            {
                description: "ID of current java process.",
                type: "key",
                name: "tgid",
            },
```

openEuler/gala-gopher

Content Risk Flag

Comments (1)

openEuler/gala-gopher .gitee-modal { width: 500px !important; }

Content Risk Flag