Closed kchodorow closed 12 years ago
Could you please clarify what you'd like to be sendable? The final frames, in a JSON file?
Some self-contained thing, so frames + HTML/JS/CSS so someone can open logl.html and be set.
Also mentioned as possibilities were video or just a text description of what happened. We can talk about it more post-.1, maybe users will have other ideas.
In it's current form, we create a file of type, '.edda' that is a json object with a frames, servers, and amin information fields inside of it. This is much smaller than the original files, and all someone has to do is load this one file into edda, the same way as they would a log file and edda will run the same way it always does.
Every time you run edda, a '[coll_name].edda' file is generated.
Can you document this new feature?
Working on doing that now. Where besides the changes.txt should it be documented?
On Tue, Aug 7, 2012 at 10:25 AM, Kristina notifications@github.com wrote:
Can you document this new feature?
— Reply to this email directly or view it on GitHubhttps://github.com/kchodorow/edda/issues/83#issuecomment-7554928.
3 places I can think of:
Done
Have a way of exporting this so you can send it to someone. Maybe export events to a json file that can be loaded as the data.
What would be awesome: be able to have ops guys get an email every day with what the cluster did that day.