updates
Before this deployment only user firebase errors were collected (e.g. errors that are related to a particular user). Now, we also collect global firebase errors, like those that may happen due to the overall system state and there is nothing about user that can be done to fix it.
Another update is for content insights dashboard, especially related to the cases when messages pool content is being updated. The issue was that the content insights were not synced with such updates, so the data was not accurate.
update
content insights fix
- manager API [before: 1.104.11.1][after: 1.105.2.0] deployment
- statistics listener [before: 1.19.2.0][after: 1.22.13.0] deployment
- manager observer [before: 1.99.1.3][after: 1.105.2.0] deployment
firebase errors
- directory responses [before: 1.75.1.1][after: 1.81.9.0] deployment
- events proxy [before: 1.14.0.0][after: 1.14.6.0] deployment
- go sender [before: 1.17.8.0][after: 1.18.2.0] deployment
- directory events API [before: 1.73.3.1][after: 1.81.9.0] deployment
supervisor & workflow agents
- supervisor starter [before: ][after: 1.1.23.0] deployment
- supervisor dispatcher [before: ][after: 1.1.23.0] deployment
- supervisor API [before: ][after: 1.1.23.0] deployment
- manager workflows [before: ][after: 1.105.2.0] deployment
- directory workflows [before: ][after: 1.81.9.0] deployment
- sso workflows [before: ][after: 1.36.8.1] deployment
additional steps
- clickhouse to be updated with the latest migrations
- check that new event is being populated in new firebase errors table
- to check new firebase errors container after the release
from apps.messages.container import MessageErrorsContainer
errors_container = MessageErrorsContainer()
print(errors_container.size)deployment render all [[templates/items/deployment]] where page = @page.name