... | @@ -116,10 +116,22 @@ After that, we need to setup Jeager exporter to export the traces emitted by our |
... | @@ -116,10 +116,22 @@ After that, we need to setup Jeager exporter to export the traces emitted by our |
|
|
|
|
|
#### Deployment
|
|
#### Deployment
|
|
|
|
|
|
[This](https://www.jaegertracing.io/docs/1.40/operator/) guide shows us how to deploy the Jaeger operator to our k8s cluster. Jaeger consist of different parts, such as Collector, Agent, Query. There are 3 strategies to deploying Jaeger: AllInOne, production, and streaming. The AllInOne is the default strategy which will package all the compnents of Jeager into one image. It is the easiest strategy to sue and recommended for testing purposes. After applying the commands, we need to port-forward the Jaeger service and exposing port `16686`, which will allow us to access the Jager UI.
|
|
[This](https://www.jaegertracing.io/docs/1.40/operator/) guide shows us how to deploy the Jaeger operator to our k8s cluster. Jaeger consist of different parts, such as Collector, Agent, Query. There are 3 strategies to deploying Jaeger: AllInOne, production, and streaming. The AllInOne is the default strategy which will package all the components of Jeager into one image. It is the easiest strategy to sue and recommended for testing purposes. After applying the commands, we need to port-forward the Jaeger service and exposing port `16686`, which will allow us to access the Jager UI.
|
|
|
|
|
|
#### Preview
|
|
#### Preview
|
|
![image](uploads/98af747326f56e2b65a9edc14631dcbf/image.png)
|
|
![image](uploads/98af747326f56e2b65a9edc14631dcbf/image.png)
|
|
*Jaeger UI*
|
|
*Jaeger UI*
|
|
![image](uploads/91d0dd381d8a895d918ec689051a0eaf/image.png)
|
|
![image](uploads/91d0dd381d8a895d918ec689051a0eaf/image.png)
|
|
*Details of a trace* |
|
*Details of a trace*
|
|
\ No newline at end of file |
|
|
|
|
|
## Elastic Stack
|
|
|
|
|
|
|
|
Elastic stack (ELK stack) is a group of products from [Elastic](https://www.elastic.co) used to analyze, search and visualize data of any source. It consists of 4 components:
|
|
|
|
- **Elasticsearch** is a full text search engine written in Java
|
|
|
|
- **Logstash** is a log aggregator that collects, transforms and then ships logs to other services
|
|
|
|
- **Kibana** is a data visualization tool that works on top of Elasticsearch
|
|
|
|
- **Beats** are agents that collects various metrics and send them to other destinations such as Logstash. Some of the most commonly used Beats are Filebeat, Metricbeat or Packetbeat.
|
|
|
|
|
|
|
|
## Configuration
|
|
|
|
|
|
|
|
[Elastic Cloud on Kubernetes(ECK)](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-overview.html) is the recommended way of deploying Elastic stack on k8s. There are individual Helm charts for each component of the stack but these will be deprecated soon. We first create all the necessary CRDs(Custom Resource Definition) such as Beat, Kibana etc. and then install the elastic operator. By default this will be installed in the `elastic-system` namespace. |
|
|
|
\ No newline at end of file |