Dima Tisnek
Dima Tisnek
On the subjects of: - log and trace data correlation - jhack support It would be enough if we: - add smth like `[traceid, spanid]` to each log line that's...
Today, charm logs are not delivered to COS, because Juju controller cannot be related to Loki. There's experimental https://github.com/canonical/loki-k8s-operator/blob/main/lib/charms/loki_k8s/v0/charm_logging.py though that still needs to be thought through (push in-line? batch?...
One idea: we could emit extra logs at TRACE level, so that by default (DEBUG) they are not emitted/captured. Some folks do collect logs from production, and then process them...
Re: format, presumably `tracedId: "42424242"` with this capitalisation, with or without quotes, fixed or variable width traceid hex representation, etc. Prior art: https://www.reddit.com/r/devops/comments/1ggg14y/correlating_logs_and_traces_in_grafana/ Upstream docs: https://grafana.com/docs/grafana/latest/explore/trace-integration/
Improve ops tracing integration tests / a little simpler setup: https://github.com/canonical/pyroscope-k8s-operator/pull/109/files#diff-fe4b41d4a56a8bea9ef29cdcb16196e3fb1bee5eda7f04cacbfe7da1acfe6fc8
I've created separate issues for future work.
Actually I also experience similar, albeit less extreme, issue when editing a file with a merge conflict -- the `>>>
As far as I can tell, my config has `set re=0` already.
Ahh I didn’t think about that. Let me ask Python ideas.
https://discuss.python.org/t/would-it-be-awesome-if-docstrings-were-stamped-with-where-they-were-defined/64667