PutProjectEvents
Sends performance events to Evidently. These events can be used to evaluate a launch or an experiment.
Request Syntax
POST /events/projects/project
HTTP/1.1
Content-type: application/json
{
"events": [
{
"data": "string
",
"timestamp": number
,
"type": "string
"
}
]
}
URI Request Parameters
The request uses the following URI parameters.
- project
-
The name or ARN of the project to write the events to.
Length Constraints: Minimum length of 0. Maximum length of 2048.
Pattern:
(^[a-zA-Z0-9._-]*$)|(arn:[^:]*:[^:]*:[^:]*:[^:]*:project/[a-zA-Z0-9._-]*)
Required: Yes
Request Body
The request accepts the following data in JSON format.
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"eventResults": [
{
"errorCode": "string",
"errorMessage": "string",
"eventId": "string"
}
],
"failedEventCount": number
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- eventResults
-
A structure that contains Evidently's response to the sent events, including an event ID and error codes, if any.
Type: Array of PutProjectEventsResultEntry objects
- failedEventCount
-
The number of events in the operation that could not be used by Evidently.
Type: Integer
Errors
For information about the errors that are common to all actions, see Common Errors.
- AccessDeniedException
-
You do not have sufficient permissions to perform this action.
HTTP Status Code: 403
- ResourceNotFoundException
-
The request references a resource that does not exist.
HTTP Status Code: 404
- ThrottlingException
-
The request was denied because of request throttling. Retry the request.
HTTP Status Code: 429
- ValidationException
-
The value of a parameter in the request caused an error.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: