-
Notifications
You must be signed in to change notification settings - Fork 47
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
persister components crash #493
Comments
u'df.inodes.total,_region=useast,_tenant_id=47bb0f0c63064fc7b777a5da50b3c0fc,availableZone=cn-north-3a,endpoint=salt-haproxy,fstype=ext4,instance_name=test,mount=/,service=vm,serviec_type=ecs,step=30,tenant_id=d8e805fc-bf4f-4d2d-93a5-3a8a988cb2f2,type=GAUGE,uuid=3143c43a-f794-4685-8a99-87f466bfc6c6 value=2485504.0,value_meta="{}" 1548321460000']: |
Hmm, never encountered such error. Could you search for |
What's more strange that after looking to influxdb code this error should return more information and not end after |
Other problem could be that this repo contain quite old monasca-persister, I should probably push more to have https://github.com/openstack/monasca-persister/tree/master/docker pushed to docker hub. |
This issue tracker is wrong place to report this. We are looking here mostly for docker part. You will need to fill new story and assign monasca-persister as a relevant project. Then tag it as a bug. Here some introduction to StoryBoard: https://www.youtube.com/watch?v=n_PaKuN4Skk Here example of reported bug for monasca-persister: |
hello,@matrixik i fix this issue: https://review.openstack.org/#/c/638589/ |
hello,monasca persister components crashed after run a long time.
error:InfluxDBClientError: 400: {"error":"unable to parse points"}
is metrics format error?
The text was updated successfully, but these errors were encountered: