You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MonitoringExecutionSummaries list empty after the endpoint envocation #1896
I have created deployed xgboost framework service, i was able to hit the endpoint with sagemaker runtime session, Now i have updated the xgboost endpoint to capture the i/o data, and created base line and Scheduled monitor job. After that i have invoked the service but monitoring execution summaries is empty, an i have not seen any s3 bucket also.
To reproduce
1.Create xgboost framework deployment.
2.updated endpoint with data capture logs
3.Create base line
4.schedule monitor job
5.invoke the endpoint
Error: Encoding mismatch: Encoding is CSV for endpointInput, but Encoding is JSON for endpointOutput. We currently only support the same type of input and output encoding at the moment.
2020-09-17 08:12:36 ERROR Main:80 - Error: Encoding mismatch: Encoding is CSV for endpointInput, but Encoding is JSON for endpointOutput. We currently only support the same type of input and output encoding at the moment.
On Sat, 19 Sep 2020, 02:52 icywang86rui, ***@***.***> wrote:
I have noticed that when the endpoint was deployed the csv_content_types
is not specified in your DataCaptureConfig. Have you tried adding it?
xgb_predictor = framework_xgb.deploy(initial_instance_count=1,
instance_type='ml.m4.xlarge',
endpoint_name=endpoint_name,
data_capture_config=DataCaptureConfig(enable_capture=True,
sampling_percentage=100,
destination_s3_uri='s3://{}/{}'.format(bucket, data_capture_prefix)
)
)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1896 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC5FIV7KN4OPGKI5IZ7FWL3SGPFRFANCNFSM4RO2BOFA>
.
@tiru1930 , Did you have any progress here ?
I'm having the same issue, but my error says that the encodingInput is JSON and the encoding Output is CSV. I've tried setting csv_content_types for both text/csv and for application/json, but none worked.
@tiru1930 , sorry for bothering you again, but I couldn't find anywhere in our code, but did you change somehow how XGBoost is returning your data ?
Reading the docs I've found that it outputs the predictions as a CSV, but your error seems to state the output is JSON encoded
@icywang86rui , could you help us out here, please ?
I've deployed my model again, this time setting the serializer and deserialzier to be the same, expecting the error to go away, but that didn't work.
Activity
tiru1930 commentedon Sep 17, 2020
now i can see cloud watch logs on hourly interval
but i got below error
icywang86rui commentedon Sep 17, 2020
@tiru1930 could you provide the code you used to produce this error here?
tiru1930 commentedon Sep 18, 2020
@icywang86rui Here is code
icywang86rui commentedon Sep 18, 2020
I have noticed that when the endpoint was deployed the
csv_content_typesis not specified in your DataCaptureConfig. Have you tried adding it?tiru1930 commentedon Sep 19, 2020
icywang86rui commentedon Sep 21, 2020
I see that you have configured DataCaptureConfig but csv_content_types is missing here.
lsabreu96 commentedon Jan 21, 2021
@tiru1930 , Did you have any progress here ?
I'm having the same issue, but my error says that the encodingInput is JSON and the encoding Output is CSV. I've tried setting csv_content_types for both text/csv and for application/json, but none worked.
tiru1930 commentedon Jan 21, 2021
lsabreu96 commentedon Jan 21, 2021
@tiru1930 , sorry for bothering you again, but I couldn't find anywhere in our code, but did you change somehow how XGBoost is returning your data ?
Reading the docs I've found that it outputs the predictions as a CSV, but your error seems to state the output is JSON encoded
lsabreu96 commentedon Jan 21, 2021
@icywang86rui , could you help us out here, please ?
I've deployed my model again, this time setting the serializer and deserialzier to be the same, expecting the error to go away, but that didn't work.