Struct aws_sdk_sagemaker::types::ScheduleConfig
source · #[non_exhaustive]pub struct ScheduleConfig {
pub schedule_expression: Option<String>,
pub data_analysis_start_time: Option<String>,
pub data_analysis_end_time: Option<String>,
}
Expand description
Configuration details about the monitoring schedule.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.schedule_expression: Option<String>
A cron expression that describes details about the monitoring schedule.
The supported cron expressions are:
-
If you want to set the job to start every hour, use the following:
Hourly: cron(0 * ? * * *)
-
If you want to start the job daily:
cron(0 \[00-23\] ? * * *)
-
If you want to run the job one time, immediately, use the following keyword:
NOW
For example, the following are valid cron expressions:
-
Daily at noon UTC:
cron(0 12 ? * * *)
-
Daily at midnight UTC:
cron(0 0 ? * * *)
To support running every 6, 12 hours, the following are also supported:
cron(0 \[00-23\]/\[01-24\] ? * * *)
For example, the following are valid cron expressions:
-
Every 12 hours, starting at 5pm UTC:
cron(0 17/12 ? * * *)
-
Every two hours starting at midnight:
cron(0 0/2 ? * * *)
-
Even though the cron expression is set to start at 5PM UTC, note that there could be a delay of 0-20 minutes from the actual requested time to run the execution.
-
We recommend that if you would like a daily schedule, you do not provide this parameter. Amazon SageMaker will pick a time for running every day.
You can also specify the keyword NOW
to run the monitoring job immediately, one time, without recurring.
data_analysis_start_time: Option<String>
Sets the start time for a monitoring job window. Express this time as an offset to the times that you schedule your monitoring jobs to run. You schedule monitoring jobs with the ScheduleExpression
parameter. Specify this offset in ISO 8601 duration format. For example, if you want to monitor the five hours of data in your dataset that precede the start of each monitoring job, you would specify: "-PT5H"
.
The start time that you specify must not precede the end time that you specify by more than 24 hours. You specify the end time with the DataAnalysisEndTime
parameter.
If you set ScheduleExpression
to NOW
, this parameter is required.
data_analysis_end_time: Option<String>
Sets the end time for a monitoring job window. Express this time as an offset to the times that you schedule your monitoring jobs to run. You schedule monitoring jobs with the ScheduleExpression
parameter. Specify this offset in ISO 8601 duration format. For example, if you want to end the window one hour before the start of each monitoring job, you would specify: "-PT1H"
.
The end time that you specify must not follow the start time that you specify by more than 24 hours. You specify the start time with the DataAnalysisStartTime
parameter.
If you set ScheduleExpression
to NOW
, this parameter is required.
Implementations§
source§impl ScheduleConfig
impl ScheduleConfig
sourcepub fn schedule_expression(&self) -> Option<&str>
pub fn schedule_expression(&self) -> Option<&str>
A cron expression that describes details about the monitoring schedule.
The supported cron expressions are:
-
If you want to set the job to start every hour, use the following:
Hourly: cron(0 * ? * * *)
-
If you want to start the job daily:
cron(0 \[00-23\] ? * * *)
-
If you want to run the job one time, immediately, use the following keyword:
NOW
For example, the following are valid cron expressions:
-
Daily at noon UTC:
cron(0 12 ? * * *)
-
Daily at midnight UTC:
cron(0 0 ? * * *)
To support running every 6, 12 hours, the following are also supported:
cron(0 \[00-23\]/\[01-24\] ? * * *)
For example, the following are valid cron expressions:
-
Every 12 hours, starting at 5pm UTC:
cron(0 17/12 ? * * *)
-
Every two hours starting at midnight:
cron(0 0/2 ? * * *)
-
Even though the cron expression is set to start at 5PM UTC, note that there could be a delay of 0-20 minutes from the actual requested time to run the execution.
-
We recommend that if you would like a daily schedule, you do not provide this parameter. Amazon SageMaker will pick a time for running every day.
You can also specify the keyword NOW
to run the monitoring job immediately, one time, without recurring.
sourcepub fn data_analysis_start_time(&self) -> Option<&str>
pub fn data_analysis_start_time(&self) -> Option<&str>
Sets the start time for a monitoring job window. Express this time as an offset to the times that you schedule your monitoring jobs to run. You schedule monitoring jobs with the ScheduleExpression
parameter. Specify this offset in ISO 8601 duration format. For example, if you want to monitor the five hours of data in your dataset that precede the start of each monitoring job, you would specify: "-PT5H"
.
The start time that you specify must not precede the end time that you specify by more than 24 hours. You specify the end time with the DataAnalysisEndTime
parameter.
If you set ScheduleExpression
to NOW
, this parameter is required.
sourcepub fn data_analysis_end_time(&self) -> Option<&str>
pub fn data_analysis_end_time(&self) -> Option<&str>
Sets the end time for a monitoring job window. Express this time as an offset to the times that you schedule your monitoring jobs to run. You schedule monitoring jobs with the ScheduleExpression
parameter. Specify this offset in ISO 8601 duration format. For example, if you want to end the window one hour before the start of each monitoring job, you would specify: "-PT1H"
.
The end time that you specify must not follow the start time that you specify by more than 24 hours. You specify the start time with the DataAnalysisStartTime
parameter.
If you set ScheduleExpression
to NOW
, this parameter is required.
source§impl ScheduleConfig
impl ScheduleConfig
sourcepub fn builder() -> ScheduleConfigBuilder
pub fn builder() -> ScheduleConfigBuilder
Creates a new builder-style object to manufacture ScheduleConfig
.
Trait Implementations§
source§impl Clone for ScheduleConfig
impl Clone for ScheduleConfig
source§fn clone(&self) -> ScheduleConfig
fn clone(&self) -> ScheduleConfig
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresource§impl Debug for ScheduleConfig
impl Debug for ScheduleConfig
source§impl PartialEq for ScheduleConfig
impl PartialEq for ScheduleConfig
impl StructuralPartialEq for ScheduleConfig
Auto Trait Implementations§
impl Freeze for ScheduleConfig
impl RefUnwindSafe for ScheduleConfig
impl Send for ScheduleConfig
impl Sync for ScheduleConfig
impl Unpin for ScheduleConfig
impl UnwindSafe for ScheduleConfig
Blanket Implementations§
source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
source§default unsafe fn clone_to_uninit(&self, dst: *mut T)
default unsafe fn clone_to_uninit(&self, dst: *mut T)
clone_to_uninit
)source§impl<T> Instrument for T
impl<T> Instrument for T
source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
source§impl<T> IntoEither for T
impl<T> IntoEither for T
source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moresource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read more