Ecotone Pulse (Service Dashboard)
Last updated
Last updated
Whenever message fails during asynchronous processing it will kept repeated till the moment it will succeed. However retry strategy with dead letter queue may be set up in order to retry message given amount of times and then move it to the storage for later review and manual retry.
This is where Ecotone Pulse kicks in, as instead of reviewing and replaying the message directly from the application's console, you may do it directly from the UI application. Besides you may connect multiple Ecotone's application to the Pulse Dashboard to have full overview of your whole system.
Ecotone Pulse provide way to control error messages for all your services from one place.
Enable Dead Letter in your service and Distributed Consumer with AMQP Module.
After this you may run docker image with Ecotone Pulse passing the configuration to your services and RabbitMQ connection.
Then run docker image with Ecotone Pulse passing environment variables:
Provide array of services with service name and database connection dsn.
The name in ServiceName from your Symfony/Laravel/Lite configuration.
This way Ecotone Pulse knows how to route messages to your Service.
DSN to your RabbitMQ instance, which services are connected with Distributed Consumer.
It's important to set up Amqp Distributed Consumer. This way Service starts to subscribe to messages coming from Ecotone Pulse.
In the dashboard you may check all the connected services. For quick overview, you will find amount of errors within given service there.
To review error messages go to specific service. From there you can review the error message, stacktrace and replay it or delete.
You may check demo application, where Symfony and Laravel services are connected to Ecotone pulse in demo application.
