Observability story
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- go
- Domain
- backend, observability
Research direction
The issue mentions building user stories for observability (traces, audit, tokens) and integrating with standards like OpenTelemetry. Start by exploring the existing codebase for any logging, tracing, or monitoring components. Look for configuration files or modules related to networking and agentic AI to understand the current state. Determine what 'standard connectors' might be needed and how they would fit into the SAM architecture.
Written by the indexing model from the issue text.
Description
Traces, audit, tokens, ... These are important things that need to be clearly defined and described ... We need to build the user stories first and then look for standard connectors to avoid absorbing the entire problem and leverage existing ecosystem like in open telemetry
- Dominant language
- Go
- Stars
- 926
- Forks
- 138
- Avg merge
- 10h 37m
- Merged PRs (30d)
- 125
Getting set up
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.
More from google/sam
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
google/sam#484 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
testnet-health
Difficulty 4/5 3-5 days Newbie friendliness 32/100
Maintainers usually reply within 1 day
-
PEP storyOpen
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
GoogleCloudPlatform/k8s-config-connector#13462 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
coder/coder#29955 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/TypeScript#64453 ·
Maintainers usually reply within 1 day
-
OpenAI-compatible endpoint: response ids have only 999 possible values (chatcmpl-rand.Intn(999))Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day