Ask Your Question
0

Do we need Ceilometer middleware to be placed under SWIFT code base, just for "storage.objects.incoming.bytes" , "storage.objects.outgoing.bytes" and "storage.api.request" ., But not for other meters such as "storage.objects" , "storage.objects.size" etc?

asked 2014-08-06 04:36:53 -0500

Manish Singh gravatar image

updated 2014-08-08 15:41:57 -0500

smaffulli gravatar image

Do we need Ceilometer middleware to be placed under SWIFT code base, just for "storage.objects.incoming.bytes" , "storage.objects.outgoing.bytes" and "storage.api.request" ., But not for other meters such as "storage.objects" , "storage.objects.size" etc?

edit retag flag offensive close merge delete

Comments

I have a hard time parsing your question. Can you try to make it more clear?

smaffulli gravatar imagesmaffulli ( 2014-08-08 15:42:37 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-08-18 04:58:57 -0500

cdent gravatar image

The middleware is responsible for those three meters and no others. Those meters are in the middleware because they run in the swift-proxy rather than any of the (potentially many) swift servers. You only need to run the middleware if you want that information.

The meters that are created by swift itself give summary information about the service in general rather than information on specific requests.

The middleware creates information about the size of requests and responses associated with a context that can identify what party is making the request. Thus it could be used for billing, if desired.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2014-08-06 04:36:53 -0500

Seen: 278 times

Last updated: Aug 08 '14