🚀 cost-insights: Better error handling for getCatalogEntityDailyCost method

[Chris-Lee-Ca]

Workspace

cost-insights

🔖 Feature description

Our company is currently implementing the Cost Insights plugin using the AWS Labs solution: AWS Cost Insights Plugin. This solution relies on annotations in components to filter cost data from AWS.

It is believed that using annotations is also a methodology for most solutions, but we have encountered an issue:

• If a component is missing the required annotation (or is not supposed to have one), the current implementation only returns a generic 500 Internal Server Error.
• This makes troubleshooting difficult, as there is no clear indication of what went wrong.

This problem cannot be resolved at the implementation layer, it requires changes to the cost-insights plugin. It would be beneficial if the plugin could provide more meaningful error messages to the user. This enhancement would improve usability and make troubleshooting easier.

🎤 Context

Instead of a 500 error, the plugin should support to return a descriptive error message explaining that any error have occured in the backend.

In my case, for the missing annotation, the most ideal outcome would be to display an instruction similar to what TechDocs does:

✌️ Possible Implementation

No response

👀 Have you spent some time to check if this feature request has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

None

[Chris-Lee-Ca]

The original issue I raised in the AWS Labs repo: awslabs/backstage-plugins-for-aws#325

[awanlin]

Thanks @Chris-Lee-Ca, added the help wanted tag and happy to see contributions for this! 🚀