[Bug]: errorType and projectId attribute is missing in the Analytics Event published to Moesif
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Gateway
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI), Aspect/Monitoring (Metrics, observability, health checks, alerts)
Description
In the current moesif dashboards, the Error Type Breakdown and Consumer Onboarding Trend charts are populated based on the data published under metadata.errorType and metadata.projectId properties published in the analytics event.
Currently the errorType is completely missing and the projectId is set as empty("") so the charts doesn't get populated as expected
Steps to Reproduce
- Setup an AI or normal gateway(self-hosted) along with analytics publishing
- Create an LLMProvider
- Invoke it in a way which results in an error during the request(Guardrail hit, request timeout,etc.)
- Wait till the event is published and go over to moesif side and look over the 2 charts specified above( It can be clearly observed that in the metadata also these 2 keys are missing)
Severity Level of the Issue
Severity/Major (Important functionality is broken. Should be prioritized. Doesn't need immediate attention)
Environment Details (with versions)
No response
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 locating the analytics event publishing path for the Gateway and the Moesif metadata construction. Reproduce an error from an AI or normal self-hosted gateway, then verify that errorType and projectId are present in the published event and that the corresponding Moesif charts populate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100