Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: display error mssg based on api error response for metric charts #2298

Merged
merged 8 commits into from
Jan 17, 2025

Conversation

adarsh0728
Copy link
Contributor

@adarsh0728 adarsh0728 commented Dec 19, 2024

If metrics API gives error response, push the error mssg to error indicator tooltip, otherwise (when err is null), display default message.
Currently we are displaying default message in all the cases. This PR change would add context for the user.

Signed-off-by: adarsh0728 <gooneriitk@gmail.com>
@adarsh0728
Copy link
Contributor Author

Screenshot 2024-12-19 at 8 55 39 PM Screenshot 2024-12-19 at 8 55 57 PM

Copy link

codecov bot commented Dec 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.61%. Comparing base (33b992b) to head (1ab5b21).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2298      +/-   ##
==========================================
- Coverage   67.67%   67.61%   -0.06%     
==========================================
  Files         351      351              
  Lines       45918    45918              
==========================================
- Hits        31074    31047      -27     
- Misses      13768    13793      +25     
- Partials     1076     1078       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@adarsh0728
Copy link
Contributor Author

@whynowy: does this PR makes sense? Only thing is error response from prom client may not be a proper formatted text. Otherwise, in my view, it gives more context about the error.

@whynowy
Copy link
Member

whynowy commented Dec 19, 2024

Shall we use the error on the right to display error message?

Screenshot 2024-12-19 at 10 02 57 AM

@adarsh0728
Copy link
Contributor Author

Shall we use the error on the right to display error message?

Screenshot 2024-12-19 at 10 02 57 AM

sure

@adarsh0728
Copy link
Contributor Author

Screenshot 2025-01-06 at 9 08 02 PM Screenshot 2025-01-06 at 9 08 14 PM Screenshot 2025-01-06 at 9 08 32 PM

@adarsh0728 adarsh0728 marked this pull request as ready for review January 6, 2025 17:04
@adarsh0728 adarsh0728 requested a review from veds-g January 6, 2025 17:04
@adarsh0728 adarsh0728 marked this pull request as draft January 10, 2025 07:00
Signed-off-by: adarsh0728 <gooneriitk@gmail.com>
@adarsh0728 adarsh0728 requested a review from veds-g January 15, 2025 14:28
@adarsh0728 adarsh0728 marked this pull request as ready for review January 15, 2025 14:30
@vigith vigith merged commit d73604e into numaproj:main Jan 17, 2025
24 checks passed
SaniyaKalamkar pushed a commit to SaniyaKalamkar/numaflow that referenced this pull request Jan 19, 2025
…ts (numaproj#2298)

Signed-off-by: adarsh0728 <gooneriitk@gmail.com>
@veds-g veds-g mentioned this pull request Feb 3, 2025
20 tasks
veds-g pushed a commit that referenced this pull request Feb 19, 2025
…ts (#2298)

Signed-off-by: adarsh0728 <gooneriitk@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants