kvm-switch VS jmespath.py

With my COVID obsession of live streaming while writing code, I ended up building something a little more elaborate. https://github.com/timgws/kvm-switch

It doesn't use DDC commands direct to the monitor(s), instead swapping it for a HDMI matrix combined with a traditional KVM for swapping around inputs smoothly when you roll your mouse over the edge of different operating systems.

The switching client runs on Windows, MacOS and Linux (if you use X).

I had the same issue with this device. I ended up writing some code that you could run on a machine to operate the switching via the RS232 port: https://github.com/timgws/kvm-switch/

Bonus for adding 'glide and switch' functionality, so you can move the mouse to the edge of the screen and it would jump the input to the next display in your layout. It's like a hardware version of Synergy.

Very finicky device, but if you don't touch it - and you don't use any of the shortcuts - it works.

The proverb 'necessity is the mother of invention' made me build a solution for sharing a keyboard and mouse between multiple devices.

Synergy/Barrier is not horrible, but I find the latency a little painful.

Ended up getting an industrial HDMI switch, with a KVM. Built a server in Go that connects to the serial port of all the devices.

A companion client that runs on all the machines tells the server when the mouse moves to the edge of the screen, so the USB inputs can be switched to the correct computer. Basically, it allows you to have multiple computers connected, to multiple displays, sharing one keyboard and mouse. (You can define layouts on the server, so the displays can move around on the matrix HDMI switcher).

https://github.com/timgws/kvm-switch

The Azure CLI lets us write queries to filter the results of the az storage blob list command. The queries are written in JMESPath, which is a query language for JSON. In this case, we are filtering the results to only include blobs that end with the .bacpac extension and then selecting the first one as ordered by the lastModified property. If there are no blobs found, the script exits with a failure code. If we find a blob, we download it to the local path specified by the localPath variable.

For JSON there is the `jmespath` library which might help.

https://github.com/jmespath/jmespath.py

I love jq, but I also use JMESPath (especially with AWS CLI), yq (bundled with tomlq and xq as well), and dasel [2]. I also wish hclq [3] wasn't so dead!

[0]: https://jmespath.org/

Probably writing the query side of things is a lot of the fun here, but there is actually a spec (and a complying Rust impl) you can hook into for this JQ-like querying: https://jmespath.org/ ( https://github.com/jmespath/jmespath.rs ).

Thanks to custom variables that use labels, we can create various filters for the dashboard. You can look up my configuration of variables and extend it with an analogy way for your own needs. At the top, I marked the filter with detected pods in selected namespace. In the lower part, you can see a preview of all labels that are associated with a single log line. Most labels are meta information that Promtail adds during scraping targets. This part of the Promtail configuration provides it. In this section, I also marked a few labels that not comes out-of-the box e.g. leavel , class , thread . We added these labels using the Promtail json stage. You need to know that Promtail processes scraped logs in a pipeline. A pipeline is comprised of a set of stages. json stage is a parsing stage that reads the log line as JSON and accepts JMESPath expressions to extract data.

The tester on the official website for JMESPath (what json_query is doing) has been useful to me: https://jmespath.org/

Interesting. How does this compared to Jmespath? Not saying Jmespath is superior, just wondering whether you were aware of it.