I am also under IA’s ignition, but subscribe to everything and deal with incoming data in a tag-change script that monitors these paths. Script effectively acts as a “bridge” between physical sensors and some pre-defined variables that get logged to data historian and have alarms configured.
I chose this path because many of my sensors have timed/supervisor message programmed (every 24hrs) and this way, the bridge hides this traffic from user/historian but still allows for proactive monitoring of sensor health (battery voltage, not-dead-yet, etc).
P.S. A killer feature for chirpstack would be some sort of framework for plugins. All my sensors are on intranet (not exposed to internet) which pretty much dooms me to having to encode configurations for sensors MANUALLY. That is, almost all vendors only support a website/console interface and from there one can perform configuration of sensors. I’ve seen very few exceptions - see https://neon-configurator.twtg.io. I salivate imagining something similar for ALL my sensors, even if I have to code it the first time 
BTW, some sensors (e.g., Laird) allow configuration of their sensors also using bluetooth - this has it’s place, but requires physical access to device (to press a button). They also allow same via downlinks, but encoding, again, is left as exercise to user.