Skip to content
#

broker

Here are 294 public repositories matching this topic...

matzuba
matzuba commented Aug 28, 2019

Environment

  • OS: RHEL 7.6
  • Erlang/OTP:
  • EMQ: 2.3.11

Description

I am using:

NIGINX --> Docker --> custom image with EMQ installed ( same host, SSL offload on nginx)

EMQ works and clients can connect but i see continous multiple crashes/proxy errors in the error.log

2019-08-27 12:12:31.287 [error] <0.11973.534> CRASH REPORT Process <0.11973.534> with 0 neighbou

ejabberd
nwf
nwf commented Apr 28, 2020

While disabling host-name verification can, indeed, be a security foot-gun, it's annoying that the only way to make mosquito_[ps]ub speak to my broker with a broker-specific certificate given as --cafile is a flag named --insecure with klaxons and gongs and marching ants around its documentation. Looking at the code, mosquitto__server_certificate_verify is careful to honor preverify_ok

msagent
msagent commented Dec 17, 2019

Hello.
Interested in the possibility of implementing the following functions for ACL MYSQL :

Add to Public and Subscribe ACL rules template variables %t (topic)
To implement the change of topics corrected in the section

example: Topic change on the fly

Public ACL

{

"pattern": "a/#",
....,
....,
....,
"modifiers": {

"topic": "%u/%t",
....,
....,
...

gdmoore
gdmoore commented Apr 8, 2020

Python 3.8, using Autobahn|Py 20.3.1, and Crossbar from crossbario/crossbar:pypy3-20.2.1

What I'm trying to do is have a pool of workers handling an endpoint with shared registration (roundrobin), and after a set number of invocations, a worker will unregister itself and exit so that a fresh process can take its' place.

Steps:

  • create two processes; each connects to Crossbar and registers
kafka-monitor

Xinfra Monitor monitors the availability of Kafka clusters by producing synthetic workloads using end-to-end pipelines to obtain derived vital statistics - E2E latency, service availability & message loss rate. It reassigns partition & trigger preferred leader election to ensure each broker acts as leader of at least 1 partition of monitor topic.

  • Updated Jun 9, 2020
  • Java
wexman
wexman commented Feb 12, 2020

I noticed that the "certificate weakening" TlsOptions like IgnoreCertificateChainErrors, IgnoreCertificateRevocationErrors, AllowUntrustedCertificates and CertificateValidationCallback have no effect when using web socket connections.

I understand this is because the underlying api (System.Net.WebSockets) does not support this (at least not in all target frameworks), but I think it should be no

lulf
lulf commented Mar 13, 2020

Description

A new CRD to manage monitoring aspects of EnMasse needs to be defined. The design should cover:

  • The schema of the Monitoring CRD
  • Cover monitoring of all EnMasse components - including IoT
  • Allow for configuring common as well as component-specific aspects
  • Cover metric monitoring, alerting and tracing
  • Define tasks for backlog

Design

Tasklist

Enu

Improve this page

Add a description, image, and links to the broker topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the broker topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.