Flows adapters don't start on Sentinel running as a container.

Description

Until Horizon 29, Sentinel as a container ran perfectly fine with flows enabled, configuring as described in the official documentation. Starting with Horizon 30, something is missing preventing the flow adapters from starting.

After some research and testing, based on the missing class from the errors I got, I found that adding the sentinel-timeseries-api feature to featuresBoot.d solves the problem on Horizon 31.

Interestingly, it was since Horizon 30 that the base image changed from centos to ubuntu, among other changes that could lead to missing some required dependencies.

I suspect this problem might exist on a bare-metal installation on Ubuntu/Debian, but I haven’t had time to verify it.

Environment

According to the documentation, run Sentinel via Docker Compose or Kubernetes with Flows Processing enabled.

Acceptance / Success Criteria

None

Activity

Show:

Benjamin Reed January 10, 2023 at 2:01 PM
Edited

Merged to foundation-2023

Fixed

Details

Assignee

Reporter

Components

Sprint

Affects versions

Priority

PagerDuty

Created December 16, 2022 at 2:41 PM
Updated January 10, 2023 at 2:01 PM
Resolved January 10, 2023 at 2:01 PM

Flag notifications