This document details how to install and administrate a cygnus-ngsi-ld agent.

cygnus-ngsi-ld is a connector in charge of persisting Orion context data in certain configured third-party storages, creating a historical view of such data. In other words, Orion only stores the last value regarding an entity's attribute, and if an older value is required then you will have to persist it in other storage, value by value, using cygnus-ngsi-ld.

cygnus-ngsi-ld uses the subscription/notification feature of Orion. A subscription is made in Orion on behalf of cygnus-ngsi-ld, detailing which entities we want to be notified when an update occurs on any of those entities attributes.

Internally, cygnus-ngsi-ld is based on Apache Flume, which is used through cygnus-common and which cygnus-ngsi-ld depends on. In fact, cygnus-ngsi-ld is a Flume agent, which is basically composed of a source in charge of receiving the data, a channel where the source puts the data once it has been transformed into a Flume event, and a sink, which takes Flume events from the channel in order to persist the data within its body into a third-party storage.

Current stable release is able to persist Orion context data in:

  • PostgreSQL, the well-know relational database manager.
  • PostGIS, a spatial database extender for PostgreSQL object-relational database.
  • CKAN, an Open Data platform.


Intended audience

This document is mainly addressed to those FIWARE users already using an Orion Context Broker instance and willing to create historical views from the context data managed by Orion. In that case, you will need this document in order to learn how to install and administrate cygnus-ngsi-ld.

If your aim is to create a new sink for cygnus-ngsi-ld, or expand it in some way, please refer to the User and Programmer Guide.


Structure of the document

Apart from this introduction, this Installation and Administration Guide mainly contains sections about installing, configuring, running and testing cygnus-ngsi-ld. The FIWARE user will also find useful information regarding multitenancy or performance tips. In addition, sanity check procedures (useful to know wether the installation was successful or not) and diagnosis procedures (a set of tips aiming to help when an issue arises) are provided as well.