Skip to content

Conversation

@sushanthkumar2004
Copy link

@sushanthkumar2004 sushanthkumar2004 commented Jul 15, 2024

Issue #, if available:

Description of changes: Add a new automatic dashboard generation parameter to the DefaultModelMonitor and ModelQualityMonitor. Automatically generate dashboards for data quality model monitoring jobs and model quality monitoring jobs.

Testing done: Unit tests verify that the dashboard is generated correctly and all error-handling in dashboard parameters are handled correctly via a Mock Boto3 client. The integration tests verify that dashboard publishing on Cloudwatch is successful with the real Boto3 client.

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

  • I have read the CONTRIBUTING doc
  • I certify that the changes I am introducing will be backward compatible, and I have discussed concerns about this, if any, with the Python SDK team
  • I used the commit message format described in CONTRIBUTING
  • I have passed the region in to all S3 and STS clients that I've initialized as part of this change.
  • I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

  • I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • I have added unit and/or integration tests as appropriate to ensure backward compatibility of the changes
  • I have checked that my tests are not configured for a specific region or account (if appropriate)
  • I have used unique_name_from_base to create resource names in integ tests (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

import json


class Variable:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to use a better name instead of Variable?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll call it DashboardVariable, DashboardWidget, DashboardWidgetProperty to keep consistency.

logger.error(message)
raise ValueError(message)

try:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need a try except expression here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need it since if the dashboard exists we don't want to overwrite it.

nileshvd
nileshvd previously approved these changes Aug 1, 2024
@sage-maker
Copy link
Collaborator

Approved workflow

sage-maker
sage-maker previously approved these changes Aug 7, 2024
Sushanth Sathish Kumar added 20 commits August 22, 2024 23:31
…eate_monitoring_schedule with error handling, TODO: modify update_monitoring_schedule accordingly and add unit tests
…nstead of endpoint name, the user provides an EndpointInput object
…to update_monitoring_schedule methods for Data Quality and Model Quality
… so that only features from the specific monitoring schedule and endpoint are loaded
… modify test_dashboard_methods to take into account the new filters in the dashboard variables
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants