Struct aws_sdk_lightsail::client::fluent_builders::GetContainerLog

pub struct GetContainerLog<C = DynConnector, M = AwsMiddleware, R = Standard> { /* fields omitted */ }

Fluent builder constructing a request to GetContainerLog.

Returns the log events of a container of your Amazon Lightsail container service.

If your container service has more than one node (i.e., a scale greater than 1), then the log events that are returned for the specified container are merged from all nodes on your container service.

Container logs are retained for a certain amount of time. For more information, see Amazon Lightsail endpoints and quotas in the AWS General Reference.

Implementations

impl<C, M, R> GetContainerLog<C, M, R> where
    C: SmithyConnector,
    M: SmithyMiddleware<C>,
    R: NewRequestPolicy, 

pub async fn send(
    self
) -> Result<GetContainerLogOutput, SdkError<GetContainerLogError>> where
    R::Policy: SmithyRetryPolicy<GetContainerLogInputOperationOutputAlias, GetContainerLogOutput, GetContainerLogError, GetContainerLogInputOperationRetryAlias>, 

Sends the request and returns the response.

If an error occurs, an SdkError will be returned with additional details that can be matched against.

By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.

pub fn service_name(self, inp: impl Into<String>) -> Self

The name of the container service for which to get a container log.

pub fn set_service_name(self, input: Option<String>) -> Self

The name of the container service for which to get a container log.

pub fn container_name(self, inp: impl Into<String>) -> Self

The name of the container that is either running or previously ran on the container service for which to return a log.

pub fn set_container_name(self, input: Option<String>) -> Self

The name of the container that is either running or previously ran on the container service for which to return a log.

pub fn start_time(self, inp: DateTime) -> Self

The start of the time interval for which to get log data.

Constraints:

• Specified in Coordinated Universal Time (UTC).

• Specified in the Unix time format.

  For example, if you wish to use a start time of October 1, 2018, at 8 PM UTC, specify 1538424000 as the start time.

You can convert a human-friendly time to Unix time format using a converter like Epoch converter.

pub fn set_start_time(self, input: Option<DateTime>) -> Self

The start of the time interval for which to get log data.

Constraints:

• Specified in Coordinated Universal Time (UTC).

• Specified in the Unix time format.

  For example, if you wish to use a start time of October 1, 2018, at 8 PM UTC, specify 1538424000 as the start time.

You can convert a human-friendly time to Unix time format using a converter like Epoch converter.

pub fn end_time(self, inp: DateTime) -> Self

The end of the time interval for which to get log data.

Constraints:

• Specified in Coordinated Universal Time (UTC).

• Specified in the Unix time format.

  For example, if you wish to use an end time of October 1, 2018, at 9 PM UTC, specify 1538427600 as the end time.

You can convert a human-friendly time to Unix time format using a converter like Epoch converter.

pub fn set_end_time(self, input: Option<DateTime>) -> Self

The end of the time interval for which to get log data.

Constraints:

• Specified in Coordinated Universal Time (UTC).

• Specified in the Unix time format.

  For example, if you wish to use an end time of October 1, 2018, at 9 PM UTC, specify 1538427600 as the end time.

You can convert a human-friendly time to Unix time format using a converter like Epoch converter.

pub fn filter_pattern(self, inp: impl Into<String>) -> Self

The pattern to use to filter the returned log events to a specific term.

The following are a few examples of filter patterns that you can specify:

• To return all log events, specify a filter pattern of "".

• To exclude log events that contain the ERROR term, and return all other log events, specify a filter pattern of "-ERROR".

• To return log events that contain the ERROR term, specify a filter pattern of "ERROR".

• To return log events that contain both the ERROR and Exception terms, specify a filter pattern of "ERROR Exception".

• To return log events that contain the ERROR or the Exception term, specify a filter pattern of "?ERROR ?Exception".

pub fn set_filter_pattern(self, input: Option<String>) -> Self

The pattern to use to filter the returned log events to a specific term.

The following are a few examples of filter patterns that you can specify:

• To return all log events, specify a filter pattern of "".

• To exclude log events that contain the ERROR term, and return all other log events, specify a filter pattern of "-ERROR".

• To return log events that contain the ERROR term, specify a filter pattern of "ERROR".

• To return log events that contain both the ERROR and Exception terms, specify a filter pattern of "ERROR Exception".

• To return log events that contain the ERROR or the Exception term, specify a filter pattern of "?ERROR ?Exception".

pub fn page_token(self, inp: impl Into<String>) -> Self

The token to advance to the next page of results from your request.

To get a page token, perform an initial GetContainerLog request. If your results are paginated, the response will return a next page token that you can specify as the page token in a subsequent request.

pub fn set_page_token(self, input: Option<String>) -> Self

The token to advance to the next page of results from your request.

To get a page token, perform an initial GetContainerLog request. If your results are paginated, the response will return a next page token that you can specify as the page token in a subsequent request.

Trait Implementations

impl<C: Debug, M: Debug, R: Debug> Debug for GetContainerLog<C, M, R>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.