jtaleric
commented
4 years ago @bengland2 this seems to be fixed now.
"uuid": "cfa63813-3acb-55d8-9c6b-a6e7b1c37952",
"timestamp": 1600806931,
"node_name": "${my_node_name}",
"pod_name": "${my_pod_name}",
"module": "cpuinfo",
"host": "localhost",
"source_type": "stockpile",
"scribe_uuid": "6dc7f082-ac15-41c6-8178-15ffa3be32a9",
"value": {
"Architecture": "x86_64",
"CPU op-mode(s)": "32-bit, 64-bit",
"Byte Order": "Little Endian",
"CPU(s)": "8",
"On-line CPU(s) list": "0-7",
"Thread(s) per core": "2",
"Core(s) per socket": "4",
"Socket(s)": "1",
"NUMA node(s)": "1",
"Vendor ID": "GenuineIntel",
"CPU family": "6",
"Model": "85",
"Model name": "Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz",
"Stepping": "4",
"CPU MHz": "3095.165",
"BogoMIPS": "5000.00",
"Hypervisor vendor": "KVM",
"Virtualization type": "full",
"L1d cache": "32K",
"L1i cache": "32K",
"L2 cache": "1024K",
"L3 cache": "33792K",
"NUMA node0 CPU(s)": "0-7",
"Flags": [
"fpu",
"vme",
"de",
"pse",
"tsc",
"msr",
"pae",
"mce",
"cx8",
"apic",
"sep",
"mtrr",
"pge",
"mca",
"cmov",
"pat",
"pse36",
"clflush",
"mmx",
"fxsr",
"sse",
"sse2",
"ss",
"ht",
"syscall",
"nx",
"pdpe1gb",
"rdtscp",
"lm",
"constant_tsc",
"rep_good",
"nopl",
"xtopology",
"nonstop_tsc",
"cpuid",
"aperfmperf",
"tsc_known_freq",
"pni",
"pclmulqdq",
"ssse3",
"fma",
"cx16",
"pcid",
"sse4_1",
"sse4_2",
"x2apic",
"movbe",
"popcnt",
"tsc_deadline_timer",
"aes",
"xsave",
"avx",
"f16c",
"rdrand",
"hypervisor",
"lahf_lm",
"abm",
"3dnowprefetch",
"invpcid_single",
"pti",
"fsgsbase",
"tsc_adjust",
"bmi1",
"hle",
"avx2",
"smep",
"bmi2",
"erms",
"invpcid",
"rtm",
"mpx",
"avx512f",
"avx512dq",
"rdseed",
"adx",
"smap",
"clflushopt",
"clwb",
"avx512cd",
"avx512bw",
"avx512vl",
"xsaveopt",
"xsavec",
"xgetbv1",
"xsaves",
"ida",
"arat",
"pku",
"ospke"
]
}
}```
I was trying to access cpuinfo metadata when I noticed that all of it is rolled into a single elasticsearch field, value.Architecture:_x86_64 . This makes it impossible for kibana to search it or display a subset of it. Is this a problem in your opinion and if so, what could be done about it? Obviously it's a maintenance headache to split out subfields 1 by 1, is there some more elegant way to insert this data into ES in a searchable form?