Skip to main content
Version: 2.19.3

Instrumentation

RailsEventStore ships with built-in instrumentation. You can build your own features, improve logging or implement tracing on top of it. It can also be the way to integrate with 3rd party services for like NewRelic RPM, Skylight or AppSignal.

Enabling instrumentation​

RubyEventStore​

The ruby_event_store gem is not integrated with any particular instrumenter implementation. We don't enforce this dependency. Only require such instrumenter to have the same API as ActiveSupport::Notifications. One can for example use standalone as-notifications gem.

Instrumentation is provided by repository, mapper and dispatcher decorators:

  • RubyEventStore::InstrumentedRepository
  • RubyEventStore::Mappers::InstrumentedMapper
  • RubyEventStore::InstrumentedDispatcher

In order to enable it, wrap the components you intend to instrument with corresponding decorators and instrumenter of your choice:

instrumenter = ActiveSupport::Notifications

RubyEventStore::Client.new(
repository: RubyEventStore::InstrumentedRepository.new(RubyEventStore::InMemoryRepository.new, instrumenter),
mapper: RubyEventStore::Mappers::InstrumentedMapper.new(RubyEventStore::Mappers::Default.new, instrumenter),
message_broker: RubyEventStore::Broker.new(
dispatcher: RubyEventStore::InstrumentedDispatcher.new(RubyEventStore::Dispatcher.new, instrumenter),
),
)

You can also instrument your own repository, mapper or dispatcher components the same way.

AggregateRoot​

The aggregate_root gem is not integrated with any particular instrumenter implementation — same as with ruby_event_store.

Instrumentation is provided by AggregateRoot::InstrumentedReposiory decorator. In order to enable instrumentation, wrap the aggregate root repository with its instrumented decorator and the instrumenter of your choice:

instrumenter = ActiveSupport::Notifications
repository = AggregateRoot::InstrumentedRepository.new(AggregateRoot::Repository.new(event_store), instrumenter)

RailsEventStore​

The rails_event_store gem is integrated with ActiveSupport::Notifications that ships with Rails. By default RailsEventStore::Client instance ships with already instrumented repository, mapper and a dispatcher.

You can start subscribing to the instrumentation hooks by now:

hook_name = "append_to_stream.repository.rails_event_store"

ActiveSupport::Notifications.subscribe(hook_name) do |name, start, finish, id, payload|
metric = ActiveSupport::Notifications::Event.new(name, start, finish, id, payload)
NewRelic::Agent.record_metric("Custom/RES/append_to_stream", metric.duration)
end

The aggregate root repository instrumentation is not enabled automaticly here. The event store is a dependency passed to aggregate root repository and has no control over it. You have to decorate this repository yourself.

Hooks and their payloads​

append_to_stream.repository.rails_event_store​

KeyValue
:eventsAn array of appended RubyEventStore::Record objects
:streamA RubyEventStore::Stream that we append events to
{
events: [#<RubyEventStore::Record:0x0000000104b51f30>],
stream: #<RubyEventStore::Stream:0x0000000106cbf578>
}
KeyValue
:event_idsAn array of linked event identifiers
:streamA RubyEventStore::Stream that we link events to
{
event_ids: ["71c38b38-4c72-4f95-86e2-203898f98c8e",
"82dcf1eb-ec4e-48c6-b061-de7ce03fb6af"],
stream: #<RubyEventStore::Stream:0x0000000106cbf578>
}

delete_stream.repository.rails_event_store​

KeyValue
:streamA RubyEventStore::Stream that we delete
{
stream: #<RubyEventStore::Stream:0x0000000106cbf578>
}

read.repository.rails_event_store​

KeyValue
:specificationA RubyEventStore::SpecificationResult describing the query requested from event store
{
specification: #<RubyEventStore::SpecificationResult:0x0000000113644d80>
}

count.repository.rails_event_store​

KeyValue
:specificationA RubyEventStore::SpecificationResult describing the query requested from event store
{
specification: #<RubyEventStore::SpecificationResult:0x0000000113644d80>
}

update_messages.repository.rails_event_store​

KeyValue
:messagesAn array of RubyEventStore::Record objects to replace existing ones of the same identifiers
{
messages: [#<RubyEventStore::Record:0x0000000109e4ff98]
}

streams_of.repository.rails_event_store​

KeyValue
:event_idAn identifier of the event used to query for streams it is present in
{ event_id: "8cee1139-4f96-483a-a175-2b947283c3c7" }

call.dispatcher.rails_event_store​

KeyValue
:eventAn event instance which is being dispatched
:subscriberA subscriber to which event is dispatched to
{
event: #<MyEvent:0x000000010e786658>,
subscriber: #<Proc:0x00000001123ecb10>
}

serialize.mapper.rails_event_store​

KeyValue
:domain_eventAn event instance which is being mapped into RubyEventStore::Record
{
domain_event: #<MyEvent:0x000000010e786658>
}

deserialize.mapper.rails_event_store​

KeyValue
:recordAn instance of RubyEventStore::Record which is being mapped into an event
{
record: #<RubyEventStore::Record:0x0000000104b51f30>
}

load.repository.aggregate_root​

KeyValue
:aggregateAn instance of an aggregate on which loaded events are being applied
:streamA stream name to load events from
{
aggregate: #<Order:0x00000001141f97c0>,
stream: "Order$42"
}

store.repository.aggregate_root​

KeyValue
:aggregateAn instance of an aggregate whose events are being stored
:streamA stream name to which events are stored
:versionAn expected version of the stream to which events are stored
:stored_eventsAn array of events that are stored as a result of actions performed on this aggregate
{
aggregate: #<Order:0x00000001141f97c0>,
stream: "Order$42",
version: -1,
stored_events: [
#<Orders::Events::OrderCreated:0x000000011428a950>,
#<Orders::Events::OrderExpired:0x000000011428a2c0>
]
}