@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public interface AmazonCloudWatchEvidentlyAsync extends AmazonCloudWatchEvidently
AsyncHandler can be used to
receive notification when an asynchronous operation completes.
Note: Do not directly implement this interface, new methods are added to it regularly. Extend from
AbstractAmazonCloudWatchEvidentlyAsync instead.
You can use Amazon CloudWatch Evidently to safely validate new features by serving them to a specified percentage of your users while you roll out the feature. You can monitor the performance of the new feature to help you decide when to ramp up traffic to your users. This helps you reduce risk and identify unintended consequences before you fully launch the feature.
You can also conduct A/B experiments to make feature design decisions based on evidence and data. An experiment can test as many as five variations at once. Evidently collects experiment data and analyzes it using statistical methods. It also provides clear recommendations about which variations perform better. You can test both user-facing features and backend features.
ENDPOINT_PREFIXbatchEvaluateFeature, createExperiment, createFeature, createLaunch, createProject, createSegment, deleteExperiment, deleteFeature, deleteLaunch, deleteProject, deleteSegment, evaluateFeature, getCachedResponseMetadata, getExperiment, getExperimentResults, getFeature, getLaunch, getProject, getSegment, listExperiments, listFeatures, listLaunches, listProjects, listSegmentReferences, listSegments, listTagsForResource, putProjectEvents, shutdown, startExperiment, startLaunch, stopExperiment, stopLaunch, tagResource, testSegmentPattern, untagResource, updateExperiment, updateFeature, updateLaunch, updateProject, updateProjectDataDeliveryFuture<BatchEvaluateFeatureResult> batchEvaluateFeatureAsync(BatchEvaluateFeatureRequest batchEvaluateFeatureRequest)
This operation assigns feature variation to user sessions. For each user session, you pass in an
entityID that represents the user. Evidently then checks the evaluation rules and assigns the
variation.
The first rules that are evaluated are the override rules. If the user's entityID matches an
override rule, the user is served the variation specified by that rule.
Next, if there is a launch of the feature, the user might be assigned to a variation in the launch. The chance of this depends on the percentage of users that are allocated to that launch. If the user is enrolled in the launch, the variation they are served depends on the allocation of the various feature variations used for the launch.
If the user is not assigned to a launch, and there is an ongoing experiment for this feature, the user might be assigned to a variation in the experiment. The chance of this depends on the percentage of users that are allocated to that experiment. If the user is enrolled in the experiment, the variation they are served depends on the allocation of the various feature variations used for the experiment.
If the user is not assigned to a launch or experiment, they are served the default variation.
batchEvaluateFeatureRequest - Future<BatchEvaluateFeatureResult> batchEvaluateFeatureAsync(BatchEvaluateFeatureRequest batchEvaluateFeatureRequest, AsyncHandler<BatchEvaluateFeatureRequest,BatchEvaluateFeatureResult> asyncHandler)
This operation assigns feature variation to user sessions. For each user session, you pass in an
entityID that represents the user. Evidently then checks the evaluation rules and assigns the
variation.
The first rules that are evaluated are the override rules. If the user's entityID matches an
override rule, the user is served the variation specified by that rule.
Next, if there is a launch of the feature, the user might be assigned to a variation in the launch. The chance of this depends on the percentage of users that are allocated to that launch. If the user is enrolled in the launch, the variation they are served depends on the allocation of the various feature variations used for the launch.
If the user is not assigned to a launch, and there is an ongoing experiment for this feature, the user might be assigned to a variation in the experiment. The chance of this depends on the percentage of users that are allocated to that experiment. If the user is enrolled in the experiment, the variation they are served depends on the allocation of the various feature variations used for the experiment.
If the user is not assigned to a launch or experiment, they are served the default variation.
batchEvaluateFeatureRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<CreateExperimentResult> createExperimentAsync(CreateExperimentRequest createExperimentRequest)
Creates an Evidently experiment. Before you create an experiment, you must create the feature to use for the experiment.
An experiment helps you make feature design decisions based on evidence and data. An experiment can test as many as five variations at once. Evidently collects experiment data and analyzes it by statistical methods, and provides clear recommendations about which variations perform better.
You can optionally specify a segment to have the experiment consider only certain audience types in
the experiment, such as using only user sessions from a certain location or who use a certain internet browser.
Don't use this operation to update an existing experiment. Instead, use UpdateExperiment.
createExperimentRequest - Future<CreateExperimentResult> createExperimentAsync(CreateExperimentRequest createExperimentRequest, AsyncHandler<CreateExperimentRequest,CreateExperimentResult> asyncHandler)
Creates an Evidently experiment. Before you create an experiment, you must create the feature to use for the experiment.
An experiment helps you make feature design decisions based on evidence and data. An experiment can test as many as five variations at once. Evidently collects experiment data and analyzes it by statistical methods, and provides clear recommendations about which variations perform better.
You can optionally specify a segment to have the experiment consider only certain audience types in
the experiment, such as using only user sessions from a certain location or who use a certain internet browser.
Don't use this operation to update an existing experiment. Instead, use UpdateExperiment.
createExperimentRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<CreateFeatureResult> createFeatureAsync(CreateFeatureRequest createFeatureRequest)
Creates an Evidently feature that you want to launch or test. You can define up to five variations of a feature, and use these variations in your launches and experiments. A feature must be created in a project. For information about creating a project, see CreateProject.
Don't use this operation to update an existing feature. Instead, use UpdateFeature.
createFeatureRequest - Future<CreateFeatureResult> createFeatureAsync(CreateFeatureRequest createFeatureRequest, AsyncHandler<CreateFeatureRequest,CreateFeatureResult> asyncHandler)
Creates an Evidently feature that you want to launch or test. You can define up to five variations of a feature, and use these variations in your launches and experiments. A feature must be created in a project. For information about creating a project, see CreateProject.
Don't use this operation to update an existing feature. Instead, use UpdateFeature.
createFeatureRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<CreateLaunchResult> createLaunchAsync(CreateLaunchRequest createLaunchRequest)
Creates a launch of a given feature. Before you create a launch, you must create the feature to use for the launch.
You can use a launch to safely validate new features by serving them to a specified percentage of your users while you roll out the feature. You can monitor the performance of the new feature to help you decide when to ramp up traffic to more users. This helps you reduce risk and identify unintended consequences before you fully launch the feature.
Don't use this operation to update an existing launch. Instead, use UpdateLaunch.
createLaunchRequest - Future<CreateLaunchResult> createLaunchAsync(CreateLaunchRequest createLaunchRequest, AsyncHandler<CreateLaunchRequest,CreateLaunchResult> asyncHandler)
Creates a launch of a given feature. Before you create a launch, you must create the feature to use for the launch.
You can use a launch to safely validate new features by serving them to a specified percentage of your users while you roll out the feature. You can monitor the performance of the new feature to help you decide when to ramp up traffic to more users. This helps you reduce risk and identify unintended consequences before you fully launch the feature.
Don't use this operation to update an existing launch. Instead, use UpdateLaunch.
createLaunchRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<CreateProjectResult> createProjectAsync(CreateProjectRequest createProjectRequest)
Creates a project, which is the logical object in Evidently that can contain features, launches, and experiments. Use projects to group similar features together.
To update an existing project, use UpdateProject.
createProjectRequest - Future<CreateProjectResult> createProjectAsync(CreateProjectRequest createProjectRequest, AsyncHandler<CreateProjectRequest,CreateProjectResult> asyncHandler)
Creates a project, which is the logical object in Evidently that can contain features, launches, and experiments. Use projects to group similar features together.
To update an existing project, use UpdateProject.
createProjectRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<CreateSegmentResult> createSegmentAsync(CreateSegmentRequest createSegmentRequest)
Use this operation to define a segment of your audience. A segment is a portion of your audience that share one or more characteristics. Examples could be Chrome browser users, users in Europe, or Firefox browser users in Europe who also fit other criteria that your application collects, such as age.
Using a segment in an experiment limits that experiment to evaluate only the users who match the segment criteria. Using one or more segments in a launch allows you to define different traffic splits for the different audience segments.
For more information about segment pattern syntax, see Segment rule pattern syntax.
The pattern that you define for a segment is matched against the value of evaluationContext, which
is passed into Evidently in the EvaluateFeature operation, when Evidently assigns a feature variation to a user.
createSegmentRequest - Future<CreateSegmentResult> createSegmentAsync(CreateSegmentRequest createSegmentRequest, AsyncHandler<CreateSegmentRequest,CreateSegmentResult> asyncHandler)
Use this operation to define a segment of your audience. A segment is a portion of your audience that share one or more characteristics. Examples could be Chrome browser users, users in Europe, or Firefox browser users in Europe who also fit other criteria that your application collects, such as age.
Using a segment in an experiment limits that experiment to evaluate only the users who match the segment criteria. Using one or more segments in a launch allows you to define different traffic splits for the different audience segments.
For more information about segment pattern syntax, see Segment rule pattern syntax.
The pattern that you define for a segment is matched against the value of evaluationContext, which
is passed into Evidently in the EvaluateFeature operation, when Evidently assigns a feature variation to a user.
createSegmentRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<DeleteExperimentResult> deleteExperimentAsync(DeleteExperimentRequest deleteExperimentRequest)
Deletes an Evidently experiment. The feature used for the experiment is not deleted.
To stop an experiment without deleting it, use StopExperiment.
deleteExperimentRequest - Future<DeleteExperimentResult> deleteExperimentAsync(DeleteExperimentRequest deleteExperimentRequest, AsyncHandler<DeleteExperimentRequest,DeleteExperimentResult> asyncHandler)
Deletes an Evidently experiment. The feature used for the experiment is not deleted.
To stop an experiment without deleting it, use StopExperiment.
deleteExperimentRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<DeleteFeatureResult> deleteFeatureAsync(DeleteFeatureRequest deleteFeatureRequest)
Deletes an Evidently feature.
deleteFeatureRequest - Future<DeleteFeatureResult> deleteFeatureAsync(DeleteFeatureRequest deleteFeatureRequest, AsyncHandler<DeleteFeatureRequest,DeleteFeatureResult> asyncHandler)
Deletes an Evidently feature.
deleteFeatureRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<DeleteLaunchResult> deleteLaunchAsync(DeleteLaunchRequest deleteLaunchRequest)
Deletes an Evidently launch. The feature used for the launch is not deleted.
To stop a launch without deleting it, use StopLaunch.
deleteLaunchRequest - Future<DeleteLaunchResult> deleteLaunchAsync(DeleteLaunchRequest deleteLaunchRequest, AsyncHandler<DeleteLaunchRequest,DeleteLaunchResult> asyncHandler)
Deletes an Evidently launch. The feature used for the launch is not deleted.
To stop a launch without deleting it, use StopLaunch.
deleteLaunchRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<DeleteProjectResult> deleteProjectAsync(DeleteProjectRequest deleteProjectRequest)
Deletes an Evidently project. Before you can delete a project, you must delete all the features that the project contains. To delete a feature, use DeleteFeature.
deleteProjectRequest - Future<DeleteProjectResult> deleteProjectAsync(DeleteProjectRequest deleteProjectRequest, AsyncHandler<DeleteProjectRequest,DeleteProjectResult> asyncHandler)
Deletes an Evidently project. Before you can delete a project, you must delete all the features that the project contains. To delete a feature, use DeleteFeature.
deleteProjectRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<DeleteSegmentResult> deleteSegmentAsync(DeleteSegmentRequest deleteSegmentRequest)
Deletes a segment. You can't delete a segment that is being used in a launch or experiment, even if that launch or experiment is not currently running.
deleteSegmentRequest - Future<DeleteSegmentResult> deleteSegmentAsync(DeleteSegmentRequest deleteSegmentRequest, AsyncHandler<DeleteSegmentRequest,DeleteSegmentResult> asyncHandler)
Deletes a segment. You can't delete a segment that is being used in a launch or experiment, even if that launch or experiment is not currently running.
deleteSegmentRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<EvaluateFeatureResult> evaluateFeatureAsync(EvaluateFeatureRequest evaluateFeatureRequest)
This operation assigns a feature variation to one given user session. You pass in an entityID that
represents the user. Evidently then checks the evaluation rules and assigns the variation.
The first rules that are evaluated are the override rules. If the user's entityID matches an
override rule, the user is served the variation specified by that rule.
If there is a current launch with this feature that uses segment overrides, and if the user session's
evaluationContext matches a segment rule defined in a segment override, the configuration in the
segment overrides is used. For more information about segments, see CreateSegment and Use
segments to focus your audience.
If there is a launch with no segment overrides, the user might be assigned to a variation in the launch. The chance of this depends on the percentage of users that are allocated to that launch. If the user is enrolled in the launch, the variation they are served depends on the allocation of the various feature variations used for the launch.
If the user is not assigned to a launch, and there is an ongoing experiment for this feature, the user might be assigned to a variation in the experiment. The chance of this depends on the percentage of users that are allocated to that experiment.
If the experiment uses a segment, then only user sessions with evaluationContext values that match
the segment rule are used in the experiment.
If the user is enrolled in the experiment, the variation they are served depends on the allocation of the various feature variations used for the experiment.
If the user is not assigned to a launch or experiment, they are served the default variation.
evaluateFeatureRequest - Future<EvaluateFeatureResult> evaluateFeatureAsync(EvaluateFeatureRequest evaluateFeatureRequest, AsyncHandler<EvaluateFeatureRequest,EvaluateFeatureResult> asyncHandler)
This operation assigns a feature variation to one given user session. You pass in an entityID that
represents the user. Evidently then checks the evaluation rules and assigns the variation.
The first rules that are evaluated are the override rules. If the user's entityID matches an
override rule, the user is served the variation specified by that rule.
If there is a current launch with this feature that uses segment overrides, and if the user session's
evaluationContext matches a segment rule defined in a segment override, the configuration in the
segment overrides is used. For more information about segments, see CreateSegment and Use
segments to focus your audience.
If there is a launch with no segment overrides, the user might be assigned to a variation in the launch. The chance of this depends on the percentage of users that are allocated to that launch. If the user is enrolled in the launch, the variation they are served depends on the allocation of the various feature variations used for the launch.
If the user is not assigned to a launch, and there is an ongoing experiment for this feature, the user might be assigned to a variation in the experiment. The chance of this depends on the percentage of users that are allocated to that experiment.
If the experiment uses a segment, then only user sessions with evaluationContext values that match
the segment rule are used in the experiment.
If the user is enrolled in the experiment, the variation they are served depends on the allocation of the various feature variations used for the experiment.
If the user is not assigned to a launch or experiment, they are served the default variation.
evaluateFeatureRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<GetExperimentResult> getExperimentAsync(GetExperimentRequest getExperimentRequest)
Returns the details about one experiment. You must already know the experiment name. To retrieve a list of experiments in your account, use ListExperiments.
getExperimentRequest - Future<GetExperimentResult> getExperimentAsync(GetExperimentRequest getExperimentRequest, AsyncHandler<GetExperimentRequest,GetExperimentResult> asyncHandler)
Returns the details about one experiment. You must already know the experiment name. To retrieve a list of experiments in your account, use ListExperiments.
getExperimentRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<GetExperimentResultsResult> getExperimentResultsAsync(GetExperimentResultsRequest getExperimentResultsRequest)
Retrieves the results of a running or completed experiment. No results are available until there have been 100 events for each variation and at least 10 minutes have passed since the start of the experiment. To increase the statistical power, Evidently performs an additional offline p-value analysis at the end of the experiment. Offline p-value analysis can detect statistical significance in some cases where the anytime p-values used during the experiment do not find statistical significance.
Experiment results are available up to 63 days after the start of the experiment. They are not available after that because of CloudWatch data retention policies.
getExperimentResultsRequest - Future<GetExperimentResultsResult> getExperimentResultsAsync(GetExperimentResultsRequest getExperimentResultsRequest, AsyncHandler<GetExperimentResultsRequest,GetExperimentResultsResult> asyncHandler)
Retrieves the results of a running or completed experiment. No results are available until there have been 100 events for each variation and at least 10 minutes have passed since the start of the experiment. To increase the statistical power, Evidently performs an additional offline p-value analysis at the end of the experiment. Offline p-value analysis can detect statistical significance in some cases where the anytime p-values used during the experiment do not find statistical significance.
Experiment results are available up to 63 days after the start of the experiment. They are not available after that because of CloudWatch data retention policies.
getExperimentResultsRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<GetFeatureResult> getFeatureAsync(GetFeatureRequest getFeatureRequest)
Returns the details about one feature. You must already know the feature name. To retrieve a list of features in your account, use ListFeatures.
getFeatureRequest - Future<GetFeatureResult> getFeatureAsync(GetFeatureRequest getFeatureRequest, AsyncHandler<GetFeatureRequest,GetFeatureResult> asyncHandler)
Returns the details about one feature. You must already know the feature name. To retrieve a list of features in your account, use ListFeatures.
getFeatureRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<GetLaunchResult> getLaunchAsync(GetLaunchRequest getLaunchRequest)
Returns the details about one launch. You must already know the launch name. To retrieve a list of launches in your account, use ListLaunches.
getLaunchRequest - Future<GetLaunchResult> getLaunchAsync(GetLaunchRequest getLaunchRequest, AsyncHandler<GetLaunchRequest,GetLaunchResult> asyncHandler)
Returns the details about one launch. You must already know the launch name. To retrieve a list of launches in your account, use ListLaunches.
getLaunchRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<GetProjectResult> getProjectAsync(GetProjectRequest getProjectRequest)
Returns the details about one launch. You must already know the project name. To retrieve a list of projects in your account, use ListProjects.
getProjectRequest - Future<GetProjectResult> getProjectAsync(GetProjectRequest getProjectRequest, AsyncHandler<GetProjectRequest,GetProjectResult> asyncHandler)
Returns the details about one launch. You must already know the project name. To retrieve a list of projects in your account, use ListProjects.
getProjectRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<GetSegmentResult> getSegmentAsync(GetSegmentRequest getSegmentRequest)
Returns information about the specified segment. Specify the segment you want to view by specifying its ARN.
getSegmentRequest - Future<GetSegmentResult> getSegmentAsync(GetSegmentRequest getSegmentRequest, AsyncHandler<GetSegmentRequest,GetSegmentResult> asyncHandler)
Returns information about the specified segment. Specify the segment you want to view by specifying its ARN.
getSegmentRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<ListExperimentsResult> listExperimentsAsync(ListExperimentsRequest listExperimentsRequest)
Returns configuration details about all the experiments in the specified project.
listExperimentsRequest - Future<ListExperimentsResult> listExperimentsAsync(ListExperimentsRequest listExperimentsRequest, AsyncHandler<ListExperimentsRequest,ListExperimentsResult> asyncHandler)
Returns configuration details about all the experiments in the specified project.
listExperimentsRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<ListFeaturesResult> listFeaturesAsync(ListFeaturesRequest listFeaturesRequest)
Returns configuration details about all the features in the specified project.
listFeaturesRequest - Future<ListFeaturesResult> listFeaturesAsync(ListFeaturesRequest listFeaturesRequest, AsyncHandler<ListFeaturesRequest,ListFeaturesResult> asyncHandler)
Returns configuration details about all the features in the specified project.
listFeaturesRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<ListLaunchesResult> listLaunchesAsync(ListLaunchesRequest listLaunchesRequest)
Returns configuration details about all the launches in the specified project.
listLaunchesRequest - Future<ListLaunchesResult> listLaunchesAsync(ListLaunchesRequest listLaunchesRequest, AsyncHandler<ListLaunchesRequest,ListLaunchesResult> asyncHandler)
Returns configuration details about all the launches in the specified project.
listLaunchesRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<ListProjectsResult> listProjectsAsync(ListProjectsRequest listProjectsRequest)
Returns configuration details about all the projects in the current Region in your account.
listProjectsRequest - Future<ListProjectsResult> listProjectsAsync(ListProjectsRequest listProjectsRequest, AsyncHandler<ListProjectsRequest,ListProjectsResult> asyncHandler)
Returns configuration details about all the projects in the current Region in your account.
listProjectsRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<ListSegmentReferencesResult> listSegmentReferencesAsync(ListSegmentReferencesRequest listSegmentReferencesRequest)
Use this operation to find which experiments or launches are using a specified segment.
listSegmentReferencesRequest - Future<ListSegmentReferencesResult> listSegmentReferencesAsync(ListSegmentReferencesRequest listSegmentReferencesRequest, AsyncHandler<ListSegmentReferencesRequest,ListSegmentReferencesResult> asyncHandler)
Use this operation to find which experiments or launches are using a specified segment.
listSegmentReferencesRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<ListSegmentsResult> listSegmentsAsync(ListSegmentsRequest listSegmentsRequest)
Returns a list of audience segments that you have created in your account in this Region.
listSegmentsRequest - Future<ListSegmentsResult> listSegmentsAsync(ListSegmentsRequest listSegmentsRequest, AsyncHandler<ListSegmentsRequest,ListSegmentsResult> asyncHandler)
Returns a list of audience segments that you have created in your account in this Region.
listSegmentsRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<ListTagsForResourceResult> listTagsForResourceAsync(ListTagsForResourceRequest listTagsForResourceRequest)
Displays the tags associated with an Evidently resource.
listTagsForResourceRequest - Future<ListTagsForResourceResult> listTagsForResourceAsync(ListTagsForResourceRequest listTagsForResourceRequest, AsyncHandler<ListTagsForResourceRequest,ListTagsForResourceResult> asyncHandler)
Displays the tags associated with an Evidently resource.
listTagsForResourceRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<PutProjectEventsResult> putProjectEventsAsync(PutProjectEventsRequest putProjectEventsRequest)
Sends performance events to Evidently. These events can be used to evaluate a launch or an experiment.
putProjectEventsRequest - Future<PutProjectEventsResult> putProjectEventsAsync(PutProjectEventsRequest putProjectEventsRequest, AsyncHandler<PutProjectEventsRequest,PutProjectEventsResult> asyncHandler)
Sends performance events to Evidently. These events can be used to evaluate a launch or an experiment.
putProjectEventsRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<StartExperimentResult> startExperimentAsync(StartExperimentRequest startExperimentRequest)
Starts an existing experiment. To create an experiment, use CreateExperiment.
startExperimentRequest - Future<StartExperimentResult> startExperimentAsync(StartExperimentRequest startExperimentRequest, AsyncHandler<StartExperimentRequest,StartExperimentResult> asyncHandler)
Starts an existing experiment. To create an experiment, use CreateExperiment.
startExperimentRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<StartLaunchResult> startLaunchAsync(StartLaunchRequest startLaunchRequest)
Starts an existing launch. To create a launch, use CreateLaunch.
startLaunchRequest - Future<StartLaunchResult> startLaunchAsync(StartLaunchRequest startLaunchRequest, AsyncHandler<StartLaunchRequest,StartLaunchResult> asyncHandler)
Starts an existing launch. To create a launch, use CreateLaunch.
startLaunchRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<StopExperimentResult> stopExperimentAsync(StopExperimentRequest stopExperimentRequest)
Stops an experiment that is currently running. If you stop an experiment, you can't resume it or restart it.
stopExperimentRequest - Future<StopExperimentResult> stopExperimentAsync(StopExperimentRequest stopExperimentRequest, AsyncHandler<StopExperimentRequest,StopExperimentResult> asyncHandler)
Stops an experiment that is currently running. If you stop an experiment, you can't resume it or restart it.
stopExperimentRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<StopLaunchResult> stopLaunchAsync(StopLaunchRequest stopLaunchRequest)
Stops a launch that is currently running. After you stop a launch, you will not be able to resume it or restart it. Also, it will not be evaluated as a rule for traffic allocation, and the traffic that was allocated to the launch will instead be available to the feature's experiment, if there is one. Otherwise, all traffic will be served the default variation after the launch is stopped.
stopLaunchRequest - Future<StopLaunchResult> stopLaunchAsync(StopLaunchRequest stopLaunchRequest, AsyncHandler<StopLaunchRequest,StopLaunchResult> asyncHandler)
Stops a launch that is currently running. After you stop a launch, you will not be able to resume it or restart it. Also, it will not be evaluated as a rule for traffic allocation, and the traffic that was allocated to the launch will instead be available to the feature's experiment, if there is one. Otherwise, all traffic will be served the default variation after the launch is stopped.
stopLaunchRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<TagResourceResult> tagResourceAsync(TagResourceRequest tagResourceRequest)
Assigns one or more tags (key-value pairs) to the specified CloudWatch Evidently resource. Projects, features, launches, and experiments can be tagged.
Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.
Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.
You can use the TagResource action with a resource that already has tags. If you specify a new tag
key for the resource, this tag is appended to the list of tags associated with the alarm. If you specify a tag
key that is already associated with the resource, the new tag value that you specify replaces the previous value
for that tag.
You can associate as many as 50 tags with a resource.
For more information, see Tagging Amazon Web Services resources.
tagResourceRequest - Future<TagResourceResult> tagResourceAsync(TagResourceRequest tagResourceRequest, AsyncHandler<TagResourceRequest,TagResourceResult> asyncHandler)
Assigns one or more tags (key-value pairs) to the specified CloudWatch Evidently resource. Projects, features, launches, and experiments can be tagged.
Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.
Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.
You can use the TagResource action with a resource that already has tags. If you specify a new tag
key for the resource, this tag is appended to the list of tags associated with the alarm. If you specify a tag
key that is already associated with the resource, the new tag value that you specify replaces the previous value
for that tag.
You can associate as many as 50 tags with a resource.
For more information, see Tagging Amazon Web Services resources.
tagResourceRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<TestSegmentPatternResult> testSegmentPatternAsync(TestSegmentPatternRequest testSegmentPatternRequest)
Use this operation to test a rules pattern that you plan to use to create an audience segment. For more information about segments, see CreateSegment.
testSegmentPatternRequest - Future<TestSegmentPatternResult> testSegmentPatternAsync(TestSegmentPatternRequest testSegmentPatternRequest, AsyncHandler<TestSegmentPatternRequest,TestSegmentPatternResult> asyncHandler)
Use this operation to test a rules pattern that you plan to use to create an audience segment. For more information about segments, see CreateSegment.
testSegmentPatternRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<UntagResourceResult> untagResourceAsync(UntagResourceRequest untagResourceRequest)
Removes one or more tags from the specified resource.
untagResourceRequest - Future<UntagResourceResult> untagResourceAsync(UntagResourceRequest untagResourceRequest, AsyncHandler<UntagResourceRequest,UntagResourceResult> asyncHandler)
Removes one or more tags from the specified resource.
untagResourceRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<UpdateExperimentResult> updateExperimentAsync(UpdateExperimentRequest updateExperimentRequest)
Updates an Evidently experiment.
Don't use this operation to update an experiment's tag. Instead, use TagResource.
updateExperimentRequest - Future<UpdateExperimentResult> updateExperimentAsync(UpdateExperimentRequest updateExperimentRequest, AsyncHandler<UpdateExperimentRequest,UpdateExperimentResult> asyncHandler)
Updates an Evidently experiment.
Don't use this operation to update an experiment's tag. Instead, use TagResource.
updateExperimentRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<UpdateFeatureResult> updateFeatureAsync(UpdateFeatureRequest updateFeatureRequest)
Updates an existing feature.
You can't use this operation to update the tags of an existing feature. Instead, use TagResource.
updateFeatureRequest - Future<UpdateFeatureResult> updateFeatureAsync(UpdateFeatureRequest updateFeatureRequest, AsyncHandler<UpdateFeatureRequest,UpdateFeatureResult> asyncHandler)
Updates an existing feature.
You can't use this operation to update the tags of an existing feature. Instead, use TagResource.
updateFeatureRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<UpdateLaunchResult> updateLaunchAsync(UpdateLaunchRequest updateLaunchRequest)
Updates a launch of a given feature.
Don't use this operation to update the tags of an existing launch. Instead, use TagResource.
updateLaunchRequest - Future<UpdateLaunchResult> updateLaunchAsync(UpdateLaunchRequest updateLaunchRequest, AsyncHandler<UpdateLaunchRequest,UpdateLaunchResult> asyncHandler)
Updates a launch of a given feature.
Don't use this operation to update the tags of an existing launch. Instead, use TagResource.
updateLaunchRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<UpdateProjectResult> updateProjectAsync(UpdateProjectRequest updateProjectRequest)
Updates the description of an existing project.
To create a new project, use CreateProject.
Don't use this operation to update the data storage options of a project. Instead, use UpdateProjectDataDelivery.
Don't use this operation to update the tags of a project. Instead, use TagResource.
updateProjectRequest - Future<UpdateProjectResult> updateProjectAsync(UpdateProjectRequest updateProjectRequest, AsyncHandler<UpdateProjectRequest,UpdateProjectResult> asyncHandler)
Updates the description of an existing project.
To create a new project, use CreateProject.
Don't use this operation to update the data storage options of a project. Instead, use UpdateProjectDataDelivery.
Don't use this operation to update the tags of a project. Instead, use TagResource.
updateProjectRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<UpdateProjectDataDeliveryResult> updateProjectDataDeliveryAsync(UpdateProjectDataDeliveryRequest updateProjectDataDeliveryRequest)
Updates the data storage options for this project. If you store evaluation events, you an keep them and analyze them on your own. If you choose not to store evaluation events, Evidently deletes them after using them to produce metrics and other experiment results that you can view.
You can't specify both cloudWatchLogs and s3Destination in the same operation.
updateProjectDataDeliveryRequest - Future<UpdateProjectDataDeliveryResult> updateProjectDataDeliveryAsync(UpdateProjectDataDeliveryRequest updateProjectDataDeliveryRequest, AsyncHandler<UpdateProjectDataDeliveryRequest,UpdateProjectDataDeliveryResult> asyncHandler)
Updates the data storage options for this project. If you store evaluation events, you an keep them and analyze them on your own. If you choose not to store evaluation events, Evidently deletes them after using them to produce metrics and other experiment results that you can view.
You can't specify both cloudWatchLogs and s3Destination in the same operation.
updateProjectDataDeliveryRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.