New
- DashboardA new first tab draws the server as a scheme: endpoints on the left, protocols with their templates in the middle, upstreams on the right, and boxes for logs, runtime data, datasets and callbacks. Every box charts its traffic live over the last 1, 5 or 15 minutes, with one cursor across all charts. Hover a protocol to light up its endpoints and upstreams, click it to show it alone, and switch on Active only to hide whatever had no traffic.
- Templates on the DashboardA protocol’s row lists its templates with their matches per second. An Unmatched row appears while requests go unanswered, and opens them in Traffic logs.
- Routing tabLists the endpoints, from the application port to those configured under
fantasticmock.protocols.instances, and the upstreams, each with its protocol. New adds an upstream, and each one opens its editor for matchers, replacements and custom fields.
- Templates choose their endpointsEndpoints this template answers on in the editor (
settings.endpoints) limits a template to some endpoints of its protocol; with none it answers on all of them. HTTP traffic logs name the endpoint a request came to.
- Similar templatesTemplate generation asks what becomes of a template that existing ones already cover: Keep existing, Replace or Keep both. The filter button in the editor toolbar lists the templates with the same routing and matchers as the open one.
- Threads and limitsThe runtime menu in the header and the Dashboard show the HTTP server’s busy threads against
server.jetty.threads.max, work waiting for a thread, callback senders busy and waiting, synchronous callbacks, failed callbacks per second and each endpoint’s in-flight limit. A chart at its limit turns red, and its ! names the setting to raise.
- Log entries per secondA chart of the traffic log entries written, in the runtime menu and on the Dashboard’s Logs box.
- Retry on mock or on proxyRight-click any Retry button to retry that log once on the mock or on the upstream, whatever Retry behavior says.
- Reset to application.ymlReset in the Settings heading puts every server setting back as
application.yml has it. Templates and traffic logs are kept. The Routing tab’s menu resets the upstreams alone.
- Forwarded headersA proxied HTTP log shows, beside what the client sent, the headers that reached the upstream after replacements and custom fields.
- Connection messages in one entryA Traffic navigation setting that lists the messages of one connection as a single entry with its message list: a callback’s connection, or a session of a protocol whose plugin declares session fields, such as a WebSocket session.
- Callbacks that wait for repliesA protocol plugin’s callback can wait for replies on its connection and keep it open with pings. Each message sent or received is its own traffic log entry. A request whose connection closes before its first response is logged as cancelled.
- Templates that answer nothingA protocol template with an empty response list counts as matched, runs its callbacks and is logged once without a response, for a message that needs no answer.
- More for protocol pluginsA field of
type: path offers request.<name>.segment<N>, which Fill to match also writes. Response and callback fields take a default, shown in the empty field, and a group heading. A field marked metadata: true shows under Details, and a template’s Routing block shows every routing key the plugin declares.
- Accept queue
fantasticmock.http.accept-queue-size sets how many new connections wait to be accepted on the application port, and accept-queue-size does the same for an HTTP endpoint.
Changed
- Generation keeps existing templatesBy default a generated template that an existing one covers is left out; 1.0.5 replaced the existing template. Choose Replace under Similar templates for the old behavior.
- Settings → Routing behaviorSettings keeps the routing mode, retry behavior and recording; the upstreams moved to the Routing tab. A browser with no retry choice of its own retries as the routing mode does.
- More work at once by defaultThe bundled
application.yml lets the HTTP server run 2,000 tasks at once (server.jetty.threads.max; 200 before) and sends 200 asynchronous callbacks at once, 200 per destination (64 and 16 before).
- DelaysEvery protocol reads delays the same way: a fixed delay wins over a random range, either bound of a range works alone, and a negative value counts as 0.
- Callback conditionsThe conditions of HTTP and Kafka callbacks match the same way as template matchers.
- Protocol APIStill version 5, so plugins built for 1.0.5 keep working. It adds thread reports for the Dashboard, callbacks that wait for replies, cancelled responses, and the endpoint of requests a plugin passes to the HTTP gateway. Compile against the 1.0.6 protocol API JAR.
Fixed
- Traffic logs under loadThe live traffic list keeps up with about 2,000 requests a second, where it used to fall behind.
- Many callbacks at onceA burst of protocol plugin callbacks on Java 21 could stop the server answering; it no longer does.
- Plugin HTTP listeners in the chartsRequests a plugin passes to the HTTP gateway, such as those of the Netty listener, count for its endpoint and protocol; they used to show 0 TPS.
- Unmatched Kafka messagesKafka messages no template answers are counted as unmatched.