...

Contents of this article:

• Getting Started(Testing / Monitoring): most customers only use Schemas to facilitate testing and monitoring. To get started quickly with testing and monitoring, go to the “Getting Started” section.

• Model Execution(ModelOp Runtime): for those using the ModelOp runtime for model execution (aka model scoring), please see “Model Execution” section

• Advanced Features / Description(Detailed Settings): for more in-depth background on the ModelOp schema, see the “Advanced Features” section

Getting Started

Running the out-of-the-box ModelOp tests and monitors requires that the business model has an extended input schema. When a testing/monitoring job is created, the monitor’s init function accesses the extended input schema, and uses it to determine certain monitoring parameters, such as the names of the fields corresponding to specific roles (score, label, etc.)

...

The normal Avro schema checking will then fail the check as the numerical probability has been replaced by a string.

Extended Schema & Monitoring

To enable monitoring out-of-the-box (OOTB), ModelOp Center introduced in V2.4 the concept of an extended schema. We will go over the details below, but in short, an extended schema is a rich Avro schema, so that more information about the data can be learned. Traditionally, Avro schemas specify field names and types. Extended schemas add more key:value pairs to each field, so that OOTB monitors can make reasonable assumptions, such as inferring the role of a field ("predictor", "identifier", etc.)

An Example

Extended schemas are best understood through an example. Let’s consider the same records from the previous example:

...