Customizable event log format about wander HOT 4 CLOSED

@yuankaiyu this feature is now merged to the next branch.

You can try it out with

go install github.com/robinovitch61/wander@next

By default, the jq query is:

wander_event_jq_query: >
  .Events[] | {
      "1:Index": .Index,
      "2:Topic": .Topic,
      "3:Type": .Type,
      "4:Name": .Payload | (.Job // .Allocation // .Deployment // .Evaluation) | (.JobID // .ID),
      "5:AllocID": .Payload | (.Allocation // .Deployment // .Evaluation).ID[:8]
  }

As mentioned in the README of next, the numbering exists to preserve ordering, as https://github.com/itchyny/gojq does not keep the order of object keys unfortunately.

Use the following to get back the previous behavior:

wander_event_jq_query: .

Feel free to experiment with the query in your config file and let me know if you have suggestions to improve the default query. I'll probably release this feature broadly sometime in the middle of this week.

from wander.

Ya I'd like to watch the events rolling.
The fields I'm interested in are topic, type, alloc id, task id etc. Probably a general queriability is better because the fields needed may change over time.
Thanks for the quick response!

from wander.

Hi @yuankaiyu , thanks for opening an issue! This would be cool, and probably doable.

One workflow I could imagine today is saving the event log of interest with ctrl + s.

If you have wander_copy_save_path set to "true", the saved path will be copied to your clipboard on save.

Then you could run cat <paste path> | jq <your query>.

Probably still worth a native-in-wander solution. If you have a good idea for what default jq query for events might be best, let me know.

from wander.

Closed in 1793de1

Upgrade to >=v0.8.0 to use this feature

from wander.