distribution(goals): add monitoring developer experience #2184
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -67,6 +67,16 @@ Creating a new release for our deployments is currently a semi-automated process | |
| - Document project and folder usage guidelines. | ||
| - Set spending limits for dynamic environments. | ||
|
|
||
| ### Improve Sourcegraph monitoring developer experience | ||
|
|
||
| - **Owner**: Gonza, Robert | ||
|
There was a problem hiding this comment. @pecigonzalo not sure who to add as owners here, saw that we generally seem to have 2 owners so I just added the two of us There was a problem hiding this comment. Its generally the one spearheading the project, I think it would make sense for it to be you and @davejrt as I can only sporadically work on project unfortunately. |
||
| - **Status**: In progress. Estimated completion by end of FY21-Q1. | ||
| - **Outcomes**: | ||
| - Our monitoring stack is compelling for engineers at Sourcegraph to interact with and build on top of. | ||
| - Our monitoring stack supports use cases specific to the needs of engineers at Sourcegraph and Sourcegraph Cloud. | ||
| - **Milestones**: | ||
| - [Monitoring pillar redux](https://github.com/orgs/sourcegraph/projects/112) | ||
|
|
||
| ## Future goals | ||
|
|
||
| These are ideas for future goals that the team might work on. Just because something is on this list, does not mean it will be worked on next. | ||
|
|
||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be more tightly scoped. There isn't a clear end here. We could always improve the monitoring experience.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the "monitoring development" experience, not the general monitoring experience. I see your point here, but I believe this should defined by the desired outcomes more than its title.
Still it could be possible you dont think the outcomes tighten that scope enough.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that both the title and the documented outcomes are not clear and scoped. A reader needs to be able to understand what done looks like. A problem statement is also missing.