Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App360 docs #550

Merged
merged 1 commit into from
Jun 18, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 21 additions & 24 deletions docs/shipping/App360/App360.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: Service-Performance-Monitoring-App360
title: Service Performance Monitoring via App360
overview: This integration allows you to configure App360 Service Performance Monitoring with OpenTelemetry collector and send spans and span metrics from your OpenTelemetry installation to Logz.io.
title: App360
overview: This integration allows you to configure App360 with OpenTelemetry collector and send data from your OpenTelemetry installation to Logz.io.
product: ['tracing']
os: ['windows', 'linux']
filters: ['Other']
Expand All @@ -16,27 +16,14 @@ drop_filter: []



[App360](https://docs.logz.io/docs/user-guide/distributed-tracing/spm/) is a high-level monitoring dashboard within Logz.io that enables you to monitor your tracing services and operations. This integration allows you to configure Service Performance Monitoring with OpenTelemetry collector and send spans and App360 span metrics from your OpenTelemetry installation to Logz.io.

{@include: ../../_include/metric-shipping/custom-dashboard.html} Install the pre-built dashboard to enhance the observability of your metrics.


<!-- logzio-inject:install:grafana:dashboards ids=["40ZpsSfzfGhbguMYoxwOqm, 5PFq9YHx2iQkwVMLCMOmjJ"] -->


{@include: ../../_include/metric-shipping/generic-dashboard.html}

[App360](https://docs.logz.io/docs/user-guide/distributed-tracing/spm/) is a high-level monitoring dashboard within Logz.io that enables you to monitor your operations. This integration allows you to configure the OpenTelemetry collector to send data from your OpenTelemetry installation to Logz.io using App360.


## Architecture overview

This integration is based on OpenTelemetry. It works as an add-on to existing OpenTelemetry installations. If you need to set up OpenTelemetry first, refer to our documentation on [OpenTelemetry](https://app.logz.io/#/dashboard/integrations/OpenTelemetry-data).

The integration includes:

* Configuring the OpenTelemetry collector to receive spans generated by your application instrumentation and send the spans and App360 span metrics to Logz.io
This integration is based on OpenTelemetry and includes configuring the OpenTelemetry collector to receive data generated by your application instrumentation and send it to Logz.io using App360

On deployment, your OpenTelemetry instrumentation captures spans from your application and forwards them to the collector, which exports the spans and App360 span metrics data to your Logz.io account.
On deployment, your OpenTelemetry instrumentation captures data from your application and forwards it to the collector, which exports the spans and metrics data to your Logz.io account using App360.

:::note
This integration uses OpenTelemetry Collector Contrib, not the OpenTelemetry Collector Core.
Expand All @@ -45,7 +32,7 @@ This integration uses OpenTelemetry Collector Contrib, not the OpenTelemetry Col



## Set up your locally hosted OpenTelemetry installation to send spans and App360 span metrics to Logz.io
## Set up your locally hosted OpenTelemetry installation to send App360 data to Logz.io

**Before you begin, you'll need**:

Expand All @@ -66,10 +53,6 @@ Create a dedicated directory on the host of your application and download the [O

##### Run as a Docker container

:::note
If you are already running a Logz.io Docker image `logzio/otel-collector-traces`, the new image `logzio/otel-collector-spm` will replace it.
:::

In the same Docker network as your application:

```shell
Expand Down Expand Up @@ -211,7 +194,17 @@ service:
{@include: ../../_include/log-shipping/listener-var.html}
{@include: ../../_include/tracing-shipping/tail-sampling.md}
By default, this configuration collects all traces that have a span that was completed with an error, all traces that are slower than 1000 ms, and 10% of the rest of the traces.
You can add more policy configurations to the processor. For more on this, refer to [OpenTelemetry Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/tailsamplingprocessor/README.md).
The configurable parameters in the Logz.io default configuration are:
| Parameter | Description | Default |
|---|---|---|
| threshold_ms | Threshold for the spand latency - all traces slower than the threshold value will be filtered in. | 1000 |
| sampling_percentage | Sampling percentage for the probabilistic policy. | 10 |
If you already have an OpenTelemetry installation, add to the configuration file of your existing OpenTelemetry collector the parameters described in the next steps.
Expand Down Expand Up @@ -293,4 +286,8 @@ Run the application to generate traces.

Give your data some time to get from your system to ours, and then open [App360](https://app.logz.io/#/dashboard/spm/services/table?start=now-1h&end=now).

## Kubernetes

:::note
Please note that running the Telemetry Collector for Kubernetes (k8s) is a separate use case, which is covered in detail in the specific section dedicated to the [Telemetry Collector for Kubernetes](/docs/user-guide/telemetry-collector).
:::
Loading