Skip to content
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

fix flatten_dictionary to work with ceph infernalis #7

Open
wants to merge 1 commit into
base: calamari
Choose a base branch
from

Conversation

strima
Copy link

@strima strima commented Nov 13, 2015

since at least ceph infernalis the dumped structure looks like this excerpt:

u'mds_epoch': {u'nick': u'', u'type': 2, u'description': u'Current epoch of MDS map'},

w/o this fix you get e.g. a path of [(['cluster','mds_epoch','description'],'Current epoch of MDS map')]

instead of the assumed [(['cluster','mds_epoch','type'],2)]

this was (at least for me) the reason why dashboard didn't show any iops/usage values. these values never made it to the graphite instance and therefore i didn't have any ceph.cluster. values in graphite which of course led to not showing them ;)

since at least ceph infernalis the dumped structure looks like this excerpt:

u'mds_epoch': {u'nick': u'', u'type': 2, u'description': u'Current epoch of MDS map'}, 

w/o this fix you get e.g. a path of [(['cluster','mds_epoch','description'],'Current epoch of MDS map')]

instead of the assumed  [(['cluster','mds_epoch','type'],2)]
@ChristinaMeno
Copy link

@strima Thank you! I have fixed this here https://github.com/python-diamond/Diamond/pull/321/files#diff-733cf31c9f55d206bd14fa56ed0f985bR335 as well.

I intend to merge that work into this repo and build new packages for download.ceph.com.
If you'd like to try out the latest just build diamond from my branch in that PR

@ChristinaMeno
Copy link

@strima Also our approaches to solving this issue seem different. I'm doing a whitelist of schema fields to report stats on. See my comment on the upstream PR. You seem to be blacklisting schema fields that are present today. It's my opinion that the white-list approach is better because it will handle future additions to the schema without modifications. What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants