topic Error in model "JVM" : Cannot add field 'cpu_time_supported' because it already exists in object 'Threading'. in Splunk Search

Error in model "JVM" : Cannot add field 'cpu_time_supported' because it already exists in object 'Threading'.

jeandez — Mon, 28 Sep 2020 17:30:02 GMT

hi !!! i got this error when trying to create a data model:"Error in model "JVM" : Cannot add field 'cpu_time_supported' because it already exists in object 'Threading'".
I don't understand it . could someone explain it to me and show me a way to fix it ?
Thank you ..

Re: Error in model "JVM" : Cannot add field 'cpu_time_supported' because it already exists in object 'Threading'.

bohrasaurabh — Mon, 01 Jun 2015 17:45:15 GMT

We are also noticing the same on the SH's which also have ES installed. has any one fout out the solution to fix this? We are running 6.1.5 on SHP.

Re: Error in model "JVM" : Cannot add field 'cpu_time_supported' because it already exists in object 'Threading'.

jcrabb_splunk — Wed, 10 Jun 2015 13:54:18 GMT

This was a bug in ES 3.0.0 which was addressed in ES 3.0.1.

Re: Error in model "JVM" : Cannot add field 'cpu_time_supported' because it already exists in object 'Threading'.

fDK — Tue, 07 Jul 2015 13:52:31 GMT

Hi,
I noticed that in the data model editor in general you cannot overwrite fields that exist in a) the events or b) the parent object of the data model object you want to define that field.

I would consider this as a bug (since you can do overwrite existing fields in a regular search) and it is not limited to the Enterprise Security app.

In general overwriting fields is a nice (the only?) way to apply multiple transfomations (eval, lookups, rex, etc.) on a field to 'enhance' its value.

We are using Splunk 6.1.2. Is this fixed in a newer version?