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

Import data directly rather than via MMV #2

Open
lzap opened this issue Mar 8, 2017 · 2 comments
Open

Import data directly rather than via MMV #2

lzap opened this issue Mar 8, 2017 · 2 comments

Comments

@lzap
Copy link
Owner

lzap commented Mar 8, 2017

There is an API to write directly to logs: http://pcp.io/docs/lab.importdata.html

This sounds better than sampling, but there are no golang bindings. Perl prototype could be easy tho, but this should be rather complementary mode.

@lzap
Copy link
Owner Author

lzap commented Mar 9, 2017

@natoscott can you give me hint with this one? I very much like the idea of "offline" data collection. I can write a super simple code that will persist all statsd measurements in an (archive) file and then Perl script that will import this into PCP. This could be the default setting for "ad-hoc" monitoring when performance issue appears in our project to let users quickly record "something" we can easily investigate with PCP.

Now, I can see PCP already have some tools to import data (sar2pcp, sheet2pcp), to not reinvent the wheel, I was thinking to store it in some already known (and efficient) format. What would be your recommendation? Thanks

@lzap
Copy link
Owner Author

lzap commented Mar 9, 2017

I quickly hacked together a simple statsd seriazer based on MessagePack binary format which I can easily pick up in C or Perl. The PMI API does not seem to be complex, it might be possible to write a Ruby FFI wrapper, not sure how safe is this to do from application context tho.

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

No branches or pull requests

1 participant