Ben Pfaff
Ben Pfaff
> Define a JSON schema for logs Is there a standard schema that we should use?
It appears, based on some cursory web searches, that there is no standard schema. tracing-subscriber, which we use, has a JSON logging format: https://docs.rs/tracing-subscriber/latest/tracing_subscriber/fmt/format/struct.Json.html
@mihaibudiu What Tz object are you thinking of? [`chrono::TimeZone`](https://docs.rs/chrono/latest/chrono/offset/trait.TimeZone.html) is a trait.
Oh I didn't know that crate. I guess it's https://docs.rs/chrono-tz/latest/chrono_tz/enum.Tz.html
This is not a matter of the manager version. This is the web console trying to talk the wrong protocol (HTTP vs HTTPS). The connections fail after the first few...
@gz I'm working on the secops demo because it's essential to the tour that I got assigned.
> @gz I'm working on the secops demo because it's essential to the tour that I got assigned. I finished with the secops demo but I'm new to this new...
We have support for a checkpoint label already. I'll look at the rest of this.
I spent a little time on this and I have questions. First, most checkpoints are created automatically, without user intervention. It's easy enough for the pipeline to add automatic metadata...
I do need a subset of this functionality to add multihost support, since the coordinator needs to query the pipelines about what checkpoints they have so that it can find...