Runlog
has been removed from Dashboard
pageAs a part of our ongoing platform optimisation and extending its capability to withstand a high load, we have removed the Runlog and implemented a new “Containers” page that will display related information. This change does not reduce the amount of logging information available to you. Instead it increases the information available for error handling and debugging while increasing the efficiency of the platform.
Containers
PageWe implemented new menu Containers
under the Analyze section.
The new page Containers
will display information about containers and components inside.
The main page displays logs for “Today” by default, and users can extend the date range by the filtering and Search fields. The container logs save up to 30 days.
The Containers
page displays next States:
To open information for the particular container click on Step Name
. The single container page displays next information:
NOTE: Logs collected before this release won’t be present on Container Details page.
As we disabled the data messages processing in the lookout we created a new data source Clickhouse for Dashboard.
containers_id
We added new query parameter container_id
into GET v2/logs
endpoint.
We changed the helm env var RECIPES_FEATURE_DISABLED
to true
. It means that the Recipes are disabled for all contracts.
Before deploying, Tenant-Admin should update the feature flag for the necessary contracts with disableRecipeFeature: false
to continue using the Recipe feature.
See in API DOCS
{
"data": {
"type": "contract",
"id": "contract_id",
"attributes": {
"feature_flags": {
"disable_recipe_feature": false
}
}
}
}
Note: The Recipes are available to activate. Only create, edit and delete are resricted.
The Lookout does not process data/input messages to reduce the Mongodb load.
We introduced the new env var - LOOKOUT_PROCESS_DATA
(default: false
).
It controls whether the lookout consumes data
and input
non-retry messages.
The particular solution to fix an issue in CSS styles. With the next release, this section will be transferred to React.
Details of errors that occurred more than 30 days ago have been removed and are no longer accessible.
The amount of errors produced by this Flow exceeds error record limit. Older error records were deleted to persist the most recent ones.
2.0.0
1.2.3
Lookup
actions and Get New and Updated Objects Polling
trigger1.0.0
Make Raw Request
action1.2.0
Get New and Updated Objects Polling
trigger1.6.0
Webhook
trigger in favor of Hubspot webhook component
1.0.0
Webhook
trigger1.3.0
Jira Service Management Cloud
2.0.1
metaHeaders
and searchHeaders
Upsert Object
action did not save the search headers in MaesterDon't throw an error
when updating an object with TTL2.6.0
Don't emit on empty results
checkbox in Query
trigger1.4.0
attachments
inside message body for XML Attachment to JSON
action1.2.0
Duplicates behavior
optionFrom this table
to From this column
To this table
to To this column
1.0.4