01
Java SDK based connector
The connector is built on the Mule Java SDK and ships as a standard module that drops into existing Mule applications.
FlorenceNext module
API health checks for the whole layer
A Java SDK module that monitors APIs in API-led connectivity layers and alerts on anomalies.
01 / Overview
The API health check is a monitoring technique implemented in microservices. It offers a means to verify the operational status of the APIs.
The HealthCheck Connector is a Java SDK based connector. It acts as a diagnostic tool, promptly alerting users to any anomalies within the microservices architecture. It is designed to work within API-Led connectivity patterns, with early warning when downstream services start to degrade.
02 / Key features
02
API-Led connectivity awareness
The connector understands the System, Process and Experience layer model. An outage at the System layer is reflected as a degraded Experience layer in the result.
03
Multi-protocol monitoring
HTTP, JMS, AMQP and database connections are all supported as monitoring targets.
04
No additional connection configuration
Existing connector configurations in the Mule application are reused. There is nothing extra to set up to start monitoring a service.
03 / Use cases
- 01
Production heartbeat across an API-led estate
A continuous probe across every layer surfaces a degrading downstream system before the first user complaint.
- 02
Pre-release smoke tests
Running the connector in the release pipeline confirms that every dependency a new app needs is reachable before traffic moves to it.
- 03
Partner-API SLA tracking
Third-party APIs (payment gateways, identity providers, logistics services) are probed on the same cadence as internal services. SLA breaches are timestamped by your monitoring.
04 / Business outcomes
01
Faster detection of anomalies
Outages and latency regressions show up in the dashboard rather than the support inbox.
02
One monitoring module across applications
The same connector handles checks that would otherwise be spread across multiple point tools, each with its own configuration to maintain.
03
Reusable across engagements
The module ships with every integration project FlorenceNext delivers, so monitoring is in place from day one.
05 / Technical highlights
- Runtime
- Java SDK module
- Protocols probed
- HTTP, JMS, AMQP, JDBC
- Architecture
- Designed for MuleSoft API-Led Connectivity
- Setup
- No additional connection configuration required
Get in touchContact us
Need an accelerator we haven’t built yet?
These accelerators started as pieces of work for client projects. If your team is hitting a recurring problem on integration, identity or monitoring, get in touch. There is a good chance we have something half-built, or we can build it with you.