-
Notifications
You must be signed in to change notification settings - Fork 186
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
Report destinations errors and status in the odigos ui #1079
Labels
Comments
@blumamir I am interested in working on this issue |
Thanks @ankur0904 let me know how it goes and if you have any questions or need assistance |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, users can add new destination and add configuration options for them.
If there is an issue with the configuration, for example if the endpoint is invalid, odigos auto-scaler component will log the error and will not show any indication in the UI.
This issue is to add indication for the destination. So if everything goes well, the destination should indicate it, and if there are errors, I want to have the error message so the user can fix it.
To do that, we will need:
Status
to the destination CRD here which should includeConditions
similar to the ones in actions.ModifyConfig
function, and write the error to the destination CRD or indicate success if there is no error. This should be applied here.After this step, the user can see any status and error in the CRD. The next step after this is done would be to report this data in the
frontent
code so it is accessible to odigos UI.The text was updated successfully, but these errors were encountered: