The Dashboard is now enhanced to provide a more useful and intuitive selection of information regarding integration flows, executions, and errors. Specifically:
Flows page with filtered ordinary flowsFlows page with filtered real-time flowsClicking the workspace name in the Workspace Memory Usage list on the Current Month Quota page will now redirect the user to the corresponding workspace’s Dashboard.

4.0.1In a new Sailor version we have replaced jakarta.json with org.eclipse.parsson.
LOOKOUT_PROCESS_DATA env varLOOKOUT_PROCESS_DATA was introduced to disable Runlog for the dashboard. After redesigning the Dashboard page, this env var does not do anything on the frontend, since runlog is not on the new dashboard.
We’ve removed this env var from the frontend completely, and removed it from lookout by making it run as if this env var is set to “false”.
The search function is now more user-friendly as it now accepts partial matches (e.g. “test.123” log line previously would match only if a user searched for exact “test.123”, but now both “test” and “123” will match the logline).
Also, we’ve fixed the bug where irrelevant search results appeared due to incorrect configuration of Elasticsearch.
How to apply new changes to the mapping:
Check if the custom mapping template is already installed
Send GET http://{ELASTICSEARCH_IP}:9200/_template/exec-custom-mapping
If exec-custom-mapping template already exists
If this template includes some additional configuration and mapping - you should include it in the request body as well and then send PUT request
If exec-custom-mapping template does not exist
Simply send PUT request
The request for adding or updating the template
PUT http://:9200/_template/exec-custom-mapping
{
"order": 0,
"index_patterns": [
"exec_*"
],
"mappings": {
"properties": {
"msg": {
"analyzer": "simple",
"type": "text"
}
}
}
}
After the mapping template is updated, Graylog indices need to be updated as well. The best way is to just wait until they are rotated by Graylog itself (with the default config it should be 15 days). To check that the oldest index has correct mapping - send
GET http://:9200/exec_602(instead ofexec_602put the oldest index from exec index set in Graylog) and find a mapping for msg filed - it should have type and analyzer from the updated custom mapping template.
Create Branch, Create Default Branch and Continue in the view flow mode for Content-Based Router.1.0.0Make Raw Request actionUpsert Object actionLookup Object (at most one) actionLookup Objects (plural) actionDelete Object by ID action2.0.0Send Mail2.0.7batching-library functionality implemented as an internal client1.5.21.5.12ObjectId in following actions:
Lookup By Unique CriteriaUpdate ManyUpsert By Unique Criteria1.0.32.7.1Number of retries and Max number of calls per second from credentials configuration1.0.64.0.12.5.74.0.11.0.74.0.1