squakez commented on issue #5528:
URL: https://github.com/apache/camel-k/issues/5528#issuecomment-2134886434
This is not really a bug. Let's observe how the Kamelet is designed:
```
template:
from:
parameters:
period: '{{period}}'
steps:
- to: https://random-data-api.com/api/beer/random_beer/fail
- to: kamelet:sink
uri: timer:beer
```
Every given time, the kamelet emit an exchange reading to the API. The fact
the API is failing is not a hard failure by the component used. You can have a
deeper look at the [Camel Http component
documentation](https://camel.apache.org/components/4.4.x/http-component.html#_response_code).
As you can see, it is in fact reported as a "Warning". And, to a certain
extent it makes sense, as the http component can fail for any networking
reason. If you want to make it a stricter one, you probably need to develop the
logic by checking the http codes and working with `circuit-breaker` eips or
leveraging [Pipes error
handler](https://github.com/apache/camel-k-examples/tree/main/generic-examples/kamelets/error-handler).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
