Update main.go

[nosmicek]

this PR does 2 things:

1. renames XMPP_USER and XMPP_PW env variables into PROMEXP_AUTH_USER and PROMEXP_AUTH_PASSWORD (so it is more compliant with jitsi naming standards) - we use k8s deployment and this collides with other things
2. solves compilation problems with new versions of FluuxIO/go-xmpp go xmpp library
   ./main.go:150:3: cannot use promoted field TransportConfiguration.Address in struct literal of type xmpp.Config
   ./main.go:152:3: unknown field 'Password' in struct literal of type xmpp.Config
   ./main.go:155:3: cannot use promoted field TransportConfiguration.TLSConfig in struct literal of type xmpp.Config
   ./main.go:264:31: not enough arguments in call to xmpp.NewClient
   have (xmpp.Config, *xmpp.Router)
   want (xmpp.Config, *xmpp.Router, func(error))

this patch doesnt update any documentation

[Kroev]

ok thank you, let me check this

[nosmicek]

i have updated PR with my latest findings with latest version of fluuxIO xmpp library, see commit message.

[nosmicek]

also good to point out, maybe in readme.md, that for jitsi prom exp to work there is necessary to have tls module enabled in prosody. we had it disabled for some reason (certificate errors), and the jitsi prom exp could not authorize to prosody due to "starttls" handshake error with prosody. it took me some time to understand the problem and enable the tls module (we are running the whole jitsi in kubernetes cluster so its a little bit more complicated).

ty for the work.

[msolters]

Hi @nosmicek , thanks for this PR. unfortunately there's yet another compilation fix that I guess was recently introduced due to upstream?
Regardless, our exporters are not receiving any presences despite connecting to the XMPP server. Was there some other configuration you had to do to your MUCs in prosody's config for this exporter to work for you? I see the JVBs publishing presences but the exporter receives nothing.

[nosmicek]

@msolters can you specify what compilation fix do you mean? according to docker i compiled two days ago with this patch against upstream, but i might want to check that..

what do you mean by exporters (in plural) not receiving any presence? we have only one exporter and that should be enough for whole setup - it works this way on our setup pretty flawlessly.

basic things to check:

• user created in prosody
• tls enabled in prosody global config
• colibri statistics enabled in jvb
• some env variables need to be set, i would esp. check if JVB_BREWERY_MUC is the same in exporter config and in jitsi env variables for your situation, but that's just a hinch (i think both defaults to other values if not set)

what do you see in logs? i had to enable debug logs in prosody to see communication here and then in jvb, that was pretty much all i had to debug.

[nosmicek]

@msolters check if my latest update doesn't help u fix your build problems.