LogoLogo
  • KPN THINGS USER GUIDE
    • Introduction
    • Getting started
      • Registration and setup
      • Device simulator app
      • Connect devices
        • SIM cards
        • Supported devices and KPN Devices
        • SODAQ R412M
        • Smartrak
        • Marvin development board
        • LoPy5
        • Arduino MKR WAN 1300/1310
        • Arduin MKR NB 1500
    • All videos
    • Tutorials
      • Configure a flow
      • Connect a HTTPs destination
      • Create a simple IoT web applicationPage
      • Send instruction to LoRa DevicePage
      • Send your data to Azure SQL
      • Technical overview
        • Management data model
        • Uplink communication
        • Downlink communication
        • Location data
      • Accounts and projects
        • Customer accounts and users
        • Projects
        • Customer management
        • Cost overview and contract
    • Frequently asked
      • Multi Factor Authentication
  • GENERAL FUNCTIONS
    • Quick reference videos
    • APIs
  • THE PORTAL EXPLAINED
    • Things Manager
      • Devices
        • Bulk operations
      • Data
        • Device data graph
      • Connectivity
        • LoRa connectivity configuration
      • Bulk reports
    • Things Creator
    • Support
      • News
      • Release notes
      • Real-time status
      • Service reports
      • Documents
      • Support tickets
      • Invoices
      • Contact info
    • Shop
  • BUILDING BLOCKS
    • Devices
      • Sensors
        • KPN Conditionsensor CO2 II
        • KPN Conditionsensor CO2 III
        • KPN Conditionsensor CO2 III motionPage 1
        • KPN FillTag I
        • KPN FillTag II
        • 1M2M ED1608
        • Elsys ERS
        • Device Simulator (Mobile Phone app)
        • Generic Device (Internet connected)
        • Generic LoRa device (preset connectivity)
        • Generic LoRa device (programmable)
        • Generic M2M device
        • Generic M2M device (with Internet connection)
      • Trackers
        • KPN Global Tracker Autonomous
        • KPN Global Tracker Wired
        • KPN LocationTag I
        • KPN LocationTag II
        • KPN LocationTag II v2
        • KPN LocationTag II v2 Expert Mode
        • KPN LocationTag II v3
        • KPN LocationTag III (with GPS)
        • KPN LocationTag III (without GPS)
        • KPN LocationTag III v2
        • KPN LocationTag III v2 Buffer
        • KPN LocationTag III v3
        • KPN LocationTag III v4
        • KPN LocationTag V
        • KPN LocationTag VI
        • KPN LocationTag WS
        • Streamline LoRa
        • Streamline M2M
        • Viloc
      • Routers
      • Gateways
        • KPN FSK Basestation
      • Device SDK
    • Connectivity
      • Connecting LoRa devices
        • LoRa connectivity configuration
      • Connecting M2M devices
      • Connecting Internet devices
      • Connecting MQTT Devices
    • Data Processing
      • ThingsML and SenML
        • ThingsML
        • SenML
          • Understanding and Interpreting SenML Data
          • Changes in KPN SenML
      • Device Twin
      • Decoders and encoders
        • Common measurements list
        • Decoder migrations
        • DIY Decoder
          • DIY decoder scripts
      • Merger
      • Device data
      • Devices
    • Destinations
      • HTTPS destination
      • MQTT broker
      • Cumulocity IoT Platform
      • Azure Event Hubs
      • Azure IoT Hub
      • Test Endpoint
      • ThingsBoard
      • Datacake
      • AWS Lambda
      • Google Cloud Run functions
  • IOT LINE UP
    • Freemium
      • Test SIM cards
    • Explorer
    • Modular
    • Tailored
    • Terms and Conditions
Powered by GitBook

© 2024 KPN - All rights reserved.

On this page
  • Connect an Azure Event Hubs
  • Where to find the required configuration values in the Azure Portal?
  • Host name and Namespace
  • Event Hubs Instance / Event space name
  • What does the connection do?
  • Example for data debugging #1: Capture
  • Example for data debugging #2: Process data explorer (Query)

Was this helpful?

Export as PDF
  1. BUILDING BLOCKS
  2. Destinations

Azure Event Hubs

PreviousCumulocity IoT PlatformNextAzure IoT Hub

Last updated 3 months ago

Was this helpful?

Below instructions help you connecting your Azure Event Hubs to KPN Things.

Don't have an Azure Event Hubs yet? Head on over to the Microsoft documentation on Azure Event Hubs:

Connect an Azure Event Hubs

The following parameters are available to connect an Azure Event Hubs

Parameter

Description

Example value

name *

The name of the destination

My Event Hub

description *

Description of the destination

url *

URL of your Event Hubs Namespace

https://myhubs. servicebus.windows.net

nameSpaceName *

The name of your Event Hubs Namespace

myhubs

Event Hubs instance * (event space name)

The name of your Event Hubs Instance

myeventhub

Policy name (sasKeyName) *

SAS Policy name for key with claim "Manage"

myeventhubKey

sasKey *†

Primary key for used SAS Policy

d2llZGl0bGpc2dlaw==

*) required value †) secret value, write only, not returned by our systems

Where to find the required configuration values in the Azure Portal?

Host name and Namespace

Open the Overview page of your Event Hubs Namespace in your Azure Portal. You will find the host name of your namespace (#1 in the screenshot) and the Event Hubs Namespace (#2 in the screenshot) as highlighted in the screenshot below.

Can't see the Host name? In the Dutch user interface, it is not visible. Switch to English language to see the host name in the Overview page.

Now, use this value to make the following input values for the Azure Event Hubs destination configuration:

  • Host name: should be of the form https://X.servicebus.windows.net, so put https:// before your host name and you're done.

  • Event Hubs Namespace: should be the name of your namespace.

Event Hubs Instance / Event space name

Continue by clicking on Event Hubs under Entities in the left menu of your Namespace. Select the Event Hub Instance you would like to connect to. This opens the Overview page of your Event Hubs Instance. Here you will find the name of your Event Hubs Instance, also known as Event Space Name, as highlighted in the screenshot below:

  • SAS Policy name: #1 in the screenshot above highlights the SAS key name of a selected Policy.

  • SAS Primary key: #2 in the screenshot above highlights the SAS key of a selected Policy.

What does the connection do?

Example for data debugging #1: Capture

Example for data debugging #2: Process data explorer (Query)

You can use SQL-like queries to explore your Event Hub data in the Process data feature. In the screenshot below it is shown how raw LoRa payload can be found in the data explorer.

All IoT Data from devices linked to the destination is forwarded to the Event Hub in JSON format. Since the Azure Event Hubs in itself does not allow you to look into the data coming from KPN Things, we give two easy examples of how to debug IoT data landing in your Event Hub.

Using the , you can store incoming data in an Azure Storage Container. In the screenshot below it is shown how raw LoRa payload can be found in the avro files generated by the capture feature.

SenML
Capture feature of your Event Hub
LogoAzure Quickstart - Create an event hub using the Azure portal - Azure Event Hubsdocsmsft