Optimization of AutoAssignment Checks

[Sergey-G-dev]

Hi all,

in our organization we are using hawkBit to manage a large number of target devices (currently around 1,2 Million and the number is growing). We want to make sure that every time a new target device connects and registers, the latest firmware is provided to that device as quickly as possible. To achieve that, we run the AutoAssigment Checker with a time interval of 3 minutes. This behavior is not optimal for us, because, on one hand, the customer has to wait up to 3 minutes to get the update. On the other hand, having that many targets saved in the database and executing TargetFilterQueries every 3 minutes causes a constantly high database load. To improve this, we would like to schedule a regular AutoAssigment Check only once a day, but whenever a target uploads its attributes to hawkBit, the AutoAssigment Check would be triggered only for that one specific target.

So it would go like this: target pushes its "configData to hawkBit", hawkBit fetches the list of the TargetFilterQueries with assigned DistributionSet from the database, then tries to match the properties from the TFQ-string against the target's attributes. If it finds a match, then the corresponding DistributionSet would be assigned to that target.

So far I haven't found any way to match the TFQ directly against the JpaTarget's properties, without querying the database. One of the possible ways to do this would be to implement some kind of a matcher that would parse the TFQs and try to match it against the given JpaTarget. Do you think that would be feasible? Or would you recommend a different approach?

Thanks and best regards, Sergey

[KONGDejing]

I want to ask a question, If i want to install hawkbit , what the detailed steps are for the new gay. I search for the internet and find nothing about this.