Sagemaker Model Monitor - endPointInput:contentType is of type application/octet-stream

0

Calling the sagemaker model endpoint with contentType application/octet-stream which is also being captured in Data Capture Logs. What would be the ideal way to transform the data such that model monitor can work properly? I understand that model monitor works with csv or json content types.

Able to use a preprocessing script to transform the input and output to csv/json from protobuf format. Can I change the contentType field also as part of pre-processing?

1 Answer
0

Hello,

I understand that you want to know if you can change the contentTpye filed as part of processing in such a way that this can also be compatible with SageMaker Model monitoring job which only supports SCV, JSON and Parquet as data formats [1].

Are you monitoring a real-time endpoint or a batch transform job [2]? Which preprocessing script did you use to transform the input and output to csv/json from protobuf format?

Please see the list of common data formats for built-in algorithms in SageMaker [3]. I recommend that you open a Support case with AWS Technical Support [4]. The Technical Support team will be able to help you with this and provide better recommendations in this case.

I trust this information finds you well. Should you have any further questions please feel free to reach out.

References:

  1. https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_MonitoringDatasetFormat.html
  2. https://docs.aws.amazon.com/sagemaker/latest/dg/model-monitor-model-quality-schedule.html
  3. https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-algo-common-data-formats.html
  4. https://support.console.aws.amazon.com/support/home?region=us-east-1#/case/create
AWS
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions