Is it possible that your raw event is noncompliant? This is what your illustrated event format suggests. If that format is exact, Splunk cannot extract anything other than "name" field. There are two elements that violates JSON syntax. The mock event contains two bare strings that are not key-value pairs, as pointed out as "MISSING-KEY1" and "MISSING-KEY2" in the following pretty-print of a "corrected" conformant JSON object: {
"name": "",
"MISSING-KEY1": "",
"pid": 8,
"level": 50,
"error": {
"message": "Request failed with status code 500",
"name": "AxiosError",
"stack": "AxiosError: Request failed with status code 500\n )",
"config": {
"transitional": {
"silentJSONParsing": true,
"forcedJSONParsing": true,
"clarifyTimeoutError": false
},
"adapter": [
"xhr",
"http"
],
"transformRequest": [
null
],
"transformResponse": [
null
],
"timeout": 0,
"xsrfCookieName": "X",
"xsrfHeaderName": "X-",
"maxContentLength": -1,
"maxBodyLength": -1,
"env": {},
"headers": {
"Accept": "application/json, text/plain, */*",
"Content-Type": "application/json",
"Authorization": "",
"User-Agent": "",
"Accept-Encoding": "gzip, compress, deflate, br"
},
"method": "get",
"MISSING-KEY2": ""
},
"code": "ERR_BAD_RESPONSE",
"status": 500
},
"eventAttributes": {
"Identifier": 2025732,
"VersionNumber": "A.43"
},
"msg": "msg:data:error",
"time": ":48:38.213Z",
"v": 0
} If your actual events are non-compliant, Splunk will not have a value for error.status. By the way, the command "eval status=case(like(error.status, "4%"), "4xx", like(error.status, "5%"), "5xx")" is wasted as your stats command does not use the field status.
... View more