- Le plus récent
- Le plus de votes
- La plupart des commentaires
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:
- https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_MonitoringDatasetFormat.html
- https://docs.aws.amazon.com/sagemaker/latest/dg/model-monitor-model-quality-schedule.html
- https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-algo-common-data-formats.html
- https://support.console.aws.amazon.com/support/home?region=us-east-1#/case/create
Contenus pertinents
- demandé il y a 7 mois
- demandé il y a un an
- demandé il y a 5 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an