aws_sdk_applicationinsights/lib.rs
1#![allow(deprecated)]
2#![allow(unknown_lints)]
3#![allow(clippy::module_inception)]
4#![allow(clippy::upper_case_acronyms)]
5#![allow(clippy::large_enum_variant)]
6#![allow(clippy::wrong_self_convention)]
7#![allow(clippy::should_implement_trait)]
8#![allow(clippy::disallowed_names)]
9#![allow(clippy::vec_init_then_push)]
10#![allow(clippy::type_complexity)]
11#![allow(clippy::needless_return)]
12#![allow(clippy::derive_partial_eq_without_eq)]
13#![allow(clippy::result_large_err)]
14#![allow(clippy::unnecessary_map_on_constructor)]
15#![allow(rustdoc::bare_urls)]
16#![allow(rustdoc::redundant_explicit_links)]
17#![allow(rustdoc::invalid_html_tags)]
18#![forbid(unsafe_code)]
19#![warn(missing_docs)]
20#![cfg_attr(docsrs, feature(doc_auto_cfg))]
21//! Amazon CloudWatch Application Insights is a service that helps you detect common problems with your applications. It enables you to pinpoint the source of issues in your applications (built with technologies such as Microsoft IIS, .NET, and Microsoft SQL Server), by providing key insights into detected problems.
22//!
23//! After you onboard your application, CloudWatch Application Insights identifies, recommends, and sets up metrics and logs. It continuously analyzes and correlates your metrics and logs for unusual behavior to surface actionable problems with your application. For example, if your application is slow and unresponsive and leading to HTTP 500 errors in your Application Load Balancer (ALB), Application Insights informs you that a memory pressure problem with your SQL Server database is occurring. It bases this analysis on impactful metrics and log errors.
24//!
25//! ## Getting Started
26//!
27//! > Examples are available for many services and operations, check out the
28//! > [examples folder in GitHub](https://github.com/awslabs/aws-sdk-rust/tree/main/examples).
29//!
30//! The SDK provides one crate per AWS service. You must add [Tokio](https://crates.io/crates/tokio)
31//! as a dependency within your Rust project to execute asynchronous code. To add `aws-sdk-applicationinsights` to
32//! your project, add the following to your **Cargo.toml** file:
33//!
34//! ```toml
35//! [dependencies]
36//! aws-config = { version = "1.1.7", features = ["behavior-version-latest"] }
37//! aws-sdk-applicationinsights = "1.74.0"
38//! tokio = { version = "1", features = ["full"] }
39//! ```
40//!
41//! Then in code, a client can be created with the following:
42//!
43//! ```rust,no_run
44//! use aws_sdk_applicationinsights as applicationinsights;
45//!
46//! #[::tokio::main]
47//! async fn main() -> Result<(), applicationinsights::Error> {
48//! let config = aws_config::load_from_env().await;
49//! let client = aws_sdk_applicationinsights::Client::new(&config);
50//!
51//! // ... make some calls with the client
52//!
53//! Ok(())
54//! }
55//! ```
56//!
57//! See the [client documentation](https://docs.rs/aws-sdk-applicationinsights/latest/aws_sdk_applicationinsights/client/struct.Client.html)
58//! for information on what calls can be made, and the inputs and outputs for each of those calls.
59//!
60//! ## Using the SDK
61//!
62//! Until the SDK is released, we will be adding information about using the SDK to the
63//! [Developer Guide](https://docs.aws.amazon.com/sdk-for-rust/latest/dg/welcome.html). Feel free to suggest
64//! additional sections for the guide by opening an issue and describing what you are trying to do.
65//!
66//! ## Getting Help
67//!
68//! * [GitHub discussions](https://github.com/awslabs/aws-sdk-rust/discussions) - For ideas, RFCs & general questions
69//! * [GitHub issues](https://github.com/awslabs/aws-sdk-rust/issues/new/choose) - For bug reports & feature requests
70//! * [Generated Docs (latest version)](https://awslabs.github.io/aws-sdk-rust/)
71//! * [Usage examples](https://github.com/awslabs/aws-sdk-rust/tree/main/examples)
72//!
73//!
74//! # Crate Organization
75//!
76//! The entry point for most customers will be [`Client`], which exposes one method for each API
77//! offered by Amazon CloudWatch Application Insights. The return value of each of these methods is a "fluent builder",
78//! where the different inputs for that API are added by builder-style function call chaining,
79//! followed by calling `send()` to get a [`Future`](std::future::Future) that will result in
80//! either a successful output or a [`SdkError`](crate::error::SdkError).
81//!
82//! Some of these API inputs may be structs or enums to provide more complex structured information.
83//! These structs and enums live in [`types`](crate::types). There are some simpler types for
84//! representing data such as date times or binary blobs that live in [`primitives`](crate::primitives).
85//!
86//! All types required to configure a client via the [`Config`](crate::Config) struct live
87//! in [`config`](crate::config).
88//!
89//! The [`operation`](crate::operation) module has a submodule for every API, and in each submodule
90//! is the input, output, and error type for that API, as well as builders to construct each of those.
91//!
92//! There is a top-level [`Error`](crate::Error) type that encompasses all the errors that the
93//! client can return. Any other error type can be converted to this `Error` type via the
94//! [`From`](std::convert::From) trait.
95//!
96//! The other modules within this crate are not required for normal usage.
97
98// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
99pub use error_meta::Error;
100
101#[doc(inline)]
102pub use config::Config;
103
104/// Client for calling Amazon CloudWatch Application Insights.
105/// ## Constructing a `Client`
106///
107/// A [`Config`] is required to construct a client. For most use cases, the [`aws-config`]
108/// crate should be used to automatically resolve this config using
109/// [`aws_config::load_from_env()`], since this will resolve an [`SdkConfig`] which can be shared
110/// across multiple different AWS SDK clients. This config resolution process can be customized
111/// by calling [`aws_config::from_env()`] instead, which returns a [`ConfigLoader`] that uses
112/// the [builder pattern] to customize the default config.
113///
114/// In the simplest case, creating a client looks as follows:
115/// ```rust,no_run
116/// # async fn wrapper() {
117/// let config = aws_config::load_from_env().await;
118/// let client = aws_sdk_applicationinsights::Client::new(&config);
119/// # }
120/// ```
121///
122/// Occasionally, SDKs may have additional service-specific values that can be set on the [`Config`] that
123/// is absent from [`SdkConfig`], or slightly different settings for a specific client may be desired.
124/// The [`Builder`](crate::config::Builder) struct implements `From<&SdkConfig>`, so setting these specific settings can be
125/// done as follows:
126///
127/// ```rust,no_run
128/// # async fn wrapper() {
129/// let sdk_config = ::aws_config::load_from_env().await;
130/// let config = aws_sdk_applicationinsights::config::Builder::from(&sdk_config)
131/// # /*
132/// .some_service_specific_setting("value")
133/// # */
134/// .build();
135/// # }
136/// ```
137///
138/// See the [`aws-config` docs] and [`Config`] for more information on customizing configuration.
139///
140/// _Note:_ Client construction is expensive due to connection thread pool initialization, and should
141/// be done once at application start-up.
142///
143/// [`Config`]: crate::Config
144/// [`ConfigLoader`]: https://docs.rs/aws-config/*/aws_config/struct.ConfigLoader.html
145/// [`SdkConfig`]: https://docs.rs/aws-config/*/aws_config/struct.SdkConfig.html
146/// [`aws-config` docs]: https://docs.rs/aws-config/*
147/// [`aws-config`]: https://crates.io/crates/aws-config
148/// [`aws_config::from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.from_env.html
149/// [`aws_config::load_from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.load_from_env.html
150/// [builder pattern]: https://rust-lang.github.io/api-guidelines/type-safety.html#builders-enable-construction-of-complex-values-c-builder
151/// # Using the `Client`
152///
153/// A client has a function for every operation that can be performed by the service.
154/// For example, the [`AddWorkload`](crate::operation::add_workload) operation has
155/// a [`Client::add_workload`], function which returns a builder for that operation.
156/// The fluent builder ultimately has a `send()` function that returns an async future that
157/// returns a result, as illustrated below:
158///
159/// ```rust,ignore
160/// let result = client.add_workload()
161/// .resource_group_name("example")
162/// .send()
163/// .await;
164/// ```
165///
166/// The underlying HTTP requests that get made by this can be modified with the `customize_operation`
167/// function on the fluent builder. See the [`customize`](crate::client::customize) module for more
168/// information.
169pub mod client;
170
171/// Configuration for Amazon CloudWatch Application Insights.
172pub mod config;
173
174/// Common errors and error handling utilities.
175pub mod error;
176
177mod error_meta;
178
179/// Information about this crate.
180pub mod meta;
181
182/// All operations that this crate can perform.
183pub mod operation;
184
185/// Primitives such as `Blob` or `DateTime` used by other types.
186pub mod primitives;
187
188/// Data structures used by operation inputs/outputs.
189pub mod types;
190
191mod auth_plugin;
192
193pub(crate) mod protocol_serde;
194
195mod sdk_feature_tracker;
196
197mod serialization_settings;
198
199mod endpoint_lib;
200
201mod lens;
202
203mod json_errors;
204
205mod serde_util;
206
207#[doc(inline)]
208pub use client::Client;