Main function.

Forwards events to Blueflood

Forwards events to Boundary Premium.

Forwards riemann events to ClickHouse.

Forwards riemann events to Amazon CloudWatch

Utility functions. Time/date, some flow control constructs, protocol buffer definitions and codecs, some vector set ops, etc.

Riemann config files are eval’d in the context of this namespace. Includes streams, client, email, logging, and graphite; the common functions used in config. Provides a default core and functions ((tcp|udp)-server, streams, index, reinject) which operate on that core.

Binds together an index, servers, and streams.

Forward events to Datadog.

Riemann’s dependency resolution system expresses stateful relationships between events. Dependencies are expressed as Rules; a Rule is a statement about the relationship between a particular event and the current state of the index.

Forwards events to Druid

Forwards events to Elasticsearch.

Send email about events. Create a mailer with (mailer opts), then create streams which send email with (your-mailer “shodan@tau.ceti.five”). Or simply call email-event directly.

Many places in Riemann need to understand whether the events they’re working with are currently valid, and whether a given host/service combo has expired. The expiration tracker provides a stateful data structure for tracking new events, figuring out when expirations should be emitted, and calling back when they need to occur.

Functions for combining states.

Forwards events to Graphite.

Forwards events to HipChat

Maintains a stateful index of events by host, service key. Can be queried to return the most recent indexed events matching some expression. Can expire events which have exceeded their TTL. Presently the only implementation of the index protocol is backed by a nonblockinghashmap, but I plan to add an HSQLDB backend as well.

Forwards events to InfluxDB. Supports InfluxDB 0.9 or higher.

Forwards events to InfluxDB v2.

Tracks Riemann performance data

Receives events from and forwards events to Kafka.

Forwards events to KairosDB.

Forwards events to Keen IO

Forwards events to Librato Metrics.

Forwards events to Logentries.

Forwards events to LogStash.

Forwards events to Mailgun

Post alerts to Microsoft Teams

Forwards events to Nagios via NSCA

Forward events to Netuitive.

Forwards events to OpenTSDB.

Forwards events to OpsGenie

Forwards events to Pagerduty

Simple plugin loader for riemann.

A generic thread-safe resource pool.

Forwards riemann events to Prometheus Pushgateway.

Provides publish-subscribe handling of events. Publishers push events onto a channel, which has n subscribers. Each subscriber subscribes to a channel with an optional predicate function. Events which match the predicate are sent to the subscriber.

Forwards events to Pushover.

The query parser. Parses strings into ASTs, and converts ASTs to functions which match events.

Forwards events to RabbitMQ.

The riemann REPL server is a bit of a special case. Since it controls almost every aspect of Riemann–and can shut those aspects down–it needs to live above them. While you usually start a repl server from the config file, it is not bound to the usual config lifecycle and won’t be shut down or interrupted during config reload.

Lifecycle protocol for stateful services bound to a core.

Forwards events to Shinken.

Post alerts to slack.com

Publish to AWS SNS topic(s) about events. Create a publisher with (sns-publisher opts), then create streams which publish to topic(s) with (your-publisher “your::arn”). Or simply call sns-publish or sns-publish-async directly.

Forwards events to Stackdriver.

The streams namespace aims to provide a comprehensive set of widely applicable, combinable tools for building more complex streams.

Riemann streams have performed exceptionally well, but their design scope was intentionally limited. Users consistently request:

Send events to Telegram

Fast, end-to-end, repeatable testing for entire Riemann configs. Provides a tap macro which taps the event stream and (in testing mode) records all events that flow through that stream. Provides a variant of deftest that initiates controlled time and sets up a fresh result set for taps, and a function inject! to apply events to streams and see what each tap received.

Clocks and scheduled tasks. Provides functions for getting the current time and running functions (Tasks) at specific times and periods. Includes a threadpool for task execution, controlled by (start!) and (stop!).

Provides controllable periodic and deferred execution. Calling (advance! delta-in-seconds) moves the clock forward, triggering events that would have occurred, in sequence.

Functions used in several transports. Some netty parts transpire here since netty is the preferred method of providing transports

It is very dark. You are likely to be eaten a grue.

Consumes messages from RabbitMQ. Associated with a core. Sends events to the core’s streams, queries the core’s index for states.

Exposes subscriptions to the index as server sent event channels

Accepts messages from external sources. Associated with a core. Sends incoming events to the core’s streams, queries the core’s index for states.

Accepts messages from external sources. Associated with a core. Sends incoming events to the core’s streams, queries the core’s index for states.

Accepts messages from external sources. Associated with a core. Sends incoming events to the core’s streams, queries the core’s index for states.

Forwards events to Twilio

Forwards events to VictorOps

Forwards events to Xymon

Forwards events to Zabbix