Skip to content
share library_books



Sematext Monitoring supports dozens of different integrations.


Stored data is received through the Elasticsearch API and also through a variety of Syslog protocols.

Elasticsearch API which lets you:

  • send log events directly from your application, using any Elasticsearch library
  • send log events using a "log shipper" application such as Logstash, rsyslog, Apache Flume, Fluentd, or anything that can output to Elasticsearch
  • search for logs from your own application, or by configuring/adapting existing Elasticsearch UIs, such as Kibana
  • optionally define custom mappings for your log types, so you can tweak the way your logs are indexed

Syslog Protocols

We accept Syslog messages using any log shipper and any Syslog library, as long as they either contain a valid token or the source IP is authorized.


We accept Journald logs using the systemd-journal-remote package. Everything you need to do is point the systemd-journal-remote to send Journald logs to Sematext Logs.

Log Shippers

  • Logagent - cross platform, Smart and lightweight Log Parser and Log Shipper written in Node.js
  • rsyslog - easy to get started, very fast and very light on resources, docs are harder to navigate for beginners though.
  • Logstash - cross platform, very simple to set up, well documented, but a little heavy on resource usage
  • Filebeat - cross platform, much lighter on resource usage, requires a Logstash instance to aggregate logs
  • syslog-ng - very fast and very light on resources, good docs, available as both free and paid version
  • syslogd - quite old, light on resources, not very feature rich
  • Fluentd - cross platform, easy to get started, horizontally scalable, available as both free and paid version
  • NXLog - cross platform but mostly used on Windows, easy to get started, available as both free and paid version

Programming Languages

Operating Systems


Cloud IaaS / PaaS


For iOS apps use Sematext Logs for iOS library.


For Android apps use Sematext Logs for Android library.


If you're an EC2 user, you can log Sematext from your instances by setting up a log shipper like you would from any other physical or virtual machine.

AWS S3 (CloudTrail, Flow logs, ELB access logs, etc.)

If you have logs stored in S3, you can ship them to Sematext via this AWS Lambda function. This method also works for when you periodically upload logs to S3 buckets, like Amazon CloudTrail does.

AWS CloudWatch Logs

If you want to ship CloudWatch logs, you can use another AWS Lambda function. If logs are VPC flowlogs, the Lambda function will also parse them and add geoIP information on the source IP addresses.


All of the integrations require adding and configuring the Experience script. However, unlike static websites and SSR websites, single-page applications require one more configuration step to register route changes.

Notification Hooks


Multiple types of alert notifications can be triggered on metrics and on logs and sent to several 3rd party services. See Alerts for more info.

Register for free or Login into Sematext IT systems monitoring platform to get started and create your logs app. Upload your logs from all your servers to our centralized log management solution with Elasticsearch API and integrated Kibana, and experience the first true Hosted ELK Stack.

Recommendations for learning more about Sematext products and services:

  • Sematext Cloud integrations guide
  • Our website
  • For open-source integrations and other Sematext contribution to the open-source community, check our GitHub repositories.
  • or just talk to us using chat located in right bottom corner of any page, and one of our engineers will help you navigate Sematext waters.