Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'base_job_name' parameter is not used to name the Processing Jobs that are created by the Model Monitoring Schedule #4783

Open
lazara2 opened this issue Jul 11, 2024 · 0 comments
Labels

Comments

@lazara2
Copy link

lazara2 commented Jul 11, 2024

Describe the bug
The base_job_name parameter specified in the DefaultModelMonitor is not being used to name the processing jobs created by the monitoring schedule.

To reproduce
Steps to reproduce the behavior:

  1. Initialize a DefaultModelMonitor with base_job_name parameter.
  2. Create a monitoring schedule.
  3. Observe that the processing jobs do not use the specified base_job_name.

Expected behavior
The processing jobs created by the monitoring schedule should use the base_job_name specified in the DefaultModelMonitor.

Screenshots or logs
sgmk_issue_mm_base_job_name1

This is the Processing Job that is created by the Model Monitoring Schedule, and it's clear that it's not using the 'base_job_name'.
Capture

System information
A description of your system. Please provide:

  • SageMaker Python SDK version: 2.221.1
  • Framework name (eg. PyTorch) or algorithm (eg. KMeans): Scikit-learn
  • Framework version: 0.23-1
  • Python version: 3.10.14
  • CPU or GPU: CPU
  • Custom Docker image (Y/N): N

Additional context
Add any other context about the problem here.

@lazara2 lazara2 added the bug label Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant