-
Notifications
You must be signed in to change notification settings - Fork 10
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
Bucket Metering #2
Comments
So we do export stats on a namespace level, however to this point I did not have plans to do bucket level exports because of the time it takes to gather that level of data. It may be possible to create a bucket level exporter, where you have to query with a namespace. Would that be what you are looking for? P.S. I am curious what company you work for (if you can share that) |
Thanks for tour answer. |
Let me see what I can do. I have a few ideas on how to make this work. My concern is how long the ECS array takes to gather this data. |
Thanks for your answer.
I think (in my case) that time will not be too long. We have only 4
productions buckets and 4 tests buckets.
If we can put bucket as parameter, in case of lot of bucket, it will limit
metrics.
We can also imagine group of bucket and different frequency of collect.
Le sam. 19 janv. 2019 à 19:26, Mark D <[email protected]> a écrit :
… Let me see what I can do. I have a few ideas on how to make this work. My
concern is how long the ECS array takes to gather this data.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AsDcGlu1pdpKeNP7FeNekRDxI_En9tw0ks5vE2NqgaJpZM4ZmeGm>
.
|
Hi, |
We have code 3.8.x.x This is s från the Dell ECS dok 3.5x Secure ports 9101 and 10099 are reserved for internal communication between services and the ECS node I get the following error when running prometheus-emcecs exports. We have opened port 9101, 4443 and 9021 between the server running the exporter and all ecs nodes. If I look at which ports the ECS listens to, it seems that it is the internal IP addresses that listen to exactly port 9101 compared to e.g. 4443 admin@xxxmgmtn01:~> netstat -nl | grep 9101 admin@ecs1mgmtn01:~> netstat -nl | grabbed 4443 Error connecting to ECS Cluster at: http://172.XX.XXX.XX:9101/stats/dt/DTInitStat cluster=xxx1mgmtn01.dc.xxx.se package=ecsclient |
Hi,
I begin with most important : Happy new Year !
Since some weeks , I use your exporter. (Windows version ask by Franklin Piat who work with me ;-) )
I would like to know if you plan to include other metering in your exporter.
I look for informations about buckets to report after a migration from a Centera to ECS.
I found good examples in "https://github.com/bottkars/ECShell" but it's not possible "to batch" with it.
Thanks for your answer.
Lionel GERARD
The text was updated successfully, but these errors were encountered: