Bartlomiej Plotka

Results 277 issues of Bartlomiej Plotka

We had really interesting discussion around anomaly detection and its usefulness [here](https://docs.google.com/document/d/19am_KCYWU28ebLiIXv_P3ji96edxCTscVb4CzemXV5A/edit?disco=AAAAzqJtg58) It would be epic to unpack this and perhaps add more more color to out whitepaper. cc @beorn7...

cn-o11y-whitepaper-v1.1

[Suggestion](https://docs.google.com/document/d/19am_KCYWU28ebLiIXv_P3ji96edxCTscVb4CzemXV5A/edit?disco=AAAAzc2WBrI) from @vjsamuel > how about causality detection? we had a very interesting talk about usage of graphs for causality detection in 2022 Open Observability day NA @vjsamuel would you...

help wanted
cn-o11y-whitepaper-v1.1

Excellent [suggestion](https://docs.google.com/document/d/19am_KCYWU28ebLiIXv_P3ji96edxCTscVb4CzemXV5A/edit?disco=AAAAzolcw_Q from @beorn7 to explain symptom and root cause based alerting. This is related to explaining or even implementing SLIs.

help wanted
cn-o11y-whitepaper-v1.1

Solid suggestion from [our final 1.0 community review period](https://docs.google.com/document/d/19am_KCYWU28ebLiIXv_P3ji96edxCTscVb4CzemXV5A/edit?disco=AAAAzolcw-0) by @beorn7 > Which, as a side thought, reminds me of the question if "probing" should be an O11y signal as...

help wanted
cn-o11y-whitepaper-v1.1

Epic [idea](https://docs.google.com/document/d/19am_KCYWU28ebLiIXv_P3ji96edxCTscVb4CzemXV5A/edit?disco=AAAAzolcw-g) from @beorn7 to dive deeper on why we have so many signals: > Björn Rabenstein: we can't have a single bicycle that works efficiently on both asphalt roads...

help wanted
cn-o11y-whitepaper-v1.1

As @zeitlinger rightly pointed in [1](https://docs.google.com/document/d/19am_KCYWU28ebLiIXv_P3ji96edxCTscVb4CzemXV5A/edit?disco=AAAAzUTdWu4), [2](https://docs.google.com/document/d/19am_KCYWU28ebLiIXv_P3ji96edxCTscVb4CzemXV5A/edit?disco=AAAAzpy3f2U), [3](https://docs.google.com/document/d/19am_KCYWU28ebLiIXv_P3ji96edxCTscVb4CzemXV5A/edit?disco=AAAAzpy3f14) we have slight inconsistency in explaining each signal. We mention export, PII and retention only for logs, we mention instrumentation only for...

help wanted
cn-o11y-whitepaper-v1.1

Suggestion from [our final 1.0 community review period](https://docs.google.com/document/d/19am_KCYWU28ebLiIXv_P3ji96edxCTscVb4CzemXV5A/edit?disco=AAAAzozsj5Q) by @nicolastakashi. It might be indeed time to promote Continuous Profiling to main "three pillars" (which we renamed to primary signals). Not...

help wanted
cn-o11y-whitepaper-v1.1

Suggestion from [our final 1.0 community review period](https://docs.google.com/document/d/19am_KCYWU28ebLiIXv_P3ji96edxCTscVb4CzemXV5A/edit?disco=AAAAzpy3fzQ). How to define clear observabilty goals? What are healthy goals? What is too much, what's not enought? cc @nicolastakashi @zeitlinger

help wanted
cn-o11y-whitepaper-v1.1

It would epic to clarify what's manual vs auto instrumentation are. This also means explaining Prometheus exporter pattern, mentioning semi-manual instrumentation (libraries auto instrumenting functionality) etc.

help wanted
cn-o11y-whitepaper-v1.1

The idea that came from our TAG meeting community. Something to guide community on. Good practices, how far you can do with the current tooling.

ideas-and-suggestions