You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a tool is used that sends an event to the event mesh, the ob-api events are littered with calls to cloudwatch metrics. This allows our dashboards to show when a tool is failing and generally track successes and failures. Tools used by the agent that don't produce an event simply run and are never tracked my metrics.
Possible Solution
Make all tools send an event and make the event parse the event details, determine the success and failure status of the event and react accordingly by sending success/failure metrics. This way openbrain can operate locally without having to spread the resources needed for metrics from ob-api to openbrain.
Additional context
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Description
When a tool is used that sends an event to the event mesh, the ob-api events are littered with calls to cloudwatch metrics. This allows our dashboards to show when a tool is failing and generally track successes and failures. Tools used by the agent that don't produce an event simply run and are never tracked my metrics.
Possible Solution
Make all tools send an event and make the event parse the event details, determine the success and failure status of the event and react accordingly by sending success/failure metrics. This way openbrain can operate locally without having to spread the resources needed for metrics from ob-api to openbrain.
Additional context
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: