Draft proposal for a o11y index page #29
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: arthursens <[email protected]>
bwplotka
reviewed
Nov 23, 2020
There was a problem hiding this comment.
uuu @ArthurSens you are accelerating fast 💪 Yes, let's discuss this. Please add it to the agenda 🤗
|
Added 🙂 |
Signed-off-by: arthursens <[email protected]>
|
Revisiting this, is this draft still active? Have discussions stalled? |
halcyondude
added
documentation
|
Is there interest in resolving this, or is it still stalled? Could an o11y index page be handled by the observe-k8s WG and their site? |
|
No response on this PR. Closing for now. Let's reopen if there is renewed interest. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a draft proposal for #19 that I'd like to get some opinions on our next meeting.
What I'd like to discuss:
What people think about this table-driven layout?
Are we "collecting" materials about Observability only, or do we want project-specific as well? E.g., my questions at Guidelines for developers on how to implement new metrics #18 were strongly related to Prometheus, do we want to provide the answer here or to leave it to the Prometheus team?
How do we accept community contributions to this index?
We need a written guide with all the requirements to accept a new entry.
Signed-off-by: arthursens [email protected]