Akkapredefined visualizations and dashboards with mailbox size, routing time, errors count, actors, dispatchers, routers, time in mailbox, ...
Apachemonitor total network traffic, PHP FPM pool listen queues and processes, scoreboard available worker and connection Ops, request rates, memory, cpu, ...
Amazon Web ServicesEC2, EBS and ELB metrics, reads, writes, rejected requests, network in and out, consumed read/write ops, requests count, ...
ClickHousecurrent metrics, profile events, asynchronous metrics, part stats, replication & replica metrics, ...
Dockercontainer cpu, memory, count, swap, memory I/O Throughput, network traffic and errors, memory failed counter, ...
Elasticsearchrequest rate, indexing, JVM Pool size, latency, documents, nodes, cluster health, cache, thread pools, circut breakers, search, index stats, ...
JVMmax open files, used, deamon thread count, thread count, collection count / avg size / max time, ...
Kafkaconsumer lag, ISR, purgatory, active controllers, requests, topic bytes/messages, consumer request time, partitions, log cleaner, ...
Mysqlconnections, queries/questions rate, select rate, mysql traffic, cache usage, mysql trafffic, MyISAM key, InnoDB, table stats, ...
Nginxtotal requests, connections, serving connections, CPU, load, memory, I/O read/wriew, total network traffic, ...
Nginx Plusrequests, cache hits, server checks, status zones, caches, upstreams, CPU, IO read/write, disk space used, ...
Node.jsprocess memory, workers, event loop latency, garbage collection, CG released memory, response time, request rate, ...
Redisconnected clients, keyspace missses, command processes, expired keys, keyspace hits, evicted keys, used memory, connected slaves, ...
Hadoopmax open files, used, deamon thread count, thread count, collection count / avg size / max time / time, ...
Solrindex stats, request rate, added docs, JVM pool size, query result cache, doxument cache, filter cache, warmup, indexing, ...
Sparklast received delay, unprocessed batches, receivers, waiting batches, active jobs, driver memory used, all jobs, executors, cores free, write ops, ...
Stormsupervisors, topologies, slots, acked, failed, executed, tasks, emitted, transferred, acked, failed, ...
Tomcatbytes sent, error requests, max connections, poller thread count, current threads busy, queue size, pool size, rejected sessions, ...
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
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.
- 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
Cloud IaaS / PaaS¶
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.
- Email as default system notification hook
- Custom user defined WebHook
- Big Panda
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.