Improve error classification for better observability

[imDarshanGK]

Summary: Errors are not consistently classified into client/server/provider categories.

• Context: Triage is slower when errors are not grouped meaningfully.
• Expected: Categorize errors to improve alerting and triage workflows.
• Suggested fix: Update exception handling middleware to attach categories and map to codes.
• Notes: Use categories in dashboards and alerting.

[Divyanshi-kumari]

Hi, I would like to work on this issue under GSSoC’26. Please assign this issue to me.

[rajprakhar07]

"Hi @imDarshanGK, I'm a GSSoC '26 contributor with Python and backend experience. I'd like to work on this issue. I'll update the exception handling middleware to consistently classify errors into client/server/provider categories, attach error codes, and make them usable in dashboards and alerting workflows. Can I get assigned?"

[Xenon010101]

Hi @imDarshanGK, I'd like to work on this.
Root cause: Error responses from backend services lack structured classification, making debugging and observability difficult.
Proposed fix: Add error classification middleware that catches, categorizes (validation/auth/rate-limit/internal), and enriches errors with standardized codes and context.
Estimated diff: ~3 files, ~80 lines
ETA: 2 hours. Can I take this?

[aayushprsingh]

Hi, I am a GSSoC 2026 contributor and would like to work on this. Please assign it to me!

Here's how I'm thinking of approaching this:
I will start by defining an enum in the exception package classifying errors into Client, Server, and Provider categories. Then, I'll update the custom exception handler middleware to map specific exceptions to their respective categories and error codes. Finally, I will add unit tests checking that responses contain the correct category details and ensure these are captured in the logging metadata.

[Sricharan106]

I would like to work on this issue. Could you please assign it to me?

[rajprakhar07]

Hi @imDarshanGK, I've raised the PR for this issue. Kindly check and merge it. PR: #941"