when For example: 1. 2017-08-08T13:24:03, someone reqeust /featured- genres/back-end 2. 2017-08-08T13:24:35, we deploy new version for cmx-api 3. 2017-08-08T13:24:42, memory usage is 250.2MB
Log can record resources usage in specific time point. We can build a whole picture if we collect enough data. API throughput: We can know the throughput by record every request. Where are these requests from, Information when some wrong happen: Save the request information, for instance: user agent, ip, query string ...
System resources usage, Services performance: Amazon CloudWatch, New Relic, Datadog API throughput, Where are these requests from: Google Analytics, Mixpanel, Amplitude Information when some wrong happen: Rollbar, Sentry
that ingests data from a multitude of sources simultaneously, transforms it, and then sends it to your favorite “stash.” 4 Log will ingest to Logstash first, and send to Elasticsearch after parse. 4 A lot built-in plugin to manipulate log.
is currently the best way in Logstash to parse unstructured log data into something structured and queryable. With 120 patterns built-in to Logstash, it’s more than likely you’ll find one that meets your needs! mutate: perform general transformations on event fields. You can rename, remove, replace, and modify fields in your events. drop: drop an event completely, for example, debug events. clone: make a copy of an event, possibly adding or removing fields. geoip: add information about geographical location of IP addresses (also displays amazing charts in Kibana!)
4 Schemaless 4 Build powerful query using ugly Elasticsearch DSL 4 Store logs in Elasticsearch 4 Store by date, all logs create in same data will store in same index
you create beautiful charts without build query yourself 4 Retrieve time series data, perform calculations to tease out the answers to complex questions