GithubHelp home page GithubHelp logo

historical data about clip HOT 6 CLOSED

asmuth avatar asmuth commented on April 28, 2024
historical data

from clip.

Comments (6)

bernd avatar bernd commented on April 28, 2024

I haven't tested it yet, but it might be possible to add the _time parameter to the event payload. Like this.

echo "{\"_type\": \"unicorn_seen\", \"_time\":1326834487}" | nc localhost 1337

It will be set to the current unix timestamp by default.

from clip.

imajes avatar imajes commented on April 28, 2024

Yeah, I had wondered about that... and still wondering if anyone has any experience / experiments with this kind of historical data?

from clip.

asmuth avatar asmuth commented on April 28, 2024

Yes, as bernd pointed out you can either just set the _time field, or use the included importer:

If you usually run your fnordmetric app like this:

ruby my_fnordmetric_app.rb run

you can also invoke the "import" task like this:

ruby my_fnordmetric_app.rb import DUMP_FILE=/path/to/newline_seperated_events.json

If you use "progressive/persistent gauges" (any of your gauges has the :progressive => true option) the events in the dump_file need to be in chronological order (first line should be the oldest and last line should be the most recent).

Btw, there is a third task called "log" which you can use to create these log/dumpfiles:

ruby my_fnordmetric_app.rb log DUMP_FILE=/path/to/events_19.01.12.json

I'll add a readme section about this in the evening.

from clip.

imajes avatar imajes commented on April 28, 2024

This is super helpful, thanks! What would also help is a bit more docs on how best to convert different kinds of data into graphs. :)

On Jan 19, 2012, at 7:48, Paul [email protected] wrote:

Yes, as bernd pointed out you can either just set the _time field, or use the included importer:

If you usually run your fnordmetric app like this:

ruby my_fnordmetric_app.rb run

you can also invoke the "import" task like this:

ruby my_fnordmetric_app.rb import DUMP_FILE=/path/to/newline_seperated_events.json

If you use "progressive/persistent gauges" (any of your gauges has the :progressive => true option) the events in the dump_file need to be in chronological order (first line should be the oldest and last line should be the most recent).

Btw, there is a third task called "log" which you can use to create these log/dumpfiles:

ruby my_fnordmetric_app.rb import DUMP_FILE=/path/to/events_19.01.12.json

I'll add a readme section about this in the evening.


Reply to this email directly or view it on GitHub:
#43 (comment)

from clip.

knewter avatar knewter commented on April 28, 2024

I just posted a gist showing how I'm doing this currently (obv fake data): https://gist.github.com/1845317 /cc @imajes @bernd @paulasmuth

from clip.

skyriverbend avatar skyriverbend commented on April 28, 2024

Is there a reason why this issue has been left open? Looks like it's sorted right?

from clip.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.