Weyert de Boer

Yes, I noticed the same issue when using Linode to create a Streisand server. Connecting with OpenVN then it will show a IPv6 ip address from my ISP (Sky UK)

You might want to have a look at the `OpenFeature` specification [www.open-feature.dev](https://openfeature.dev)

As far as I know it's key-value pairs were the value can either be a string, or an array of strings?

I imagined something like below: The YAML listed below: ```yaml blah: blah bleh: - item1 - item2 - item3 ``` becomes something like this in JSON: ```json { "blah": "blah"...

Personally I think this is a problem for the integrator/vendor platform that integrates OpenSLO to solve not for us to worry about.

The metadata has a different purpose than the notations, though. The metadata is for the vendor to leverage e.g. for search, tagging. To display in a metadata panel. The annotations...

Sorry, what do you mean? There is `metadata.annotations` and `metadata.labels`. The first is implementation metadata, the latter is user metadata so free form metadata whatever it likes but it only...

I am liking the idea. Don't we already support `indicatorRef` in the objectives of a objective spec?

Are you sure you sure not logging to `stderr`? I have a similar issue with logging from Go binaries and I think Google Logging falls back to `error` log level...

I understand but can you check the labels in Google Logging for one of the log entries whether you don't have something like this in `labels` the value `logName: "projects/my-project/logs/stderr"`....