Please note, a newer package is available: azeventhubs as of [2023-05-09]. We strongly encourage you to upgrade. See the Migration Guide for more details.
Azure Event Hubs is a highly scalable publish-subscribe service that can ingest millions of events per second and stream them into multiple applications. This lets you process and analyze the massive amounts of data produced by your connected devices and applications. Once Event Hubs has collected the data, you can retrieve, transform and store it by using any real-time analytics provider or with batching/storage adapters.
Refer to the online documentation to learn more about Event Hubs in general.
This library is a pure Golang implementation of Azure Event Hubs over AMQP.
If you want to use stable versions of the library, please use Go modules.
NOTE: versions prior to 3.0.0 depend on pack.ag/amqp which is no longer maintained. Any new code should not use versions prior to 3.0.0.
go get -u github.com/Azure/azure-event-hubs-go/v3
go get -u github.com/Azure/azure-event-hubs-go/v2
go get -u github.com/Azure/azure-event-hubs-go
In this section we'll cover some basics of the library to help you get started.
This library has two main dependencies, vcabbage/amqp and Azure AMQP Common. The former provides the AMQP protocol implementation and the latter provides some common authentication, persistence and request-response message flows.
Let's send and receive "hello, world!"
to all the partitions in an Event Hub.
package main
import (
"context"
"fmt"
"os"
"os/signal"
"time"
"github.com/Azure/azure-event-hubs-go/v3"
)
func main() {
connStr := "Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=superSecret1234=;EntityPath=hubName"
hub, err := eventhub.NewHubFromConnectionString(connStr)
if err != nil {
fmt.Println(err)
return
}
ctx, cancel := context.WithTimeout(context.Background(), 20*time.Second)
defer cancel()
// send a single message into a random partition
err = hub.Send(ctx, eventhub.NewEventFromString("hello, world!"))
if err != nil {
fmt.Println(err)
return
}
handler := func(c context.Context, event *eventhub.Event) error {
fmt.Println(string(event.Data))
return nil
}
// listen to each partition of the Event Hub
runtimeInfo, err := hub.GetRuntimeInformation(ctx)
if err != nil {
fmt.Println(err)
return
}
for _, partitionID := range runtimeInfo.PartitionIDs {
// Start receiving messages
//
// Receive blocks while attempting to connect to hub, then runs until listenerHandle.Close() is called
// <- listenerHandle.Done() signals listener has stopped
// listenerHandle.Err() provides the last error the receiver encountered
listenerHandle, err := hub.Receive(ctx, partitionID, handler)
if err != nil {
fmt.Println(err)
return
}
}
// Wait for a signal to quit:
signalChan := make(chan os.Signal, 1)
signal.Notify(signalChan, os.Interrupt, os.Kill)
<-signalChan
err = hub.Close(context.Background())
if err != nil {
fmt.Println(err)
}
}
In the above example, the Hub
instance was created using environment variables. Here is a list of environment
variables used in this project.
EVENTHUB_NAMESPACE
the namespace of the Event Hub instanceEVENTHUB_NAME
the name of the Event Hub instanceThere are two sets of environment variables which can produce a SAS TokenProvider 1) Expected Environment Variables:
EVENTHUB_KEY_NAME
the name of the Event Hub keyEVENTHUB_KEY_VALUE
the secret for the Event Hub key named in EVENTHUB_KEY_NAME
2) Expected Environment Variable:
EVENTHUB_CONNECTION_STRING
connection string from the Azure portal like: Endpoint=sb://foo.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=fluffypuppy;EntityPath=hubName
1) Client Credentials: attempt to authenticate with a Service Principal via
AZURE_TENANT_ID
the Azure Tenant IDAZURE_CLIENT_ID
the Azure Application IDAZURE_CLIENT_SECRET
a key / secret for the corresponding application
2) Client Certificate: attempt to authenticate with a Service Principal via AZURE_TENANT_ID
the Azure Tenant IDAZURE_CLIENT_ID
the Azure Application IDAZURE_CERTIFICATE_PATH
the path to the certificate fileAZURE_CERTIFICATE_PASSWORD
the password for the certificateThe Azure Environment used can be specified using the name of the Azure Environment set in "AZURE_ENVIRONMENT" var.
Event Hubs offers a couple different paths for authentication, shared access signatures (SAS) and Azure Active Directory (AAD)
JWT authentication. Both token types are available for use and are exposed through the TokenProvider
interface.
// TokenProvider abstracts the fetching of authentication tokens
TokenProvider interface {
GetToken(uri string) (*Token, error)
}
The SAS token provider uses the namespace of the Event Hub, the name of the "Shared access policy" key and the value of the key to produce a token.
You can create new Shared access policies through the Azure portal as shown below.
You can create a SAS token provider in a couple different ways. You can build one with a key name and key value like this.
provider := sas.TokenProviderWithKey("myKeyName", "myKeyValue")
Or, you can create a token provider from environment variables like this.
// TokenProviderWithEnvironmentVars creates a new SAS TokenProvider from environment variables
//
// There are two sets of environment variables which can produce a SAS TokenProvider
//
// 1) Expected Environment Variables:
// - "EVENTHUB_KEY_NAME" the name of the Event Hub key
// - "EVENTHUB_KEY_VALUE" the secret for the Event Hub key named in "EVENTHUB_KEY_NAME"
//
// 2) Expected Environment Variable:
// - "EVENTHUB_CONNECTION_STRING" connection string from the Azure portal
provider, err := sas.NewTokenProvider(sas.TokenProviderWithEnvironmentVars())
The AAD JWT token provider uses Azure Active Directory to authenticate the service and acquire a token (JWT) which is
used to authenticate with Event Hubs. The authenticated identity must have Contributor
role based authorization for
the Event Hub instance. This article
provides more information about this preview feature.
The easiest way to create a JWT token provider is via environment variables.
// 1. Client Credentials: attempt to authenticate with a Service Principal via "AZURE_TENANT_ID", "AZURE_CLIENT_ID" and
// "AZURE_CLIENT_SECRET"
//
// 2. Client Certificate: attempt to authenticate with a Service Principal via "AZURE_TENANT_ID", "AZURE_CLIENT_ID",
// "AZURE_CERTIFICATE_PATH" and "AZURE_CERTIFICATE_PASSWORD"
//
// 3. Managed Service Identity (MSI): attempt to authenticate via MSI
//
//
// The Azure Environment used can be specified using the name of the Azure Environment set in "AZURE_ENVIRONMENT" var.
provider, err := aad.NewJWTProvider(aad.JWTProviderWithEnvironmentVars())
You can also provide your own adal.ServicePrincipalToken
.
config := &aad.TokenProviderConfiguration{
ResourceURI: azure.PublicCloud.ResourceManagerEndpoint,
Env: &azure.PublicCloud,
}
spToken, err := config.NewServicePrincipalToken()
if err != nil {
// handle err
}
provider, err := aad.NewJWTProvider(aad.JWTProviderWithAADToken(aadToken))
The basics of messaging are sending and receiving messages. Here are the different ways you can do that.
By default, a Hub will send messages any of the load balanced partitions. Sometimes you want to send to only a particular partition. You can do this in two ways. 1) You can supply a partition key on an event
event := eventhub.NewEventFromString("foo")
event.PartitionKey = "bazz"
hub.Send(ctx, event) // send event to the partition ID to which partition key hashes
2) You can build a hub instance that will only send to one partition.
partitionID := "0"
hub, err := eventhub.NewHubFromEnvironment(eventhub.HubWithPartitionedSender(partitionID))
Sending a batch of messages is more efficient than sending a single message. SendBatch
takes an *EventBatchIterator
that will automatically create batches from a slice of *Event
.
import (
eventhub "github.com/Azure/azure-event-hubs-go/v3"
)
...
var events []*eventhub.Event
events = append(events, eventhub.NewEventFromString("one"))
events = append(events, eventhub.NewEventFromString("two"))
events = append(events, eventhub.NewEventFromString("three"))
err := client.SendBatch(ctx, eventhub.NewEventBatchIterator(events...))
By default, a Hub will retry sending messages forever if the errors that occur are retryable (for instance, network timeouts. You can control the number of retries using the HubWithSenderMaxRetryCount
option when constructing your Hub client. For instance, to limit the number of retries to 5:
// NOTE: you can use any 'NewHub*' method.
eventhub.NewHubFromConnectionString("<connection string>", eventhub.HubWithSenderMaxRetryCount(5))
When receiving messages from an Event Hub, you always need to specify the partition you'd like to receive from.
Hub.Receive
is a non-blocking call, which takes a message handler func and options. Since Event Hub is just a long
log of messages, you also have to tell it where to start from. By default, a receiver will start from the beginning
of the log, but there are options to help you specify your starting offset.
The Receive
func returns a handle to the running receiver and an error. If error is returned, the receiver was unable
to start. If error is nil, the receiver is running and can be stopped by calling Close
on the Hub
or the handle
returned.
handle, err := hub.Receive(ctx, partitionID, func(ctx context.Context, event *eventhub.Event) error {
// do stuff
})
handle, err := hub.Receive(ctx, partitionID, handler, eventhub.ReceiveWithLatestOffset())
handle, err := hub.Receive(ctx, partitionID, handler, eventhub.ReceiveWithStartingOffset(offset))
At some point, a receiver process is going to stop. You will likely want it to start back up at the spot that it stopped processing messages. This is where message offsets can be used to start from where you have left off.
The Hub
struct can be customized to use an persist.CheckpointPersister
. By default, a Hub
uses an in-memory
CheckpointPersister
, but accepts anything that implements the persist.CheckpointPersister
interface.
// CheckpointPersister provides persistence for the received offset for a given namespace, hub name, consumer group, partition Id and
// offset so that if a receiver where to be interrupted, it could resume after the last consumed event.
CheckpointPersister interface {
Write(namespace, name, consumerGroup, partitionID string, checkpoint Checkpoint) error
Read(namespace, name, consumerGroup, partitionID string) (Checkpoint, error)
}
For example, you could use the persist.FilePersister to save your checkpoints to a directory.
persister, err := persist.NewFilePersister(directoryPath)
if err != nil {
// handle err
}
hub, err := eventhub.NewHubFromEnvironment(eventhub.HubWithOffsetPersistence(persister))
The key to scale for Event Hubs is the idea of partitioned consumers. In contrast to the competing consumers pattern, the partitioned consumer pattern enables high scale by removing the contention bottleneck and facilitating end to end parallelism.
The Event Processor Host (EPH) is an intelligent consumer agent that simplifies the management of checkpointing, leasing, and parallel event readers. EPH is intended to be run across multiple processes and machines while load balancing message consumers. A message consumer in EPH will take a lease on a partition, begin processing messages and periodically write a check point to a persistent store. If at any time a new EPH process is added or lost, the remaining processors will balance the existing leases amongst the set of EPH processes.
The default implementation of partition leasing and check pointing is based on Azure Storage. Below is an example using EPH to start listening to all of the partitions of an Event Hub and print the messages received.
package main
import (
"context"
"fmt"
"os"
"os/signal"
"time"
"github.com/Azure/azure-amqp-common-go/v4/conn"
"github.com/Azure/azure-amqp-common-go/v4/sas"
"github.com/Azure/azure-event-hubs-go/v3"
"github.com/Azure/azure-event-hubs-go/v3/eph"
"github.com/Azure/azure-event-hubs-go/v3/storage"
"github.com/Azure/azure-storage-blob-go/azblob"
"github.com/Azure/go-autorest/autorest/azure"
)
func main() {
// Azure Storage account information
storageAccountName := "mystorageaccount"
storageAccountKey := "Zm9vCg=="
// Azure Storage container to store leases and checkpoints
storageContainerName := "ephcontainer"
// Azure Event Hub connection string
eventHubConnStr := "Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=superSecret1234=;EntityPath=hubName"
parsed, err := conn.ParsedConnectionFromStr(eventHubConnStr)
if err != nil {
// handle error
}
// create a new Azure Storage Leaser / Checkpointer
cred, err := azblob.NewSharedKeyCredential(storageAccountName, storageAccountKey)
if err != nil {
fmt.Println(err)
return
}
leaserCheckpointer, err := storage.NewStorageLeaserCheckpointer(cred, storageAccountName, storageContainerName, azure.PublicCloud)
if err != nil {
fmt.Println(err)
return
}
// SAS token provider for Azure Event Hubs
provider, err := sas.NewTokenProvider(sas.TokenProviderWithKey(parsed.KeyName, parsed.Key))
if err != nil {
fmt.Println(err)
return
}
ctx, cancel := context.WithTimeout(context.Background(), 20*time.Second)
defer cancel()
// create a new EPH processor
processor, err := eph.New(ctx, parsed.Namespace, parsed.HubName, provider, leaserCheckpointer, leaserCheckpointer)
if err != nil {
fmt.Println(err)
return
}
// register a message handler -- many can be registered
handlerID, err := processor.RegisterHandler(ctx,
func(c context.Context, e *eventhub.Event) error {
fmt.Println(string(e.Data))
return nil
})
if err != nil {
fmt.Println(err)
return
}
fmt.Printf("handler id: %q is running\n", handlerID)
// unregister a handler to stop that handler from receiving events
// processor.UnregisterHandler(ctx, handleID)
// start handling messages from all of the partitions balancing across multiple consumers
err = processor.StartNonBlocking(ctx)
if err != nil {
fmt.Println(err)
return
}
// Wait for a signal to quit:
signalChan := make(chan os.Signal, 1)
signal.Notify(signalChan, os.Interrupt, os.Kill)
<-signalChan
err = processor.Close(context.Background())
if err != nil {
fmt.Println(err)
return
}
}
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
See CONTRIBUTING.md.
To setup the integration test environment, ensure the following pre-requisites are in place
go get github.com/fzipp/gocyclo
go get -u golang.org/x/lint/golint
sudo apt install jq
sudo apt update
sudo apt install build-essential
az login
To run all tests run make test
To cleanup dev tools in go.mod
and go.sum
prior to check-in run make tidy
or go mode tidy
MIT, see LICENSE.