NOTICE: Your download and use of Edge Hub beta firmware is subject to the terms and conditions of your Splunk Partner Agreement, the
Splunk General Terms, or the Splunk Beta Evaluation Agreement – Splunk IoT Edge Hub, as applicable to you.
Industry specific certifications for regional expansion
EU region shows interest in transportation certifications. APAC did have similar requests as well with interest in mining. In US process industry certifications have been brought up as improvement suggestions Class 1 Div 2
Containerize edge hub OS, such as the ingest, process, storage, message bus capabilities as micro-services. Opens up options for deployment flexibility of services, and run on kubernetes and commodity hardware.
Port Android SplunkMobile to run on the display of Edge Hub
Edge Hub has a beautiful display. However the tiles of sensor data are not directly useful for highly specialized people in a manufacturing environment. They neeed this data merged with other data in Splunk and brought to life with an equally beau...
Currently we are generating unique messages for each of opc ua data points as events, and metrics for others. There are also some repeats in how the units and other metadata is captured. Ideally some of this can be reduced by allowing the user to ...
Overall improvements in configuration workflow. Currently requires individual entry / configuration. Can we come up with a schema and an import mechanism to automate this process?
OPC UA data schema improvements for Splunk ingestion
OPC UA currently uses event index, this is not very optimum as most of the information acquired is metric based. Should we consider moving to metric indexes? If not can we provide some sort of optimization for how the event data is communicated so...
Because of timeout requirements we had to update the OPC UA to manually browse and individually add. We would like to see all Node IDs and let the partner configure which ones to select / maybe a way to import them as CSVs
MQTT doc indicates there is no need to include sensor type but the hub requires a name starting with ext_ and MQTT docs do not mention dimension rule options