Characteristics of JSON output from OMEGAMON Data Connect
If you need to work directly with JSON output from OMEGAMON® Data Connect, then it's useful to understand the characteristics of this data, such as its structure, property names, and property values.
The characteristics described here refer to data with OMEGAMON monitoring agents as the data source. For characteristics of data from other data sources, see the separate documentation for that other software.
Flat: no nested objects
Each line of the JSON Lines output by OMEGAMON Data Connect is a
JSON object consisting of a collection of name/value pairs (properties
).
The structure is flat: there are no nested objects.
No null
values
If there is no underlying data available for an OMEGAMON attribute, then rather than representing the attribute in JSON output as a key with
the JavaScript value null
, OMEGAMON Data Connect
omits the key.
OMEGAMON Data Connect performs this processing for each line of JSON. Depending on the availability of the underlying data, a key that is present in some lines of JSON output might not be present in other lines for the same attribute table.
No whitespace between tokens
The JSON standard (ECMA-404) allows insignificant whitespace before or after any token.
The JSON output by OMEGAMON Data Connect is deliberately compact and omits such whitespace.
Property names
JSON property names are based on OMEGAMON attribute names. For details, see Attribute names versus field names.
Timestamps
Timestamps are in ISO 8601 date and time of day representation extended format with a trailing zone designator:
yyyy-mm-ddThh:mm:ss.SSSSSSSSS[+|-]hh:mm
Example:
2021-06-23T00:18:28.999999001-04:00
Scientific notation
Very large or very small numbers might be represented in scientific notation. For example,
1.077952576E8
.
Introduced fields
OMEGAMON Data Connect introduces fields that do not occur in the original OMEGAMON attribute groups.
Example
Here is a single line of JSON output from OMEGAMON Data Connect, shown here with indenting and line breaks for readability:
{
"managed_system":"ZOSAPLEX:ZOS1:MVSSYS",
"job_name":"M5M5DS",
"cpu_percent":1.7,
"tcb_percent":1.7,
"srb_percent":0.0,
"step_name":"M5M5DS",
"proc_step":"TEMSREMT",
"svcclass":"STCLO",
"svcclasp":1,
"asid":417,
"jesjobid":"S0852831",
"job_cpu_time":1671.63,
"job_tcb_time":1655.76,
"job_srb_time":15.34,
"sysplex_name":"ZOSAPLEX",
"smf_id":"ZOS1",
"table_name":"ascpuutil",
"write_time":"2021-10-13T08:00:13.999999001-04:00",
"product_code":"km5",
"interval_seconds":60
}
This example includes the following fields introduced by OMEGAMON Data Connect:
sysplex_name
smf_id
table_name
write_time
product_code
interval_seconds