Merge pull request #4029 from SigNoz/release/v0.34.2

Release/v0.34.2
This commit is contained in:
Prashant Shahi 2023-11-22 21:30:38 +05:30 committed by GitHub
commit bc72b5fcea
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
350 changed files with 2212 additions and 521 deletions

1
.github/CODEOWNERS vendored
View File

@ -4,6 +4,7 @@
* @ankitnayan
/frontend/ @palashgdev @YounixM
/frontend/src/container/MetricsApplication @srikanthccv
/deploy/ @prashant-shahi
/sample-apps/ @prashant-shahi
**/query-service/ @srikanthccv

View File

@ -146,7 +146,7 @@ services:
condition: on-failure
query-service:
image: signoz/query-service:0.34.1
image: signoz/query-service:0.34.2
command:
[
"-config=/root/config/prometheus.yml",
@ -186,7 +186,7 @@ services:
<<: *db-depend
frontend:
image: signoz/frontend:0.34.1
image: signoz/frontend:0.34.2
deploy:
restart_policy:
condition: on-failure

View File

@ -164,7 +164,7 @@ services:
# Notes for Maintainers/Contributors who will change Line Numbers of Frontend & Query-Section. Please Update Line Numbers in `./scripts/commentLinesForSetup.sh` & `./CONTRIBUTING.md`
query-service:
image: signoz/query-service:${DOCKER_TAG:-0.34.1}
image: signoz/query-service:${DOCKER_TAG:-0.34.2}
container_name: signoz-query-service
command:
[
@ -203,7 +203,7 @@ services:
<<: *db-depend
frontend:
image: signoz/frontend:${DOCKER_TAG:-0.34.1}
image: signoz/frontend:${DOCKER_TAG:-0.34.2}
container_name: signoz-frontend
restart: on-failure
depends_on:

View File

@ -114,8 +114,8 @@ export const databaseCallsAvgDuration = ({
const legendFormulas = ['Average Duration'];
const expressions = [FORMULA.DATABASE_CALLS_AVG_DURATION];
const aggregateOperators = [
MetricAggregateOperator.SUM,
MetricAggregateOperator.SUM,
MetricAggregateOperator.SUM_RATE,
MetricAggregateOperator.SUM_RATE,
];
const dataSource = DataSource.METRICS;

View File

@ -94,8 +94,8 @@ export const externalCallErrorPercent = ({
const additionalItems = [additionalItemsA, additionalItemsB];
const aggregateOperators = [
MetricAggregateOperator.SUM,
MetricAggregateOperator.SUM,
MetricAggregateOperator.SUM_RATE,
MetricAggregateOperator.SUM_RATE,
];
const legends = [legend, legend];
const dataSource = DataSource.METRICS;
@ -153,8 +153,8 @@ export const externalCallDuration = ({
const additionalItems = [additionalItemsA, additionalItemsA];
const legends = [legend, legend];
const aggregateOperators = [
MetricAggregateOperator.SUM,
MetricAggregateOperator.SUM,
MetricAggregateOperator.SUM_RATE,
MetricAggregateOperator.SUM_RATE,
];
const dataSource = DataSource.METRICS;
@ -251,8 +251,8 @@ export const externalCallDurationByAddress = ({
const additionalItems = [additionalItemsA, additionalItemsA];
const legends = [legend, legend];
const aggregateOperators = [
MetricAggregateOperator.SUM,
MetricAggregateOperator.SUM,
MetricAggregateOperator.SUM_RATE,
MetricAggregateOperator.SUM_RATE,
];
const dataSource = DataSource.METRICS;

View File

@ -1,14 +1,17 @@
### Install otel-collector in your Kubernetes infra
## Install otel-collector in your Kubernetes infra
&nbsp;
Add the SigNoz Helm Chart repository
```bash
helm repo add signoz https://charts.signoz.io
```
&nbsp;
If the chart is already present, update the chart to the latest using:
```bash
helm repo update
```
&nbsp;
Install the Kubernetes Infrastructure chart provided by SigNoz
```bash

View File

@ -1,7 +1,9 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your Go Application
After setting up the Otel collector agent, follow the steps below to instrument your Go Application
&nbsp;
&nbsp;
### Step 1: Install OpenTelemetry Dependencies
Dependencies related to OpenTelemetry exporter and SDK have to be installed first
Dependencies related to OpenTelemetry exporter and SDK have to be installed first.
Run the below commands after navigating to the application source folder:
```bash
@ -13,7 +15,9 @@ go get go.opentelemetry.io/otel \
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
```
**Note:** Note that we are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
**Note:** We are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
&nbsp;
&nbsp;
### Step 2: Declare environment variables for configuring OpenTelemetry
Declare the following global variables in **`main.go`** which we will use to configure OpenTelemetry:
@ -24,9 +28,10 @@ Declare the following global variables in **`main.go`** which we will use to con
insecure = os.Getenv("INSECURE_MODE")
)
```
&nbsp;
### Step 3: Instrument your Go application
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your `main.go` file.
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your **`main.go`** file.
```bash
@ -85,9 +90,10 @@ To configure your application to send data we will need a function to initialize
return exporter.Shutdown
}
```
&nbsp;
### Step 4: Initialise the tracer in `main.go`
Modify the main function to initialise the tracer in main.go. Initiate the tracer at the very beginning of our main function.
### Step 4: Initialise the tracer in **`main.go`**
Modify the main function to initialise the tracer in **`main.go`**. Initiate the tracer at the very beginning of our main function.
```bash
func main() {
cleanup := initTracer()
@ -96,9 +102,10 @@ func main() {
......
}
```
&nbsp;
### Step 5: Add the OpenTelemetry Gin middleware
Configure Gin to use the middleware by adding the following lines in `main.go`
Configure Gin to use the middleware by adding the following lines in **`main.go`**
```bash
import (
....

View File

@ -1,3 +1,5 @@
&nbsp;
To run your Go Gin application, use the below command :
```bash

View File

@ -1,6 +1,9 @@
After setting up the Otel collector agent, follow the steps below to instrument your Go Application
&nbsp;
&nbsp;
### Step 1: Install OpenTelemetry Dependencies
Dependencies related to OpenTelemetry exporter and SDK have to be installed first
Dependencies related to OpenTelemetry exporter and SDK have to be installed first.
Run the below commands after navigating to the application source folder:
```bash
@ -12,7 +15,9 @@ go get go.opentelemetry.io/otel \
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
```
**Note:** Note that we are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
**Note:** We are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
&nbsp;
&nbsp;
### Step 2: Declare environment variables for configuring OpenTelemetry
Declare the following global variables in **`main.go`** which we will use to configure OpenTelemetry:
@ -23,9 +28,10 @@ Declare the following global variables in **`main.go`** which we will use to con
insecure = os.Getenv("INSECURE_MODE")
)
```
&nbsp;
### Step 3: Instrument your Go application
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your `main.go` file.
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your **`main.go`** file.
```bash
@ -84,9 +90,10 @@ To configure your application to send data we will need a function to initialize
return exporter.Shutdown
}
```
&nbsp;
### Step 4: Initialise the tracer in `main.go`
Modify the main function to initialise the tracer in main.go. Initiate the tracer at the very beginning of our main function.
### Step 4: Initialise the tracer in **`main.go`**
Modify the main function to initialise the tracer in **`main.go`**. Initiate the tracer at the very beginning of our main function.
```bash
func main() {
cleanup := initTracer()
@ -95,9 +102,10 @@ func main() {
......
}
```
&nbsp;
### Step 5: Add the OpenTelemetry Gin middleware
Configure Gin to use the middleware by adding the following lines in `main.go`
Configure Gin to use the middleware by adding the following lines in **`main.go`**
```bash
import (
....

View File

@ -1,3 +1,4 @@
&nbsp;
To run your Go Gin application, use the below command :
```bash

View File

@ -1,16 +1,19 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_linux_amd64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_linux_amd64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
### Step 3: Create `config.yaml` in `otelcol-contrib` folder with the below content in it
```bash
receivers:
otlp:

View File

@ -1,7 +1,9 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your Go Application
After setting up the Otel collector agent, follow the steps below to instrument your Go Application
&nbsp;
&nbsp;
### Step 1: Install OpenTelemetry Dependencies
Dependencies related to OpenTelemetry exporter and SDK have to be installed first
Dependencies related to OpenTelemetry exporter and SDK have to be installed first.
Run the below commands after navigating to the application source folder:
```bash
@ -13,7 +15,9 @@ go get go.opentelemetry.io/otel \
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
```
**Note:** Note that we are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
**Note:** We are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
&nbsp;
&nbsp;
### Step 2: Declare environment variables for configuring OpenTelemetry
Declare the following global variables in **`main.go`** which we will use to configure OpenTelemetry:
@ -24,9 +28,10 @@ Declare the following global variables in **`main.go`** which we will use to con
insecure = os.Getenv("INSECURE_MODE")
)
```
&nbsp;
### Step 3: Instrument your Go application
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your `main.go` file.
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your **`main.go`** file.
```bash
@ -85,9 +90,10 @@ To configure your application to send data we will need a function to initialize
return exporter.Shutdown
}
```
&nbsp;
### Step 4: Initialise the tracer in `main.go`
Modify the main function to initialise the tracer in main.go. Initiate the tracer at the very beginning of our main function.
### Step 4: Initialise the tracer in **`main.go`**
Modify the main function to initialise the tracer in **`main.go`**. Initiate the tracer at the very beginning of our main function.
```bash
func main() {
cleanup := initTracer()
@ -96,9 +102,10 @@ func main() {
......
}
```
&nbsp;
### Step 5: Add the OpenTelemetry Gin middleware
Configure Gin to use the middleware by adding the following lines in `main.go`
Configure Gin to use the middleware by adding the following lines in **`main.go`**
```bash
import (
....

View File

@ -1,4 +1,6 @@
&nbsp;
Once you are done intrumenting your Go Gin application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,15 +8,19 @@ Once you are done intrumenting your Go Gin application, you can run it using the
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Set environment variables and run your Go Gin application
```bash
SERVICE_NAME={{MYAPP}} INSECURE_MODE=true OTEL_EXPORTER_OTLP_ENDPOINT=localhost:4317 go run main.go

View File

@ -1,6 +1,9 @@
After setting up the Otel collector agent, follow the steps below to instrument your Go Application
&nbsp;
&nbsp;
### Step 1: Install OpenTelemetry Dependencies
Dependencies related to OpenTelemetry exporter and SDK have to be installed first
Dependencies related to OpenTelemetry exporter and SDK have to be installed first.
Run the below commands after navigating to the application source folder:
```bash
@ -12,7 +15,9 @@ go get go.opentelemetry.io/otel \
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
```
**Note:** Note that we are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
**Note:** We are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
&nbsp;
&nbsp;
### Step 2: Declare environment variables for configuring OpenTelemetry
Declare the following global variables in **`main.go`** which we will use to configure OpenTelemetry:
@ -23,9 +28,10 @@ Declare the following global variables in **`main.go`** which we will use to con
insecure = os.Getenv("INSECURE_MODE")
)
```
&nbsp;
### Step 3: Instrument your Go application
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your `main.go` file.
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your **`main.go`** file.
```bash
@ -84,9 +90,10 @@ To configure your application to send data we will need a function to initialize
return exporter.Shutdown
}
```
&nbsp;
### Step 4: Initialise the tracer in `main.go`
Modify the main function to initialise the tracer in main.go. Initiate the tracer at the very beginning of our main function.
### Step 4: Initialise the tracer in **`main.go`**
Modify the main function to initialise the tracer in **`main.go`**. Initiate the tracer at the very beginning of our main function.
```bash
func main() {
cleanup := initTracer()
@ -95,9 +102,10 @@ func main() {
......
}
```
&nbsp;
### Step 5: Add the OpenTelemetry Gin middleware
Configure Gin to use the middleware by adding the following lines in `main.go`
Configure Gin to use the middleware by adding the following lines in **`main.go`**
```bash
import (
....

View File

@ -1,3 +1,4 @@
&nbsp;
To run your Go Gin application, use the below command :
```bash

View File

@ -1,16 +1,22 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_linux_arm64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_linux_arm64.tar.gz -C otelcol-contrib
```
&nbsp;
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
### Step 3: Create `config.yaml` in `otelcol-contrib` folder with the below content in it
```bash
receivers:
otlp:

View File

@ -1,7 +1,9 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your Go Application
After setting up the Otel collector agent, follow the steps below to instrument your Go Application
&nbsp;
&nbsp;
### Step 1: Install OpenTelemetry Dependencies
Dependencies related to OpenTelemetry exporter and SDK have to be installed first
Dependencies related to OpenTelemetry exporter and SDK have to be installed first.
Run the below commands after navigating to the application source folder:
```bash
@ -13,7 +15,9 @@ go get go.opentelemetry.io/otel \
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
```
**Note:** Note that we are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
**Note:** We are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
&nbsp;
&nbsp;
### Step 2: Declare environment variables for configuring OpenTelemetry
Declare the following global variables in **`main.go`** which we will use to configure OpenTelemetry:
@ -24,9 +28,10 @@ Declare the following global variables in **`main.go`** which we will use to con
insecure = os.Getenv("INSECURE_MODE")
)
```
&nbsp;
### Step 3: Instrument your Go application
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your `main.go` file.
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your **`main.go`** file.
```bash
@ -85,9 +90,10 @@ To configure your application to send data we will need a function to initialize
return exporter.Shutdown
}
```
&nbsp;
### Step 4: Initialise the tracer in `main.go`
Modify the main function to initialise the tracer in main.go. Initiate the tracer at the very beginning of our main function.
### Step 4: Initialise the tracer in **`main.go`**
Modify the main function to initialise the tracer in **`main.go`**. Initiate the tracer at the very beginning of our main function.
```bash
func main() {
cleanup := initTracer()
@ -96,9 +102,10 @@ func main() {
......
}
```
&nbsp;
### Step 5: Add the OpenTelemetry Gin middleware
Configure Gin to use the middleware by adding the following lines in `main.go`
Configure Gin to use the middleware by adding the following lines in **`main.go`**
```bash
import (
....

View File

@ -1,4 +1,6 @@
&nbsp;
Once you are done intrumenting your Go Gin application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,15 +8,19 @@ Once you are done intrumenting your Go Gin application, you can run it using the
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Set environment variables and run your Go Gin application
```bash
SERVICE_NAME={{MYAPP}} INSECURE_MODE=true OTEL_EXPORTER_OTLP_ENDPOINT=localhost:4317 go run main.go

View File

@ -1,6 +1,9 @@
After setting up the Otel collector agent, follow the steps below to instrument your Go Application
&nbsp;
&nbsp;
### Step 1: Install OpenTelemetry Dependencies
Dependencies related to OpenTelemetry exporter and SDK have to be installed first
Dependencies related to OpenTelemetry exporter and SDK have to be installed first.
Run the below commands after navigating to the application source folder:
```bash
@ -12,7 +15,9 @@ go get go.opentelemetry.io/otel \
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
```
**Note:** Note that we are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
**Note:** We are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
&nbsp;
&nbsp;
### Step 2: Declare environment variables for configuring OpenTelemetry
Declare the following global variables in **`main.go`** which we will use to configure OpenTelemetry:
@ -23,9 +28,10 @@ Declare the following global variables in **`main.go`** which we will use to con
insecure = os.Getenv("INSECURE_MODE")
)
```
&nbsp;
### Step 3: Instrument your Go application
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your `main.go` file.
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your **`main.go`** file.
```bash
@ -84,9 +90,10 @@ To configure your application to send data we will need a function to initialize
return exporter.Shutdown
}
```
&nbsp;
### Step 4: Initialise the tracer in `main.go`
Modify the main function to initialise the tracer in main.go. Initiate the tracer at the very beginning of our main function.
### Step 4: Initialise the tracer in **`main.go`**
Modify the main function to initialise the tracer in **`main.go`**. Initiate the tracer at the very beginning of our main function.
```bash
func main() {
cleanup := initTracer()
@ -95,9 +102,10 @@ func main() {
......
}
```
&nbsp;
### Step 5: Add the OpenTelemetry Gin middleware
Configure Gin to use the middleware by adding the following lines in `main.go`
Configure Gin to use the middleware by adding the following lines in **`main.go`**
```bash
import (
....

View File

@ -1,3 +1,4 @@
&nbsp;
To run your Go Gin application, use the below command :
```bash

View File

@ -1,16 +1,19 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_darwin_amd64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_darwin_amd64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
### Step 3: Create `config.yaml` in folder `otelcol-contrib` with the below content in it
```bash
receivers:
otlp:

View File

@ -1,7 +1,9 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your Go Application
After setting up the Otel collector agent, follow the steps below to instrument your Go Application
&nbsp;
&nbsp;
### Step 1: Install OpenTelemetry Dependencies
Dependencies related to OpenTelemetry exporter and SDK have to be installed first
Dependencies related to OpenTelemetry exporter and SDK have to be installed first.
Run the below commands after navigating to the application source folder:
```bash
@ -13,7 +15,9 @@ go get go.opentelemetry.io/otel \
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
```
**Note:** Note that we are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
**Note:** We are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
&nbsp;
&nbsp;
### Step 2: Declare environment variables for configuring OpenTelemetry
Declare the following global variables in **`main.go`** which we will use to configure OpenTelemetry:
@ -24,9 +28,10 @@ Declare the following global variables in **`main.go`** which we will use to con
insecure = os.Getenv("INSECURE_MODE")
)
```
&nbsp;
### Step 3: Instrument your Go application
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your `main.go` file.
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your **`main.go`** file.
```bash
@ -85,9 +90,10 @@ To configure your application to send data we will need a function to initialize
return exporter.Shutdown
}
```
&nbsp;
### Step 4: Initialise the tracer in `main.go`
Modify the main function to initialise the tracer in main.go. Initiate the tracer at the very beginning of our main function.
### Step 4: Initialise the tracer in **`main.go`**
Modify the main function to initialise the tracer in **`main.go`**. Initiate the tracer at the very beginning of our main function.
```bash
func main() {
cleanup := initTracer()
@ -96,9 +102,10 @@ func main() {
......
}
```
&nbsp;
### Step 5: Add the OpenTelemetry Gin middleware
Configure Gin to use the middleware by adding the following lines in `main.go`
Configure Gin to use the middleware by adding the following lines in **`main.go`**
```bash
import (
....

View File

@ -1,4 +1,6 @@
&nbsp;
Once you are done intrumenting your Go Gin application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,15 +8,19 @@ Once you are done intrumenting your Go Gin application, you can run it using the
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Set environment variables and run your Go Gin application
```bash
SERVICE_NAME={{MYAPP}} INSECURE_MODE=true OTEL_EXPORTER_OTLP_ENDPOINT=localhost:4317 go run main.go

View File

@ -1,6 +1,9 @@
After setting up the Otel collector agent, follow the steps below to instrument your Go Application
&nbsp;
&nbsp;
### Step 1: Install OpenTelemetry Dependencies
Dependencies related to OpenTelemetry exporter and SDK have to be installed first
Dependencies related to OpenTelemetry exporter and SDK have to be installed first.
Run the below commands after navigating to the application source folder:
```bash
@ -12,7 +15,9 @@ go get go.opentelemetry.io/otel \
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
```
**Note:** Note that we are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
**Note:** We are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
&nbsp;
&nbsp;
### Step 2: Declare environment variables for configuring OpenTelemetry
Declare the following global variables in **`main.go`** which we will use to configure OpenTelemetry:
@ -23,9 +28,10 @@ Declare the following global variables in **`main.go`** which we will use to con
insecure = os.Getenv("INSECURE_MODE")
)
```
&nbsp;
### Step 3: Instrument your Go application
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your `main.go` file.
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your **`main.go`** file.
```bash
@ -84,9 +90,10 @@ To configure your application to send data we will need a function to initialize
return exporter.Shutdown
}
```
&nbsp;
### Step 4: Initialise the tracer in `main.go`
Modify the main function to initialise the tracer in main.go. Initiate the tracer at the very beginning of our main function.
### Step 4: Initialise the tracer in **`main.go`**
Modify the main function to initialise the tracer in **`main.go`**. Initiate the tracer at the very beginning of our main function.
```bash
func main() {
cleanup := initTracer()
@ -95,9 +102,10 @@ func main() {
......
}
```
&nbsp;
### Step 5: Add the OpenTelemetry Gin middleware
Configure Gin to use the middleware by adding the following lines in `main.go`
Configure Gin to use the middleware by adding the following lines in **`main.go`**
```bash
import (
....

View File

@ -1,3 +1,4 @@
&nbsp;
To run your Go Gin application, use the below command :
```bash

View File

@ -1,15 +1,17 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_darwin_arm64.tar.gz
```
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_darwin_arm64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
### Step 3: Create `config.yaml` in folder `otelcol-contrib` with the below content in it
```bash
receivers:
otlp:

View File

@ -1,7 +1,9 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your Go Application
After setting up the Otel collector agent, follow the steps below to instrument your Go Application
&nbsp;
&nbsp;
### Step 1: Install OpenTelemetry Dependencies
Dependencies related to OpenTelemetry exporter and SDK have to be installed first
Dependencies related to OpenTelemetry exporter and SDK have to be installed first.
Run the below commands after navigating to the application source folder:
```bash
@ -13,7 +15,9 @@ go get go.opentelemetry.io/otel \
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
```
**Note:** Note that we are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
**Note:** We are assuming you are using gin request router. If you are using other request routers, check out the [corresponding package](https://signoz.io/docs/instrumentation/golang/#request-routers).
&nbsp;
&nbsp;
### Step 2: Declare environment variables for configuring OpenTelemetry
Declare the following global variables in **`main.go`** which we will use to configure OpenTelemetry:
@ -24,9 +28,10 @@ Declare the following global variables in **`main.go`** which we will use to con
insecure = os.Getenv("INSECURE_MODE")
)
```
&nbsp;
### Step 3: Instrument your Go application
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your `main.go` file.
To configure your application to send data we will need a function to initialize OpenTelemetry. Add the following snippet of code in your **`main.go`** file.
```bash
@ -85,9 +90,10 @@ To configure your application to send data we will need a function to initialize
return exporter.Shutdown
}
```
&nbsp;
### Step 4: Initialise the tracer in `main.go`
Modify the main function to initialise the tracer in main.go. Initiate the tracer at the very beginning of our main function.
### Step 4: Initialise the tracer in **`main.go`**
Modify the main function to initialise the tracer in **`main.go`**. Initiate the tracer at the very beginning of our main function.
```bash
func main() {
cleanup := initTracer()
@ -96,9 +102,10 @@ func main() {
......
}
```
&nbsp;
### Step 5: Add the OpenTelemetry Gin middleware
Configure Gin to use the middleware by adding the following lines in `main.go`
Configure Gin to use the middleware by adding the following lines in **`main.go`**
```bash
import (
....

View File

@ -1,4 +1,6 @@
&nbsp;
Once you are done intrumenting your Go Gin application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,15 +8,19 @@ Once you are done intrumenting your Go Gin application, you can run it using the
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Set environment variables and run your Go Gin application
```bash
SERVICE_NAME={{MYAPP}} INSECURE_MODE=true OTEL_EXPORTER_OTLP_ENDPOINT=localhost:4317 go run main.go

View File

@ -1,14 +1,17 @@
### Install otel-collector in your Kubernetes infra
## Install otel-collector in your Kubernetes infra
&nbsp;
Add the SigNoz Helm Chart repository
```bash
helm repo add signoz https://charts.signoz.io
```
&nbsp;
If the chart is already present, update the chart to the latest using:
```bash
helm repo update
```
&nbsp;
Install the Kubernetes Infrastructure chart provided by SigNoz
```bash

View File

@ -1,8 +1,10 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your JavaScript Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary
```bash

View File

@ -2,6 +2,7 @@
```bash
vim /opt/jboss-eap-7.1/bin/standalone.conf
```
&nbsp;
### Update `JAVA_OPTS` environment variable
```bash
@ -9,6 +10,11 @@ JAVA_OPTS="-javaagent:/<path>/opentelemetry-javaagent.jar"
```
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
**Note:**
- In case you're dockerising your application, make sure to dockerise it along with OpenTelemetry instrumentation done in previous step.
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/jboss/#troubleshooting-your-installation) for assistance.

View File

@ -1,6 +1,8 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary
```bash

View File

@ -2,6 +2,7 @@
```bash
vim /opt/jboss-eap-7.1/bin/standalone.conf
```
&nbsp;
### Update `JAVA_OPTS` environment variable
Update `JAVA_OPTS` environment variable with configurations required to send data to SigNoz cloud in your configuration file.
@ -15,9 +16,13 @@ JAVA_OPTS="-javaagent:/<path>/opentelemetry-javaagent.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
### (Optional step) Write the output/logs of standalone.sh script to a file nohup.out as a background thread
#### (Optional step) Write the output/logs of standalone.sh script to a file nohup.out as a background thread
```bash
/opt/jboss-eap-7.1/bin/standalone.sh > /opt/jboss-eap-7.1/bin/nohup.out &
```
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/jboss/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_linux_amd64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_linux_amd64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your JavaScript Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,5 @@
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,20 +7,24 @@ Once you are done intrumenting your Java application, you can run it using the b
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Open `standalone.conf` Configuration File
```bash
vim /opt/jboss-eap-7.1/bin/standalone.conf
```
&nbsp;
### Step 3: Update `JAVA_OPTS` environment variable
```bash
@ -28,3 +33,6 @@ JAVA_OPTS="-javaagent:/<path>/opentelemetry-javaagent.jar"
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/jboss/#troubleshooting-your-installation) for assistance.

View File

@ -1,6 +1,8 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary
```bash

View File

@ -2,6 +2,7 @@
```bash
vim /opt/jboss-eap-7.1/bin/standalone.conf
```
&nbsp;
### Update `JAVA_OPTS` environment variable
Update `JAVA_OPTS` environment variable with configurations required to send data to SigNoz cloud in your configuration file.
@ -15,9 +16,13 @@ JAVA_OPTS="-javaagent:/<path>/opentelemetry-javaagent.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
### (Optional step) Write the output/logs of standalone.sh script to a file nohup.out as a background thread
#### (Optional step) Write the output/logs of standalone.sh script to a file nohup.out as a background thread
```bash
/opt/jboss-eap-7.1/bin/standalone.sh > /opt/jboss-eap-7.1/bin/nohup.out &
```
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/jboss/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_linux_arm64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_linux_arm64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your JavaScript Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,5 @@
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,20 +7,24 @@ Once you are done intrumenting your Java application, you can run it using the b
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Open `standalone.conf` Configuration File
```bash
vim /opt/jboss-eap-7.1/bin/standalone.conf
```
&nbsp;
### Step 3: Update `JAVA_OPTS` environment variable
```bash
@ -28,3 +33,6 @@ JAVA_OPTS="-javaagent:/<path>/opentelemetry-javaagent.jar"
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/jboss/#troubleshooting-your-installation) for assistance.

View File

@ -1,6 +1,8 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary
```bash

View File

@ -2,6 +2,7 @@
```bash
vim /opt/jboss-eap-7.1/bin/standalone.conf
```
&nbsp;
### Update `JAVA_OPTS` environment variable
Update `JAVA_OPTS` environment variable with configurations required to send data to SigNoz cloud in your configuration file.
@ -15,9 +16,13 @@ JAVA_OPTS="-javaagent:/<path>/opentelemetry-javaagent.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
### (Optional step) Write the output/logs of standalone.sh script to a file nohup.out as a background thread
#### (Optional step) Write the output/logs of standalone.sh script to a file nohup.out as a background thread
```bash
/opt/jboss-eap-7.1/bin/standalone.sh > /opt/jboss-eap-7.1/bin/nohup.out &
```
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/jboss/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_darwin_amd64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_darwin_amd64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your JavaScript Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,5 @@
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,20 +7,24 @@ Once you are done intrumenting your Java application, you can run it using the b
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Open `standalone.conf` Configuration File
```bash
vim /opt/jboss-eap-7.1/bin/standalone.conf
```
&nbsp;
### Step 3: Update `JAVA_OPTS` environment variable
```bash
@ -28,3 +33,6 @@ JAVA_OPTS="-javaagent:/<path>/opentelemetry-javaagent.jar"
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/jboss/#troubleshooting-your-installation) for assistance.

View File

@ -1,6 +1,8 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary
```bash

View File

@ -2,6 +2,7 @@
```bash
vim /opt/jboss-eap-7.1/bin/standalone.conf
```
&nbsp;
### Update `JAVA_OPTS` environment variable
Update `JAVA_OPTS` environment variable with configurations required to send data to SigNoz cloud in your configuration file.
@ -15,9 +16,13 @@ JAVA_OPTS="-javaagent:/<path>/opentelemetry-javaagent.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
### (Optional step) Write the output/logs of standalone.sh script to a file nohup.out as a background thread
#### (Optional step) Write the output/logs of standalone.sh script to a file nohup.out as a background thread
```bash
/opt/jboss-eap-7.1/bin/standalone.sh > /opt/jboss-eap-7.1/bin/nohup.out &
```
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/jboss/#troubleshooting-your-installation) for assistance.

View File

@ -1,13 +1,17 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_darwin_arm64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_darwin_arm64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your JavaScript Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,5 @@
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,20 +7,24 @@ Once you are done intrumenting your Java application, you can run it using the b
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Open `standalone.conf` Configuration File
```bash
vim /opt/jboss-eap-7.1/bin/standalone.conf
```
&nbsp;
### Step 3: Update `JAVA_OPTS` environment variable
```bash
@ -28,3 +33,6 @@ JAVA_OPTS="-javaagent:/<path>/opentelemetry-javaagent.jar"
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/jboss/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Install otel-collector in your Kubernetes infra
## Install otel-collector in your Kubernetes infra
&nbsp;
Add the SigNoz Helm Chart repository
```bash
helm repo add signoz https://charts.signoz.io
```
&nbsp;
If the chart is already present, update the chart to the latest using:
```bash
helm repo update
```
&nbsp;
Install the Kubernetes Infrastructure chart provided by SigNoz
```bash

View File

@ -1,8 +1,10 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your Java Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary
```bash

View File

@ -1,3 +1,5 @@
&nbsp;
Once you are done intrumenting your Java application, you can run it using the below command
```bash
@ -5,6 +7,11 @@ java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
```
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
**Note:**
- In case you're dockerising your application, make sure to dockerise it along with OpenTelemetry instrumentation done in previous step.
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/java/#troubleshooting-your-installation) for assistance.

View File

@ -1,5 +1,6 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary agent

View File

@ -10,5 +10,7 @@ java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/java/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_linux_amd64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_linux_amd64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your Java Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,7 @@
OOnce you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,15 +9,19 @@ OOnce you are done intrumenting your Java application, you can run it using the
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Run your application
```bash
java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar

View File

@ -1,5 +1,6 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary agent

View File

@ -10,5 +10,7 @@ java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/java/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_linux_arm64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_linux_arm64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your Java Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,7 @@
OOnce you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,15 +9,19 @@ OOnce you are done intrumenting your Java application, you can run it using the
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Run your application
```bash
java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar

View File

@ -1,5 +1,6 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary agent

View File

@ -10,5 +10,7 @@ java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/java/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_darwin_amd64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_darwin_amd64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your Java Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,7 @@
OOnce you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,15 +9,19 @@ OOnce you are done intrumenting your Java application, you can run it using the
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Run your application
```bash
java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar

View File

@ -1,5 +1,6 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary agent

View File

@ -10,5 +10,7 @@ java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/java/#troubleshooting-your-installation) for assistance.

View File

@ -1,13 +1,17 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_darwin_arm64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_darwin_arm64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your Java Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,7 @@
OOnce you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,12 +9,14 @@ OOnce you are done intrumenting your Java application, you can run it using the
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```

View File

@ -1,14 +1,17 @@
### Install otel-collector in your Kubernetes infra
## Install otel-collector in your Kubernetes infra
&nbsp;
Add the SigNoz Helm Chart repository
```bash
helm repo add signoz https://charts.signoz.io
```
&nbsp;
If the chart is already present, update the chart to the latest using:
```bash
helm repo update
```
&nbsp;
Install the Kubernetes Infrastructure chart provided by SigNoz
```bash

View File

@ -1,7 +1,9 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
&nbsp;
After setting up the Otel collector agent, follow the steps below to instrument your Java Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,3 +1,5 @@
&nbsp;
Once you are done intrumenting your Java application, you can run it using the below commands
@ -7,5 +9,11 @@ java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
**Note:**
- In case you're dockerising your application, make sure to dockerise it along with OpenTelemetry instrumentation done in previous step.
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/springboot/#troubleshooting-your-installation) for assistance.

View File

@ -2,6 +2,8 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary agent
```bash

View File

@ -10,5 +10,7 @@ java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/springboot/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_linux_amd64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_linux_amd64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your Java Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,7 @@
&nbsp;
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,21 +9,28 @@ Once you are done intrumenting your Java application, you can run it using the b
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Run your application
```bash
java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
```
&nbsp;
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/springboot/#troubleshooting-your-installation) for assistance.

View File

@ -2,6 +2,8 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary agent
```bash

View File

@ -10,5 +10,7 @@ java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/springboot/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_linux_arm64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_linux_arm64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your Java Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,7 @@
&nbsp;
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,21 +9,28 @@ Once you are done intrumenting your Java application, you can run it using the b
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Run your application
```bash
java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
```
&nbsp;
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/springboot/#troubleshooting-your-installation) for assistance.

View File

@ -2,6 +2,8 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary agent
```bash

View File

@ -10,5 +10,7 @@ java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/springboot/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_darwin_amd64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_darwin_amd64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your Java Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,7 @@
&nbsp;
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,20 +9,28 @@ Once you are done intrumenting your Java application, you can run it using the b
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Run your application
```bash
java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
```
&nbsp;
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/springboot/#troubleshooting-your-installation) for assistance.

View File

@ -2,6 +2,8 @@
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary agent
```bash

View File

@ -10,5 +10,7 @@ java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/springboot/#troubleshooting-your-installation) for assistance.

View File

@ -1,13 +1,17 @@
### Setup OpenTelemetry Binary as an agent
## Setup OpenTelemetry Binary as an agent
&nbsp;
### Step 1: Download otel-collector tar.gz
```bash
wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.79.0/otelcol-contrib_0.79.0_darwin_arm64.tar.gz
```
&nbsp;
### Step 2: Extract otel-collector tar.gz to the `otelcol-contrib` folder
```bash
mkdir otelcol-contrib && tar xvzf otelcol-contrib_0.79.0_darwin_arm64.tar.gz -C otelcol-contrib
```
&nbsp;
### Step 3: Create config.yaml in folder otelcol-contrib with the below content in it
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your Java Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,4 +1,7 @@
&nbsp;
Once you are done intrumenting your Java application, you can run it using the below commands
&nbsp;
### Step 1: Run OTel Collector
Run this command inside the `otelcol-contrib` directory that you created in the install Otel Collector step
@ -6,20 +9,28 @@ Once you are done intrumenting your Java application, you can run it using the b
```bash
./otelcol-contrib --config ./config.yaml &> otelcol-output.log & echo "$!" > otel-pid
```
### (Optional Step): View last 50 lines of `otelcol` logs
&nbsp;
#### (Optional Step): View last 50 lines of `otelcol` logs
```bash
tail -f -n 50 otelcol-output.log
```
### (Optional Step): Stop `otelcol`
#### (Optional Step): Stop `otelcol`
```bash
kill "$(< otel-pid)"
```
&nbsp;
### Step 2: Run your application
```bash
java -javaagent:<path>/opentelemetry-javaagent.jar -jar {{MYAPP}}.jar
```
&nbsp;
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/springboot/#troubleshooting-your-installation) for assistance.

View File

@ -1,14 +1,17 @@
### Install otel-collector in your Kubernetes infra
## Install otel-collector in your Kubernetes infra
&nbsp;
Add the SigNoz Helm Chart repository
```bash
helm repo add signoz https://charts.signoz.io
```
&nbsp;
If the chart is already present, update the chart to the latest using:
```bash
helm repo update
```
&nbsp;
Install the Kubernetes Infrastructure chart provided by SigNoz
```bash

View File

@ -1,7 +1,8 @@
After setting up the Otel collector agent, follow the steps below to instrumnet your JavaScript Application
After setting up the Otel collector agent, follow the steps below to instrument your JavaScript Application
#### Requirements
- Java 8 or higher
&nbsp;
### Download otel java binary

View File

@ -1,14 +1,24 @@
### Enable the instrumentation agent and run your application
## Enable the instrumentation agent and run your application
&nbsp;
If you run your .war package by putting in webapps folder, just add setenv.sh in your Tomcat bin folder.
&nbsp;
This should set the environment variable and start sending telemetry data to SigNoz Cloud.
```bash
export CATALINA_OPTS="$CATALINA_OPTS -javaagent:/<path>/opentelemetry-javaagent.jar"
```
&nbsp;
<path> - update it to the path where you downloaded the Java JAR agent in previous step
&nbsp;
&nbsp;
**Note:**
- In case you're dockerising your application, make sure to dockerise it along with OpenTelemetry instrumentation done in previous step.
&nbsp;
If you encounter any difficulties, please consult the [troubleshooting section](https://signoz.io/docs/instrumentation/tomcat/#troubleshooting-your-installation) for assistance.

Some files were not shown because too many files have changed in this diff Show More