Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

The Essentials

With Logsene, we expose the Elasticsearch API so you can:

When you use the API, here are the things you need to know:

  • host name:
  • port: 80 or 443 (depending on whether you want to use plain HTTP or HTTPS)
  • index name: your Logsene application token - note: this token should be kept secret (n.b. you can have N Logsene Apps, each with its own token)


With the same REST API, you can index logs directly from your application, or you can craft your own "log sender". 

If you are sending logs from your application use the Elasticsearch HTTP API. If you are sending logs from a Java application use a library like log4j2-elasticsearch-http or Jest instead of Elasticsearch TransportClient.

Besides specifying your Logsene app token as the index name, it's nice to have a field named "@timestamp".  Its value should be a valid ISO 8601 timestamp. This will be used for searching and sorting when/if you use Kibana with Logsene. If you don't provide a timestamp, Logsene will add one when it receives your message.

For example, you can send a log like this:

Code Block
NOW=`date "+%Y-%m-%dT%H:%M:%S"`
curl -XPOST$YOUR_TOKEN_HERE/mytype/ -d '
  "@timestamp": "'$NOW'",
  "message": "Hello World!"

This will index a simple "hello world" message to Logsene. That event would have the current timestamp and will go to your Logsene app (provided that the $YOUR_TOKEN_HERE variable contains your token), within a type named "mytype". The type is a logical division of events. Typically, you'd put events with different structures in different types. For example, syslog messages in a type called "syslog", apache logs in a type called "apache". Essentially, the type can be anything, it's the token of your application that has to match.

For performance reasons, we highly recommend using the Bulk API, because it allows you to send multiple events with a single request. For example, the following request sends three events:

Code Block
NOW=`date "+%Y-%m-%dT%H:%M:%S"`

echo '{ "index" : { "_index": "LOGSENE_APP_TOKEN_GOES_HERE", "_type" : "mytype" } }
{ "@timestamp": "'$NOW'", "severity_numeric" : 1 }
{ "index" : { "_index": "LOGSENE_APP_TOKEN_GOES_HERE", "_type" : "mytype" } }
{ "@timestamp": "'$NOW'", "message" : "hello again" }
{ "index" : { "_index": "LOGSENE_APP_TOKEN_GOES_HERE", "_type" : "mytype" } }
{ "@timestamp": "'$NOW'", "alternate_message": "fields can be added and removed at will" }' > req

curl -XPOST --data-binary @req; echo

Default Log Index Mapping

A mapping is a way to define how your logs are indexed - which fields are in each log event and how each field is indexed. Logsene provides a default mapping that works well for most use-cases:


Custom Log Index Mapping

If the default log index fields (also known as index mapping) don't fit your needs you can create completely custom index mapping. See Custom Logsene Mapping Template How-To.  Note that if you have N different log structures, the best way to handle that is by creating N Logsene Apps, each with its own index mapping.  For example, you may have web server logs, your system logs in /var/log/messages, and your custom application logs.  Each of these 3 types of logs has a different structure.  The web server logs probably use Apache Common Log format, the logs in /var/log/messages have syslog structure, and your own application's logs can be in any format your application happens to use.  To handle all 3 log formats elegantly simply create 3 separate Logsene Apps and use a different format for each of them.  See Custom Logsene Mapping Template How-To for details.