Kong / Kong/developer.konghq.com
O11y rework: SPIKE use case how tos
Open
Nobody has claimed this yet.
docs-improvements
internal
product:advanced-analytics
- Dominant language
- Ruby
- Stars
- 28
- Forks
- 121
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 313
Description
Definition of done
- Find/ask for content to build O11y use case docs like:
- My app is slow
- My service is failing
- Doc based on SE demo framework
- Deep learning on O11y in Konnect/explorer/reporting/dashboards/debugger
Inspiration: tutorials here https://docs.newrelic.com/docs/new-relic-solutions/tutorial-landing-page/
Information
DRP: Christian H.
Size
M
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed use cases—“My app is slow” and “My service is failing”—and the linked New Relic tutorial examples. Explore observability in Konnect, Explorer, Reporting, Dashboards, and Debugger, and ask for content based on the SE demo framework. Done means the required source content and direction for O11y use-case documentation are identified.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, observability
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100