1. InfluxDB follows time-series data method. Two types of time seried data.
Regular – data that is sampled at regular intervals. For example every second, or every hour.
Irregular – for example, data that is only recorded when an event occurs, which might happen frequently, but always at completely random times.
2. The InfluxData Platform is the first purpose-built, end-to-end solution for collecting, storing, visualizing and alerting on time-series data at scale. Based on the TICK stack, all of the components of the platform are designed to work together seamlessly.
3. What’s the TICK stack? It’s our vision for a complete data platform to manage time-series data.
Telegraf - Collect time series data from a variety of sources
InfluxDB - Deliver high performances writes and efficiently stores time series data.
Chronograf - visualizes and graph the time series data stored in influxDB.
Kapacitor - Provides alerting, ETL and detects anomalies in time series data.
4. Telegraf:
Telegraf is an open source agent written in Go for collecting metrics and data on the system it’s running on or from other services. Telegraf then writes the data to InfluxDB in the correct format.
Key features include:
MIT License
Minimal memory footprint
Extensible plugin design with 40+ input and output plugins
Support for datasources like MongoDB, MySQL and Redis
Messaging systems like Apache Kafka and RabbitMQ
Third party APIs like Mailchimp, AWS CloudWatch and Google Analytics
Collect system metrics like CPU, Memory, I/O, etc
5. InfluxDB:
InfluxDB is an open source database written in Go specifically to handle time series data with high availability and performance requirements. InfluxDB installs in minutes without external dependencies, yet is flexible and scalable enough for complex deployments.
Key features include:
MIT License
Simple to install, yet highly extensible
Purpose built for time series data, no special schema design or custom app logic required
Thousands of writes per second with the new TSM1 storage engine
Horizontal clustering for high availability in active development
A native HTTP API means no server side code to manage
Time centric functions and an easy to use SQL-like query language
Data can be tagged, allowing very flexible querying
Answer queries in realtime with every data point indexed as it comes in and immediately available in less than 100ms
6. Chronograf:
Chronograf is a single binary web application that you can deploy behind your firewall to do ad hoc exploration of your time series data in InfluxDB. It includes a library of intelligent, pre-configured dashboards for common data sets.
Key features include:
Simple installation and configuration
Tight integration with InfluxDB makes getting connected to data easy
Support for ad-hoc visualizations
Smart query builder designed to work with large datasets
Collect multiple graphs into dashboards
Templating, new graph types and visualizations coming!
7. Kapacitor:
Kapacitor is an alerting and data processing engine for time series data. It lets you define your own custom pipeline to aggregate, select, transform or otherwise process data and then store it back in InfluxDB or trigger an event.
Key features include:
Stream data from InfluxDB or query from InfluxDB
Trigger events/alerts based on complex or dynamic criteria
Perform any transformation currently possible in InfluxQL, for example: SUM, MIN, MAX, etc.
Store transformed data back into InfluxDB
Process historical data, for example: backfill data using a processing pipeline
Note:
TCP port 8083 is used for InfluxDB’s Admin panel
TCP port 8086 is used for client-server communication over InfluxDB’s HTTP API
TCP ports 8088 and 8091 are required for clustered InfluxDB instances
Default file for influxdb: /etc/influxdb/influxdb.conf
Source: https://docs.influxdata.com/influxdb/v0.13/introduction/getting_started/
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon