Andrew, I’ve been out of commission these past few days from wisdom teeth extraction... I asked Tracy and Samip to review it.. if you need anything else today or tomorrow reach out to them
Matt is also on vacation, he’ll be back this weekend
Hi .. I there any way to implement enterprise flogo mapper activity into docker flogo .. coz the docker flogo mapper activity is not able to take the inputs to map
Do we know how to subscribe a message from Solace Queue/Topic ? Tried with REST invoke get method but got only Queue/Topic properties but not body. Also verified with MQTT Topic Subscriber but I could not see any subscriber count on the topic... Any Pointers ??
@hari-kasetty Shouldn’t be difficult to write a trigger for PubSub+
Thanks Mark. Could you please give some reference to write a trigger for Subscribing message from Solace ?
@dhire05 I think coerce.toParams should do it. Also there’s no straightforward way to have enterprise contributions on OSS logo.
@hari-kasetty if you want to connect using the Mqtt protocol you can use the existing trigger that @jvanderl has written... if you want to connect using the native Solace protocols you’ll have to ask the Solace team to build a Go SDK
Hi team, I'm building a Prometheus Pusher activity and everything is working fine in local when I do the tests and so on, but when I use it inside my app, I'm getting these kind of errors
2019/06/08 22:36:03 proto: duplicate proto type registered: io.prometheus.client.Bucket 2019/06/08 22:36:03 proto: duplicate proto type registered: io.prometheus.client.Metric 2019/06/08 22:36:03 proto: duplicate proto type registered: io.prometheus.client.MetricFamily panic: proto: duplicate enum registered: io.prometheus.client.MetricType
I'm only importing the packages in my activity.go, nothing else...
@alexandrev There’s already a statsd activity that works with Prometheus and Grafana on the showcase that i wrote.
@retgits Thank you for your response. When connected using MQTT Protocol , I could not see any subscriber count on the topic and also messages are not flowing ... Do we need to check anything in MQTT or any specific settings. Any pointers please ..
@mmussett that a lot, but that requires an statd daemon running right? and then using Prometheus Exporter for statsd? Or am I missing something?
@alexandrev That sounds like a Golang issue ..... if you search for "proto: duplicate proto type registered" there are a number of hits that describe situation where there is some form of name collision with different packages ... my go skills arn't enough to help you any further....
@ayh20 yep, the problem seems to be a colission with the embedded Prometheyus integration in FE 2.6
I'll try in OSS and see if it is working fine there
@hari-kasetty What do you see if you turn on DEBUG ? Do you see connection information when Flogo connects to MQTT ? Have you tried emulating your connection details with a tool like MQTT.fx ? Have you tried a different MQTT server like Mosquitto to eliminate that the problem is with the server ? I've used MQTT quite a bit and the only issues i've ever had are due to me not getting the right url or topic name patterns
Hi all does anyone try to run flogo on espressif 32?
@ayh20 . Thank you so much Andy for your inputs. In Solace, I don't see any option to turn on DEBUG mode. I tried using MQTT.fx tool that is mentioned. Able to see Client ID in MQTT Sessions. But in the MQTT.fx console, "session present: false". Could you please let me know if I am missing something here.
@hari-kasetty i was thinking of DEBUG for the FLOGO_lOG_LEVEL ... what messages does the trigger generate when it tries to connect. If you can't get MQTT.fx to connect then i suspect that the problem is at the Solace end..... you need a Solace expert i guess