for some reason this new tag layout (validated wit...
# umh-supportd
Diederik
09/21/2024, 12:43 PMfor some reason this new tag layout (validated with the validator) does not get into UMH
Diederik
09/23/2024, 7:34 AM@Jermuk could you take a look here as well? i think this is a bug (wild guess?)
some tags do not get recognized after the new benthos tag layout (whichs works on the validator)
j
Jermuk
09/23/2024, 7:37 AMyes, @Ferdinand will look into it
f
Ferdinand
09/23/2024, 8:51 AMchecking
Ferdinand
09/23/2024, 5:06 PM@Diederik Yes, this is a bug.
I checked it against our benthos based mqtt-kafka & kafka-postgresql bridges, and it does not happen to them anymore.
Ill check tomorrow if i can fix it on the old bridges.
d
Diederik
09/23/2024, 9:58 PMWait, that does not make sense
Diederik
09/23/2024, 9:58 PMI'm on the latest version
Diederik
09/23/2024, 10:17 PMor like in the dev/accp versions? :p
j
Jermuk
09/24/2024, 6:36 AM@Ferdinand has been spending most of his time when he is not bug fixing rewriting the bridges using benthos and making them available as custom data flow components as templates. The goal is to move everything to benthos so that we only need to write management and monitoring once, and then can apply it to everything else. This is what he is referring to new.
We check if we can push an update , or if it’s not better to upgrade fully. As you are only using _historian, it could make sense to upgrade instead. The new bridges are already running in production for a couple of weeks now at our customers without issues.
d
Diederik
09/24/2024, 6:51 AMahhhhh i didnt know! So if i understand correctly the bridges (cointainers) doing the work between MQTT => Kafka => TimescaleDB are actually also benthos'es? ("Redpanda connect")
j
Jermuk
09/24/2024, 6:54 AMIn the future, yes. And in the future they will only work for _historian by default and for everything else one needs to configure them manually
d
Diederik
09/24/2024, 6:58 AMhmmmm interesting! We will see it in the roadmap updates soon then! 😄