-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in publishing cloudwatch metrics #54
Labels
bug
Something isn't working
Comments
taoj-action
pushed a commit
that referenced
this issue
Nov 11, 2019
Reported at: #54 The input params are not used to set monitor service in cloudwatch Init function. The empty appName, streamName and workerID cause PutMetricData failed with error string "Error in publishing cloudwatch metrics. Error: InvalidParameter...". Signed-off-by: Tao Jiang <taoj@vmware.com>
taoj-action
pushed a commit
that referenced
this issue
Nov 11, 2019
Reported at: #54 The input params are not used to set monitor service in cloudwatch Init function. The empty appName, streamName and workerID cause PutMetricData failed with error string "Error in publishing cloudwatch metrics. Error: InvalidParameter...". Signed-off-by: Tao Jiang <taoj@vmware.com>
Thanks for reporting this bug. It has been fixed in the latest commit. |
taoj-action
pushed a commit
to vmware/vmware-go-kcl-v2
that referenced
this issue
Dec 21, 2021
Reported at: vmware/vmware-go-kcl#54 The input params are not used to set monitor service in cloudwatch Init function. The empty appName, streamName and workerID cause PutMetricData failed with error string "Error in publishing cloudwatch metrics. Error: InvalidParameter...". Signed-off-by: Tao Jiang <taoj@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems the input params are not used to set monitor service in cloudwatch Init function.
The empty appName, streamName and workerID cause PutMetricData failed with error string "Error in publishing cloudwatch metrics. Error: InvalidParameter...".
Could you help to check this issue? Thanks.
The text was updated successfully, but these errors were encountered: