Ingest data into FusionReactor using a local Grafana Agent. from FusionReactorAPM on Vimeo.
diff --git a/docs/Monitor-your-data/Observability-agent/observability-agent.md b/docs/Monitor-your-data/Observability-agent/observability-agent.md index 488738a..42f3b35 100644 --- a/docs/Monitor-your-data/Observability-agent/observability-agent.md +++ b/docs/Monitor-your-data/Observability-agent/observability-agent.md @@ -133,10 +133,10 @@ To add integrations without being prompted for credentials, there are several en | **Variable** | **Type** |**Description** | |--------------------------|----------|---------------------------------------------------------------| -| `api_key` | `string` | API Key to authenticate with your FusionReactor Cloud Account. [Generate an API key](/Monitor-your-data/Observability-agent/overview/#step-1-generate-an-api-key). | +| `api_key` | `string` | API Key to authenticate with your OpsPilot Account. [Generate an API key](/Monitor-your-data/Observability-agent/overview/#step-1-generate-an-api-key). | |`metricsEndpoint` | `string` | Default: `https://api.fusionreactor.io/v1/metrics` | | `logsEndpoint` | `string` | Default: `https://api.fusionreactor.io/v1/logs` | -| `logs_user` | `string` | Username to authenticate with your FusionReactor Cloud Account (observability-agent-flow only)| +| `logs_user` | `string` | Username to authenticate with your OpsPilot Account (observability-agent-flow only)| diff --git a/docs/Monitor-your-data/Observability-agent/overview.md b/docs/Monitor-your-data/Observability-agent/overview.md index decbe85..3d40984 100644 --- a/docs/Monitor-your-data/Observability-agent/overview.md +++ b/docs/Monitor-your-data/Observability-agent/overview.md @@ -7,7 +7,7 @@ Integration allows you to ingest vital metrics to monitor the health of your ent Metric exporters are libraries that expose integration metrics to an agent. At FusionReactor, we have developed a wrapper for Grafana Alloy called the **Observability Agent** which allows you to ingest metrics with minimal configuration required. -With our Observability Agent you can ingest any data into the FusionReactor Cloud, and visualise your data within the [Integration dashboards](/Data-insights/Features/dashboards/#integration-dashboards). +With our Observability Agent you can ingest any data into the OpsPilot, and visualise your data within the [Integration dashboards](/Data-insights/Features/dashboards/#integration-dashboards). !!! info For local servers, we recommend utilizing FRAM for installing the Observability Agent, while for all other environments, we suggest opting for Docker. @@ -27,7 +27,7 @@ Exporters are available in many forms and allow you to monitor many aspects of y ### Viewing your metrics -Scraped metrics will be available in both **Explore** and the **Integrations Dashboard** within the FusionReactor Cloud. +Scraped metrics will be available in both **Explore** and the **Integrations Dashboard** within the OpsPilot. ### Getting started @@ -35,7 +35,7 @@ Scraped metrics will be available in both **Explore** and the **Integrations Das #### **Step 1**: Generate an API key. -To generate a new API key, go to your account settings page in FusionReactor Cloud [Account Settings](https://app.fusionreactor.io/account/settings). +To generate a new API key, go to your account settings page in OpsPilot [Account Settings](https://app.fusionreactor.io/account/settings). Under the API keys tab, click generate and create a key. diff --git a/docs/Monitor-your-data/OpenTelemetry/Configuration.md b/docs/Monitor-your-data/OpenTelemetry/Configuration.md index 010fa84..f6fff7e 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Configuration.md +++ b/docs/Monitor-your-data/OpenTelemetry/Configuration.md @@ -1,6 +1,6 @@ # OpenTelemetry Configuration -This guide covers essential OpenTelemetry configuration topics for FusionReactor Cloud, including semantic conventions, resource attributes, service naming, and sampling strategies. +This guide covers essential OpenTelemetry configuration topics for OpsPilot, including semantic conventions, resource attributes, service naming, and sampling strategies. --- @@ -8,13 +8,13 @@ This guide covers essential OpenTelemetry configuration topics for FusionReactor Semantic conventions are standardized naming and structure rules for OpenTelemetry attributes. Following these conventions ensures consistency across your observability stack and compatibility with tools, dashboards, and other systems. -**FusionReactor Cloud follows the official OpenTelemetry semantic conventions.** This guide provides common examples and FusionReactor-specific mappings. For the complete specification and all available conventions, refer to the [OpenTelemetry Semantic Conventions documentation](https://opentelemetry.io/docs/concepts/semantic-conventions/). +**OpsPilot follows the official OpenTelemetry semantic conventions.** This guide provides common examples and FusionReactor-specific mappings. For the complete specification and all available conventions, refer to the [OpenTelemetry Semantic Conventions documentation](https://opentelemetry.io/docs/concepts/semantic-conventions/). ### Why semantic conventions matter * **Consistency**: All services use the same attribute names * **Interoperability**: Dashboards and queries work across different applications -* **Searchability**: Easy filtering and correlation in FusionReactor Cloud +* **Searchability**: Easy filtering and correlation in OpsPilot * **Best practices**: Leverage community knowledge and tooling ### Common semantic conventions @@ -68,10 +68,10 @@ Resource attributes describe the entity producing telemetry data (your service, #### service.name -The most important resource attribute. It identifies your service in FusionReactor Cloud. +The most important resource attribute. It identifies your service in OpsPilot. !!! warning "Important mapping" - In FusionReactor Cloud, `service.name` becomes the `job` label for querying. + In OpsPilot, `service.name` becomes the `job` label for querying. **How to set it:** @@ -120,7 +120,7 @@ resource = Resource.create({ }) ``` -Query in FusionReactor Cloud: +Query in OpsPilot: ```promql http_requests_total{job="checkout-api", service_version="2.3.1"} ``` @@ -142,7 +142,7 @@ resource = Resource.create({ ``` !!! tip "Filter by environment" - In FusionReactor Cloud: `job="checkout-api" AND deployment_environment="production"` + In OpsPilot: `job="checkout-api" AND deployment_environment="production"` #### service.namespace @@ -217,7 +217,7 @@ service.namespace: ecommerce deployment.environment.name: production ``` -Query in FusionReactor Cloud: +Query in OpsPilot: ```promql {job="checkout-api", service_namespace="ecommerce", deployment_environment="production"} ``` @@ -261,7 +261,7 @@ Sampling reduces telemetry volume and costs by collecting a subset of traces whi ### When to use sampling * **High-traffic applications**: Reduce data volume without losing visibility -* **Cost management**: Control telemetry data costs in FusionReactor Cloud +* **Cost management**: Control telemetry data costs in OpsPilot * **Performance**: Reduce overhead on applications and collectors ### Head sampling @@ -483,11 +483,11 @@ docker run --network host \ --otlp-insecure ``` -Check FusionReactor Cloud's **Explore > Traces** for a service named `telemetrygen` within 60 seconds. +Check OpsPilot's **Explore > Traces** for a service named `telemetrygen` within 60 seconds. ### Verify resource attributes -Query your service in FusionReactor Cloud to see resource attributes: +Query your service in OpsPilot to see resource attributes: ```promql {job="your-service-name"} diff --git a/docs/Monitor-your-data/OpenTelemetry/FAQ.md b/docs/Monitor-your-data/OpenTelemetry/FAQ.md index 4954dec..359fc19 100644 --- a/docs/Monitor-your-data/OpenTelemetry/FAQ.md +++ b/docs/Monitor-your-data/OpenTelemetry/FAQ.md @@ -1,6 +1,6 @@ # OpenTelemetry FAQ -This page answers frequently asked questions about using OpenTelemetry with FusionReactor Cloud. +This page answers frequently asked questions about using OpenTelemetry with OpsPilot. --- @@ -38,7 +38,7 @@ Add manual instrumentation later only when you need to: * **Data transformation**: Filter, enrich, or scrub sensitive data before it leaves your network * **Reliability**: Queue and retry mechanisms handle network failures gracefully -For local development and testing, you can send data directly to FusionReactor Cloud using OTLP endpoints. +For local development and testing, you can send data directly to OpsPilot using OTLP endpoints. ### When should I initialize OpenTelemetry in my application? @@ -60,9 +60,9 @@ Initialize OpenTelemetry **at the very start of your application**, before loadi * **Trace**: A collection of spans linked together under a unique trace ID, representing a complete request flow through your system * **Transaction**: FusionReactor's term for a top-level operation, typically mapped to a trace's root span -### How do I see my service name in FusionReactor Cloud? +### How do I see my service name in OpsPilot? -The OpenTelemetry `service.name` resource attribute becomes the `job` label in FusionReactor Cloud. +The OpenTelemetry `service.name` resource attribute becomes the `job` label in OpsPilot. **Set it during initialization:** @@ -87,7 +87,7 @@ Yes. You can run both simultaneously: * **FusionReactor Agent**: Provides deep JVM/CFML insights, profiling, and error tracking * **OpenTelemetry**: Captures distributed traces, custom metrics, and standardized telemetry -They complement each other and send data to FusionReactor Cloud independently. +They complement each other and send data to OpsPilot independently. ### What should I include in span attributes? @@ -111,7 +111,7 @@ Follow [OpenTelemetry Semantic Conventions](https://opentelemetry.io/docs/concep ### What's the difference between OTLP gRPC and HTTP? -Both protocols send telemetry data to FusionReactor Cloud, but they have different characteristics: +Both protocols send telemetry data to OpsPilot, but they have different characteristics: | Feature | gRPC (port 4317) | HTTP (port 4318) | |---------|------------------|------------------| @@ -138,7 +138,7 @@ processors: send_batch_size: 1024 # Or when 1024 spans collected ``` -### Why is my data not appearing in FusionReactor Cloud? +### Why is my data not appearing in OpsPilot? Common causes: @@ -209,9 +209,9 @@ For detailed sampling configurations and strategies by traffic level, see the [C ## Visualization & Querying -### How do I query my OpenTelemetry metrics in FusionReactor Cloud? +### How do I query my OpenTelemetry metrics in OpsPilot? -FusionReactor Cloud uses PromQL for querying metrics. OpenTelemetry metrics are automatically converted to Prometheus format. +OpsPilot uses PromQL for querying metrics. OpenTelemetry metrics are automatically converted to Prometheus format. **Metric naming convention:** * Counter: `Instrumenting a Go app using OpenTelemetry from FusionReactorAPM on Vimeo.
## Prerequisites -* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in FusionReactor Cloud. +* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in OpsPilot. * **Go**: Go 1.21 or later installed on your system. * **Telemetry Pipeline**: You must have either an [OpenTelemetry Collector](/Monitor-your-data/OpenTelemetry/Shipping/Collector/) or [Grafana Alloy](/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent/) configured and running to receive data from your Go application. @@ -71,7 +71,7 @@ func setupMetrics(ctx context.Context) (*sdkmetric.MeterProvider, error) { ctx, otlpmetrichttp.WithInsecure(), otlpmetrichttp.WithEndpoint(endpoint), - // FusionReactor Cloud is Prometheus-based and requires Cumulative temporality + // OpsPilot is Prometheus-based and requires Cumulative temporality otlpmetrichttp.WithTemporalitySelector(func(kind sdkmetric.InstrumentKind) metricdata.Temporality { return metricdata.CumulativeTemporality }), @@ -227,9 +227,9 @@ Run your instrumented application: go run . ``` -## Step 5: Verify in FusionReactor Cloud +## Step 5: Verify in OpsPilot -1. **View in FusionReactor Cloud**: +1. **View in OpsPilot**: - Navigate to **Explore > Traces** to see your Go application traces - Navigate to **Explore > Metrics** and search for `demo_counter` to see the counter metric - Your service should appear as `test-go-server-http` @@ -238,14 +238,14 @@ go run . * Instrument HTTP handlers using `go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp` * Add database instrumentation with `go.opentelemetry.io/contrib/instrumentation/database/sql/otelsql` -* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in FusionReactor Cloud to visualize your Go application metrics +* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in OpsPilot to visualize your Go application metrics --- ## Related Guides - **[Configuration Guide](/Monitor-your-data/OpenTelemetry/Configuration/)**: Configure semantic conventions, resource attributes, and sampling strategies -- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in FusionReactor Cloud +- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in OpsPilot - **[Troubleshooting](/Monitor-your-data/OpenTelemetry/Troubleshooting/)**: Debug common instrumentation issues - **[FAQ](/Monitor-your-data/OpenTelemetry/FAQ/)**: Common questions about instrumentation diff --git a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Java.md b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Java.md index 4904aee..9a619ef 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Java.md +++ b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Java.md @@ -1,10 +1,10 @@ # Java -This guide demonstrates how to instrument a Java application with OpenTelemetry to send traces, metrics, and logs to FusionReactor Cloud. +This guide demonstrates how to instrument a Java application with OpenTelemetry to send traces, metrics, and logs to OpsPilot. ## Prerequisites -* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in FusionReactor Cloud. +* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in OpsPilot. * **Java**: Java 8 or later installed on your system. * **Telemetry Pipeline**: You must have either an [OpenTelemetry Collector](/Monitor-your-data/OpenTelemetry/Shipping/Collector/) or [Grafana Alloy](/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent/) configured and running to receive data from your Java application. @@ -98,7 +98,7 @@ java -javaagent:opentelemetry-javaagent.jar \ ### Configuration options explained * `-javaagent:opentelemetry-javaagent.jar`: Attaches the OpenTelemetry agent -* `-Dotel.service.name`: Sets the service name (appears as `job` in FusionReactor Cloud) +* `-Dotel.service.name`: Sets the service name (appears as `job` in OpsPilot) * `-Dotel.exporter.otlp.endpoint`: Points to your local collector * `-Dotel.exporter.otlp.protocol`: Uses HTTP protocol (port 4318) @@ -106,9 +106,9 @@ java -javaagent:opentelemetry-javaagent.jar \ **If you see:** `Failed to export spans` or `Connection refused` **Fix:** Your collector is not running. Start it first using the [Collector setup guide](/Monitor-your-data/OpenTelemetry/Shipping/Collector/). -## Step 4: Verify in FusionReactor Cloud +## Step 4: Verify in OpsPilot -1. Log in to **FusionReactor Cloud** +1. Log in to **OpsPilot** 2. Navigate to **Explore**: - **Traces**: Select `Resource Service Name = fibonacci-service` - **Metrics**: Search for JVM metrics like `process.runtime.jvm.memory.usage{job="fibonacci-service"}` @@ -124,14 +124,14 @@ You should see: * Use the agent with Spring Boot applications for automatic REST endpoint instrumentation * Configure [agent extensions](https://opentelemetry.io/docs/languages/java/automatic/extensions/) for custom instrumentation * Add manual instrumentation for business-specific tracing using the [Java SDK](https://opentelemetry.io/docs/languages/java/instrumentation/) -* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in FusionReactor Cloud to visualize your Java application metrics +* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in OpsPilot to visualize your Java application metrics --- ## Related Guides - **[Configuration Guide](/Monitor-your-data/OpenTelemetry/Configuration/)**: Configure semantic conventions, resource attributes, and sampling strategies -- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in FusionReactor Cloud +- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in OpsPilot - **[Troubleshooting](/Monitor-your-data/OpenTelemetry/Troubleshooting/)**: Debug common instrumentation issues - **[FAQ](/Monitor-your-data/OpenTelemetry/FAQ/)**: Common questions about instrumentation diff --git a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Kotlin.md b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Kotlin.md index 18fc4aa..925e7fb 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Kotlin.md +++ b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Kotlin.md @@ -1,13 +1,13 @@ # Kotlin -This guide demonstrates how to instrument a Kotlin application with OpenTelemetry to send traces, metrics, and logs to FusionReactor Cloud. +This guide demonstrates how to instrument a Kotlin application with OpenTelemetry to send traces, metrics, and logs to OpsPilot. !!! warning "Beta Status" OpenTelemetry Kotlin is currently in **Beta**. APIs may change between releases. Suitable for testing and development, but review release notes carefully before production use. ## Prerequisites -* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in FusionReactor Cloud. +* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in OpsPilot. * **Kotlin**: Kotlin 1.8+ with JVM target installed on your system. * **Telemetry Pipeline**: You must have either an [OpenTelemetry Collector](/Monitor-your-data/OpenTelemetry/Shipping/Collector/) or [Grafana Alloy](/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent/) configured and running to receive data from your Kotlin application. @@ -158,9 +158,9 @@ The application will calculate 20 Fibonacci numbers and send telemetry to your l **If you see:** Connection errors or export failures **Fix:** Your collector is not running. Start it first using the [Collector setup guide](/Monitor-your-data/OpenTelemetry/Shipping/Collector/). -## Step 4: Verify in FusionReactor Cloud +## Step 4: Verify in OpsPilot -1. Log in to **FusionReactor Cloud** +1. Log in to **OpsPilot** 2. Navigate to **Explore**: - **Traces**: Select `Resource Service Name = fibonacci-service` @@ -174,14 +174,14 @@ You should see: * Use the Java agent for automatic instrumentation of Kotlin/JVM applications * Instrument coroutines with custom spans * Add instrumentation to Ktor or Spring Boot applications -* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in FusionReactor Cloud +* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in OpsPilot --- ## Related Guides - **[Configuration Guide](/Monitor-your-data/OpenTelemetry/Configuration/)**: Configure semantic conventions, resource attributes, and sampling strategies -- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in FusionReactor Cloud +- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in OpsPilot - **[Troubleshooting](/Monitor-your-data/OpenTelemetry/Troubleshooting/)**: Debug common instrumentation issues - **[FAQ](/Monitor-your-data/OpenTelemetry/FAQ/)**: Common questions about instrumentation diff --git a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Overview.md b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Overview.md index 8572ef3..cbc4335 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Overview.md +++ b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Overview.md @@ -28,7 +28,7 @@ Manual instrumentation captures specific business logic or custom events that au ## Supported Languages -OpenTelemetry supports 12+ languages. Select your language below to get started with instrumentation for FusionReactor Cloud. +OpenTelemetry supports 12+ languages. Select your language below to get started with instrumentation for OpsPilot. ### Production-Ready (Stable) @@ -73,7 +73,7 @@ These languages are under active development: ## Next step: Shipping your data -Once your application is instrumented, the next step is sending that data to FusionReactor Cloud. +Once your application is instrumented, the next step is sending that data to OpsPilot. [Shipping Telemetry Overview →](/Monitor-your-data/OpenTelemetry/Shipping/overview/) @@ -95,7 +95,7 @@ After instrumenting your application, explore these topics: ### eBPF Instrumentation !!! info "Coming Soon" - eBPF (Extended Berkeley Packet Filter) instrumentation provides kernel-level observability without code changes or agent installation. This feature is coming soon to FusionReactor Cloud. + eBPF (Extended Berkeley Packet Filter) instrumentation provides kernel-level observability without code changes or agent installation. This feature is coming soon to OpsPilot. eBPF enables: @@ -108,7 +108,7 @@ After instrumenting your application, explore these topics: ### Kubernetes Operator !!! info "Coming Soon" - The OpenTelemetry Operator for Kubernetes provides automated instrumentation injection for containerized workloads. This feature is coming soon to FusionReactor Cloud. + The OpenTelemetry Operator for Kubernetes provides automated instrumentation injection for containerized workloads. This feature is coming soon to OpsPilot. The Operator enables: diff --git a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/PHP.md b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/PHP.md index 699786c..c0baa50 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/PHP.md +++ b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/PHP.md @@ -1,10 +1,10 @@ # PHP -This guide demonstrates how to instrument a PHP application with OpenTelemetry to send traces, metrics, and logs to FusionReactor Cloud. +This guide demonstrates how to instrument a PHP application with OpenTelemetry to send traces, metrics, and logs to OpsPilot. ## Prerequisites -* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in FusionReactor Cloud. +* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in OpsPilot. * **PHP**: PHP 8.0 or later with the following extensions: - `ext-json` - `ext-curl` @@ -320,7 +320,7 @@ The application will send telemetry to your local collector at `localhost:4318`. **If you see:** `Connection refused` or `Failed to export` **Fix:** Your collector is not running. Start it first using the [Collector setup guide](/Monitor-your-data/OpenTelemetry/Shipping/Collector/). -## Step 5: Verify in FusionReactor Cloud +## Step 5: Verify in OpsPilot 1. Generate some traffic: ```bash @@ -328,7 +328,7 @@ The application will send telemetry to your local collector at `localhost:4318`. for i in {1..10}; do curl "http://localhost:8000/fibonacci?n=$i"; done ``` -2. Log in to **FusionReactor Cloud** +2. Log in to **OpsPilot** 3. Navigate to **Explore**: - **Traces**: Select `Resource Service Name = php-otel-demo` @@ -348,14 +348,14 @@ You should see: * Instrument Laravel applications with [laravel-otel](https://github.com/open-telemetry/opentelemetry-php-contrib/tree/main/src/Instrumentation/Laravel) * Instrument Symfony applications with [symfony-otel](https://github.com/open-telemetry/opentelemetry-php-contrib/tree/main/src/Instrumentation/Symfony) * Add database instrumentation with PDO or Doctrine extensions -* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in FusionReactor Cloud +* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in OpsPilot --- ## Related Guides - **[Configuration Guide](/Monitor-your-data/OpenTelemetry/Configuration/)**: Configure semantic conventions, resource attributes, and sampling strategies -- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in FusionReactor Cloud +- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in OpsPilot - **[Troubleshooting](/Monitor-your-data/OpenTelemetry/Troubleshooting/)**: Debug common instrumentation issues - **[FAQ](/Monitor-your-data/OpenTelemetry/FAQ/)**: Common questions about instrumentation diff --git a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Python.md b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Python.md index 3e780db..81f59ea 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Python.md +++ b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Python.md @@ -1,10 +1,10 @@ # Python -This guide demonstrates how to instrument a Python application with OpenTelemetry to send traces, metrics, and logs to FusionReactor Cloud. +This guide demonstrates how to instrument a Python application with OpenTelemetry to send traces, metrics, and logs to OpsPilot. ## Prerequisites -* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in FusionReactor Cloud. +* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in OpsPilot. * **Python**: Python 3.8 or later installed on your system. * **Telemetry Pipeline**: You must have either an [OpenTelemetry Collector](/Monitor-your-data/OpenTelemetry/Shipping/Collector/) or [Grafana Alloy](/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent/) configured and running to receive data from your Python application. @@ -27,7 +27,7 @@ Create a file named `fib.py` with the following code. This example calculates Fi ```python # Fibonacci by Iteration -# Example Python code for FusionReactor Cloud integration +# Example Python code for OpsPilot integration import sys import logging @@ -113,7 +113,7 @@ def initialize_otel(endpoint: str) -> tuple: ) # Initialize Metrics - # FusionReactor Cloud is Prometheus-based and requires Cumulative temporality + # OpsPilot is Prometheus-based and requires Cumulative temporality cumulative = { Counter: AggregationTemporality.CUMULATIVE, UpDownCounter: AggregationTemporality.CUMULATIVE, @@ -181,7 +181,7 @@ Sets up the three OpenTelemetry providers: - **Meter Provider** - Sends metrics data to the collector - **Logger Provider** - Sends log data to the collector -All three providers use the same service name (`fib_by_iteration`), which appears as the `job` label in FusionReactor Cloud. +All three providers use the same service name (`fib_by_iteration`), which appears as the `job` label in OpsPilot. ## Step 3: Run locally @@ -197,9 +197,9 @@ The application will calculate 20 Fibonacci numbers and send telemetry to your l **If you see:** `Connection refused` or `Max retries exceeded` **Fix:** Your collector is not running. Start it first using the [Collector setup guide](/Monitor-your-data/OpenTelemetry/Shipping/Collector/). -## Step 4: Verify in FusionReactor Cloud +## Step 4: Verify in OpsPilot -1. Log in to **FusionReactor Cloud** +1. Log in to **OpsPilot** 2. Navigate to **Explore**: - **Traces**: Select `Resource Service Name = fib_by_iteration` - **Metrics**: Go to **Explore > Metrics**, select `fib_iteration_counter`, and run the query. Filter by `job = fib_by_iteration` to scope to your service. @@ -215,14 +215,14 @@ You should see: * Add automatic instrumentation for popular frameworks using [`opentelemetry-instrumentation`](https://opentelemetry.io/docs/languages/python/automatic/) * Instrument HTTP requests with `opentelemetry-instrumentation-requests` * Instrument database calls with `opentelemetry-instrumentation-sqlalchemy` -* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in FusionReactor Cloud to visualize your Python application metrics +* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in OpsPilot to visualize your Python application metrics --- ## Related Guides - **[Configuration Guide](/Monitor-your-data/OpenTelemetry/Configuration/)**: Configure semantic conventions, resource attributes, and sampling strategies -- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in FusionReactor Cloud +- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in OpsPilot - **[Troubleshooting](/Monitor-your-data/OpenTelemetry/Troubleshooting/)**: Debug common instrumentation issues - **[FAQ](/Monitor-your-data/OpenTelemetry/FAQ/)**: Common questions about instrumentation diff --git a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Ruby.md b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Ruby.md index 2c6285a..a123a6c 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Ruby.md +++ b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Ruby.md @@ -1,10 +1,10 @@ # Ruby -This guide demonstrates how to instrument a Ruby application with OpenTelemetry to send traces and metrics to FusionReactor Cloud. +This guide demonstrates how to instrument a Ruby application with OpenTelemetry to send traces and metrics to OpsPilot. ## Prerequisites -* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in FusionReactor Cloud. +* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in OpsPilot. * **Ruby**: Ruby 3.0 or later installed on your system. * **Telemetry Pipeline**: You must have either an [OpenTelemetry Collector](/Monitor-your-data/OpenTelemetry/Shipping/Collector/) or [Grafana Alloy](/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent/) configured and running to receive data from your Ruby application. @@ -102,7 +102,7 @@ Calculates the Fibonacci sequence while creating telemetry: **OpenTelemetry configuration:** Sets up the tracer provider: -- **Service Name** - Identifies the application (appears as `job` in FusionReactor Cloud) +- **Service Name** - Identifies the application (appears as `job` in OpsPilot) - **Span Processor** - Batches and exports spans to the collector - **Automatic Instrumentation** - `use_all()` enables instrumentation for common Ruby libraries @@ -120,9 +120,9 @@ The application will calculate 20 Fibonacci numbers and send telemetry to your l **If you see:** `Connection refused` or `Failed to export` **Fix:** Your collector is not running. Start it first using the [Collector setup guide](/Monitor-your-data/OpenTelemetry/Shipping/Collector/). -## Step 4: Verify in FusionReactor Cloud +## Step 4: Verify in OpsPilot -1. Log in to **FusionReactor Cloud** +1. Log in to **OpsPilot** 2. Navigate to **Explore**: - **Traces**: Select `Resource Service Name = fibonacci-service` - **Metrics**: Search for Ruby runtime metrics (if using instrumentation) @@ -137,14 +137,14 @@ You should see: * Instrument Rails applications with [`opentelemetry-instrumentation-rails`](https://opentelemetry.io/docs/languages/ruby/automatic/) * Add HTTP instrumentation with `opentelemetry-instrumentation-http` * Instrument database calls with `opentelemetry-instrumentation-active_record` -* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in FusionReactor Cloud to visualize your Ruby application metrics +* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in OpsPilot to visualize your Ruby application metrics --- ## Related Guides - **[Configuration Guide](/Monitor-your-data/OpenTelemetry/Configuration/)**: Configure semantic conventions, resource attributes, and sampling strategies -- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in FusionReactor Cloud +- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in OpsPilot - **[Troubleshooting](/Monitor-your-data/OpenTelemetry/Troubleshooting/)**: Debug common instrumentation issues - **[FAQ](/Monitor-your-data/OpenTelemetry/FAQ/)**: Common questions about instrumentation diff --git a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Rust.md b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Rust.md index 6b582be..9548e8f 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Rust.md +++ b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Rust.md @@ -1,13 +1,13 @@ # Rust -This guide demonstrates how to instrument a Rust application with OpenTelemetry to send traces, metrics, and logs to FusionReactor Cloud. +This guide demonstrates how to instrument a Rust application with OpenTelemetry to send traces, metrics, and logs to OpsPilot. !!! warning "Beta Status" OpenTelemetry Rust is currently in **Beta**. APIs may change between releases. Suitable for testing and development, but review release notes carefully before production use. ## Prerequisites -* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in FusionReactor Cloud. +* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in OpsPilot. * **Rust**: Rust 1.65 or later installed on your system. * **Telemetry Pipeline**: You must have either an [OpenTelemetry Collector](/Monitor-your-data/OpenTelemetry/Shipping/Collector/) or [Grafana Alloy](/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent/) configured and running to receive data from your Rust application. @@ -110,7 +110,7 @@ async fn main() { **`init_tracer()` function:** - Configures the OTLP HTTP exporter pointing to the collector -- Sets the service name (appears as `job` in FusionReactor Cloud) +- Sets the service name (appears as `job` in OpsPilot) - Uses Tokio runtime for async operations ## Step 3: Run locally @@ -127,9 +127,9 @@ The application will calculate 20 Fibonacci numbers and send telemetry to your l **If you see:** `Connection refused` or `Failed to export` **Fix:** Your collector is not running. Start it first using the [Collector setup guide](/Monitor-your-data/OpenTelemetry/Shipping/Collector/). -## Step 4: Verify in FusionReactor Cloud +## Step 4: Verify in OpsPilot -1. Log in to **FusionReactor Cloud** +1. Log in to **OpsPilot** 2. Navigate to **Explore**: - **Traces**: Select `Resource Service Name = fibonacci-service` - **Metrics**: Search for Rust application metrics @@ -143,14 +143,14 @@ You should see: * Add tracing to async operations using `#[tracing::instrument]` macro * Instrument HTTP servers with `opentelemetry-http` and frameworks like Actix or Axum -* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in FusionReactor Cloud to visualize your Rust application metrics +* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in OpsPilot to visualize your Rust application metrics --- ## Related Guides - **[Configuration Guide](/Monitor-your-data/OpenTelemetry/Configuration/)**: Configure semantic conventions, resource attributes, and sampling strategies -- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in FusionReactor Cloud +- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in OpsPilot - **[Troubleshooting](/Monitor-your-data/OpenTelemetry/Troubleshooting/)**: Debug common instrumentation issues - **[FAQ](/Monitor-your-data/OpenTelemetry/FAQ/)**: Common questions about instrumentation diff --git a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Swift.md b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Swift.md index b02b43f..8e218cb 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Swift.md +++ b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/Swift.md @@ -1,13 +1,13 @@ # Swift -This guide demonstrates how to instrument a Swift application with OpenTelemetry to send traces to FusionReactor Cloud. +This guide demonstrates how to instrument a Swift application with OpenTelemetry to send traces to OpsPilot. !!! note "Platform Status" OpenTelemetry Swift is **stable for traces**. Metrics and logs are in beta. Ideal for iOS, macOS, and server-side Swift applications. ## Prerequisites -* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in FusionReactor Cloud. +* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in OpsPilot. * **Swift**: Swift 5.7 or later installed on your system. * **Telemetry Pipeline**: You must have either an [OpenTelemetry Collector](/Monitor-your-data/OpenTelemetry/Shipping/Collector/) or [Grafana Alloy](/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent/) configured and running to receive data from your Swift application. @@ -141,9 +141,9 @@ The application will calculate 20 Fibonacci numbers and send telemetry to your l **If you see:** Connection errors or export failures **Fix:** Your collector is not running. Start it first using the [Collector setup guide](/Monitor-your-data/OpenTelemetry/Shipping/Collector/). -## Step 4: Verify in FusionReactor Cloud +## Step 4: Verify in OpsPilot -1. Log in to **FusionReactor Cloud** +1. Log in to **OpsPilot** 2. Navigate to **Explore**: - **Traces**: Select `Resource Service Name = fibonacci-service` @@ -157,14 +157,14 @@ You should see: * Instrument iOS/macOS apps with automatic network tracing * Add custom spans for business-critical operations * Integrate with SwiftUI for UI performance tracking -* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in FusionReactor Cloud to visualize your Swift application metrics +* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in OpsPilot to visualize your Swift application metrics --- ## Related Guides - **[Configuration Guide](/Monitor-your-data/OpenTelemetry/Configuration/)**: Configure semantic conventions, resource attributes, and sampling strategies -- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in FusionReactor Cloud +- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in OpsPilot - **[Troubleshooting](/Monitor-your-data/OpenTelemetry/Troubleshooting/)**: Debug common instrumentation issues - **[FAQ](/Monitor-your-data/OpenTelemetry/FAQ/)**: Common questions about instrumentation diff --git a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/node.md b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/node.md index ef3be06..3438822 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Instrumentation/node.md +++ b/docs/Monitor-your-data/OpenTelemetry/Instrumentation/node.md @@ -1,13 +1,13 @@ # Node.js -This guide demonstrates how to instrument a Node.js application with OpenTelemetry to send traces, metrics, and logs to FusionReactor Cloud. +This guide demonstrates how to instrument a Node.js application with OpenTelemetry to send traces, metrics, and logs to OpsPilot.Instrumenting a Go app using OpenTelemetry from FusionReactorAPM on Vimeo.
## Prerequisites -* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in FusionReactor Cloud. +* **FusionReactor API Key**: Obtain this from **Account Settings > API Keys** in OpsPilot. * **Docker Desktop**: [Install Docker Desktop](https://www.docker.com/products/docker-desktop/) to build and run the application container. * **Telemetry Pipeline**: You must have either an [OpenTelemetry Collector](/Monitor-your-data/OpenTelemetry/Shipping/Collector/) or [Grafana Alloy](/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent/) configured and running to receive data from your Node.js application. @@ -298,9 +298,9 @@ for i in {1..10}; do curl http://localhost:3000/fibonacci/$i; done **If you see:** `ECONNREFUSED` or `connect ECONNREFUSED` **Fix:** Your collector is not running. Start it first using the [Collector setup guide](/Monitor-your-data/OpenTelemetry/Shipping/Collector/). -## Step 6: Verify in FusionReactor Cloud +## Step 6: Verify in OpsPilot -1. Log in to **FusionReactor Cloud** +1. Log in to **OpsPilot** 2. Navigate to **Explore**: - **Traces**: Select `Resource Service Name = node-otel-demo` @@ -317,7 +317,7 @@ You should see: * Add database instrumentation with `@opentelemetry/instrumentation-pg` or `@opentelemetry/instrumentation-mongodb` * Instrument Redis with `@opentelemetry/instrumentation-redis` * Add custom business metrics using the Metrics API -* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in FusionReactor Cloud +* Create [custom dashboards](/Getting-started/Tutorials/create-dashboard/) in OpsPilot * Enable additional auto-instrumentations for your specific frameworks --- @@ -325,7 +325,7 @@ You should see: ## Related Guides - **[Configuration Guide](/Monitor-your-data/OpenTelemetry/Configuration/)**: Configure semantic conventions, resource attributes, and sampling strategies -- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in FusionReactor Cloud +- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in OpsPilot - **[Troubleshooting](/Monitor-your-data/OpenTelemetry/Troubleshooting/)**: Debug common instrumentation issues - **[FAQ](/Monitor-your-data/OpenTelemetry/FAQ/)**: Common questions about instrumentation diff --git a/docs/Monitor-your-data/OpenTelemetry/Shipping/Collector.md b/docs/Monitor-your-data/OpenTelemetry/Shipping/Collector.md index 2a0904f..098cda6 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Shipping/Collector.md +++ b/docs/Monitor-your-data/OpenTelemetry/Shipping/Collector.md @@ -1,20 +1,20 @@ # OpenTelemetry Collector -The OpenTelemetry (OTel) Collector is a high-performance, vendor-agnostic proxy that receives, processes, and exports telemetry data. It acts as the central hub of your observability pipeline, allowing you to aggregate data from multiple services before securely shipping it to FusionReactor Cloud. +The OpenTelemetry (OTel) Collector is a high-performance, vendor-agnostic proxy that receives, processes, and exports telemetry data. It acts as the central hub of your observability pipeline, allowing you to aggregate data from multiple services before securely shipping it to OpsPilot. ### Key Components * **Receivers**: Ingest data from your applications via the OTLP protocol (gRPC or HTTP). * **Processors**: Refine and transform data through batching, filtering, and resource limiting for efficiency and stability. -* **Exporters**: Send processed telemetry to FusionReactor Cloud via OTLP/HTTP. +* **Exporters**: Send processed telemetry to OpsPilot via OTLP/HTTP. -## Shipping Telemetry to FusionReactor Cloud +## Shipping Telemetry to OpsPilot The recommended approach is to use a **Unified OTLP Pipeline**. This allows you to send Traces, Metrics, and Logs through a single, efficient exporter. ### Prerequisites -* A FusionReactor Cloud account. +* A OpsPilot account. * Docker Desktop installed on your machine. @@ -71,7 +71,7 @@ service: ### **Step 2:** Obtain your API Key -1. Log in to **FusionReactor Cloud**. +1. Log in to **OpsPilot**. 2. Navigate to **Account Settings > API Keys**. 3. Generate a new key and save it securely. @@ -142,8 +142,8 @@ docker run --network host ghcr.io/open-telemetry/opentelemetry-collector-contrib ``` -2. **Check FusionReactor Cloud**: -* Log in to your **FusionReactor Cloud** dashboard. +2. **Check OpsPilot**: +* Log in to your **OpsPilot** dashboard. * Navigate to **Explore > Traces**. * You should see a service named **`telemetrygen`** appearing within 60 seconds. diff --git a/docs/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent.md b/docs/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent.md index 355e1ab..77e3227 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent.md +++ b/docs/Monitor-your-data/OpenTelemetry/Shipping/Grafana-agent.md @@ -6,7 +6,7 @@ For FusionReactor users, Alloy is recommended when you need a highly programmabl ## How it works -Alloy acts as a programmable intermediary. It receives OTLP data from your instrumented applications, processes it for efficiency or security, and exports it to FusionReactor Cloud using the OTLP protocol. +Alloy acts as a programmable intermediary. It receives OTLP data from your instrumented applications, processes it for efficiency or security, and exports it to OpsPilot using the OTLP protocol. @@ -42,7 +42,7 @@ otelcol.processor.batch "default" { } } -// 3. Export data to FusionReactor Cloud +// 3. Export data to OpsPilot otelcol.exporter.otlphttp "fusionreactor" { client { endpoint = "https://api.fusionreactor.io" diff --git a/docs/Monitor-your-data/OpenTelemetry/Shipping/Observability-agent.md b/docs/Monitor-your-data/OpenTelemetry/Shipping/Observability-agent.md index 36d5156..0b444dc 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Shipping/Observability-agent.md +++ b/docs/Monitor-your-data/OpenTelemetry/Shipping/Observability-agent.md @@ -1,7 +1,7 @@ The Observability Agent is a wrapper that we've developed around Grafana Alloy, simplifying the process of collecting and shipping data. -To send OpenTelemetry data to FusionReactor Cloud requires the installation of the Observability Agent. +To send OpenTelemetry data to OpsPilot requires the installation of the Observability Agent. * [FRAM](/Monitor-your-data/Observability-agent/Installation/FRAM/) diff --git a/docs/Monitor-your-data/OpenTelemetry/Shipping/overview.md b/docs/Monitor-your-data/OpenTelemetry/Shipping/overview.md index 65f349b..3a14866 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Shipping/overview.md +++ b/docs/Monitor-your-data/OpenTelemetry/Shipping/overview.md @@ -1,8 +1,8 @@ -# Shipping OpenTelemetry data to FusionReactor Cloud +# Shipping OpenTelemetry data to OpsPilot -Shipping OpenTelemetry (OTel) data to FusionReactor Cloud centralizes your observability and enables OpsPilot AI analysis, faster troubleshooting, and cross-tier performance optimization. Using a vendor-agnostic OTLP pipeline ensures your monitoring remains flexible and future-proof. +Shipping OpenTelemetry (OTel) data to OpsPilot centralizes your observability and enables OpsPilot AI analysis, faster troubleshooting, and cross-tier performance optimization. Using a vendor-agnostic OTLP pipeline ensures your monitoring remains flexible and future-proof. -To send your telemetry data to FusionReactor Cloud, you'll need a component that receives data from your instrumented applications and forwards it via OTLP. There are two recommended options: +To send your telemetry data to OpsPilot, you'll need a component that receives data from your instrumented applications and forwards it via OTLP. There are two recommended options: ### 1. [OpenTelemetry Collector](/Monitor-your-data/OpenTelemetry/Shipping/Collector/) @@ -26,7 +26,7 @@ Before and after setting up your telemetry pipeline, explore these topics: - **[Instrumentation Overview](/Monitor-your-data/OpenTelemetry/Instrumentation/Overview/)**: Instrument your application to generate telemetry - **[Configuration Guide](/Monitor-your-data/OpenTelemetry/Configuration/)**: Configure semantic conventions, resource attributes, and sampling strategies -- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in FusionReactor Cloud +- **[Visualize Your Data](/Monitor-your-data/OpenTelemetry/Visualize/Metrics/)**: Query and visualize your telemetry in OpsPilot - **[Troubleshooting](/Monitor-your-data/OpenTelemetry/Troubleshooting/)**: Debug common collector and pipeline issues - **[FAQ](/Monitor-your-data/OpenTelemetry/FAQ/)**: Common questions about shipping telemetry data diff --git a/docs/Monitor-your-data/OpenTelemetry/Troubleshooting.md b/docs/Monitor-your-data/OpenTelemetry/Troubleshooting.md index 5635a23..bf0ca02 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Troubleshooting.md +++ b/docs/Monitor-your-data/OpenTelemetry/Troubleshooting.md @@ -1,6 +1,6 @@ # OpenTelemetry Troubleshooting -This guide helps you diagnose and resolve common issues when using OpenTelemetry with FusionReactor Cloud. +This guide helps you diagnose and resolve common issues when using OpenTelemetry with OpsPilot. --- @@ -15,10 +15,10 @@ Before diving into specific issues, run these quick checks: --- -## Data Not Appearing in FusionReactor Cloud +## Data Not Appearing in OpsPilot ### Symptom -You've instrumented your application and configured your telemetry pipeline, but data doesn't appear in FusionReactor Cloud. +You've instrumented your application and configured your telemetry pipeline, but data doesn't appear in OpsPilot. ### Diagnostic Steps @@ -63,7 +63,7 @@ Check your pipeline logs for export errors. Look for keywords like: **Common error patterns:** -* **"connection refused"**: Pipeline cannot reach FusionReactor Cloud (network issue) +* **"connection refused"**: Pipeline cannot reach OpsPilot (network issue) * **"unauthorized"** or **"401"**: Invalid API key * **"timeout"**: Network latency or connectivity issue @@ -80,7 +80,7 @@ docker run --network host \ --otlp-insecure ``` -Check FusionReactor Cloud (**Explore > Traces**) for a service named `telemetrygen` within 60 seconds. +Check OpsPilot (**Explore > Traces**) for a service named `telemetrygen` within 60 seconds. **If test data appears**: Your pipeline is working correctly. The issue is with your application instrumentation. @@ -114,13 +114,13 @@ otelcol.exporter.otlphttp "fusionreactor" { ``` To get your API key: -1. Log in to **FusionReactor Cloud** +1. Log in to **OpsPilot** 2. Navigate to **User Menu > Account > API Keys** 3. Generate a new key or copy an existing one #### Network Connectivity -Test connectivity to FusionReactor Cloud from your pipeline environment: +Test connectivity to OpsPilot from your pipeline environment: ```bash # Test basic connectivity @@ -539,7 +539,7 @@ Pipeline consumes excessive CPU. ### Slow Data Ingestion #### Symptom -Telemetry data takes several minutes to appear in FusionReactor Cloud. +Telemetry data takes several minutes to appear in OpsPilot. #### Causes & Solutions @@ -553,7 +553,7 @@ processors: **Cause 2: Network latency** * Test latency: `ping api.fusionreactor.io` -* Consider deploying pipeline closer to applications or FusionReactor Cloud +* Consider deploying pipeline closer to applications or OpsPilot **Cause 3: Exporter queue backlog** ```yaml @@ -604,13 +604,13 @@ def background_task(): ### Duplicate Metrics or Traces #### Symptom -Same telemetry appears multiple times in FusionReactor Cloud. +Same telemetry appears multiple times in OpsPilot. #### Causes & Solutions **Cause 1: Multiple exporters in application** -* Application configured to send to both pipeline and FusionReactor Cloud directly -* **Solution**: Send only to your pipeline, let it forward to FusionReactor Cloud +* Application configured to send to both pipeline and OpsPilot directly +* **Solution**: Send only to your pipeline, let it forward to OpsPilot **Cause 2: Multiple pipeline instances** * Duplicate pipelines ingesting same data @@ -693,7 +693,7 @@ Access metrics at: `http://localhost:8888/metrics` failed to export: connection refused ``` -**Cause**: Pipeline cannot reach FusionReactor Cloud endpoint. +**Cause**: Pipeline cannot reach OpsPilot endpoint. **Solution**: 1. Verify endpoint URL in exporter config @@ -729,7 +729,7 @@ failed to export: 401 Unauthorized **Cause**: Invalid or missing API key. **Solution**: -1. Verify API key in FusionReactor Cloud: **User Menu > Account > API Keys** +1. Verify API key in OpsPilot: **User Menu > Account > API Keys** 2. Check API key is correctly set in your pipeline configuration 3. Ensure no extra spaces or characters in the API key @@ -759,11 +759,11 @@ When contacting support, provide: 2. **Pipeline logs** showing the error 3. **Application instrumentation code** (initialization section) 4. **OpenTelemetry SDK versions** used -5. **FusionReactor Cloud account region** (US or EU) +5. **OpsPilot account region** (US or EU) ### Contact Support -* **FusionReactor Support**: Use the chat bubble in FusionReactor Cloud +* **FusionReactor Support**: Use the chat bubble in OpsPilot * **Community Forum**: [FusionReactor Community](https://community.fusionreactor.io/) ### Additional Resources diff --git a/docs/Monitor-your-data/OpenTelemetry/Visualize/Distributed-tracing.md b/docs/Monitor-your-data/OpenTelemetry/Visualize/Distributed-tracing.md index 093e6da..89e67a3 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Visualize/Distributed-tracing.md +++ b/docs/Monitor-your-data/OpenTelemetry/Visualize/Distributed-tracing.md @@ -8,7 +8,7 @@ Distributed tracing is a technique of tracking application requests as they move from frontend devices to backend services and databases. Developers use distributed tracing to troubleshoot applications and optimize application performance. You can pinpoint requests with errors or high latency and quickly diagnose performance issues to gain real-time visibility of the user experience. -FusionReactor Cloud is able to provide distributed trace information which is captured and displayed in a graphical format, so you can visualize the entire request flow and quickly identify any issues or bottlenecks. +OpsPilot is able to provide distributed trace information which is captured and displayed in a graphical format, so you can visualize the entire request flow and quickly identify any issues or bottlenecks. diff --git a/docs/Monitor-your-data/OpenTelemetry/Visualize/Logs.md b/docs/Monitor-your-data/OpenTelemetry/Visualize/Logs.md index 12c908c..9afb3fd 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Visualize/Logs.md +++ b/docs/Monitor-your-data/OpenTelemetry/Visualize/Logs.md @@ -2,15 +2,15 @@ OpenTelemetry logs integrate logging information into your observability stack, enriching it with additional telemetry data and linking it to related traces. Log entries can accommodate both unstructured text and structured information, making them flexible for various logging needs. -To visualize your logs, simply navigate to FusionReactor Cloud in a browser and access the **Log Browser** dashboard, which provides comprehensive logging features without requiring additional configuration. Alternatively, you can view your logs in **Explore** by selecting **Logs** from the datasource dropdown, or via the **Logging** tab. +To visualize your logs, simply navigate to OpsPilot in a browser and access the **Log Browser** dashboard, which provides comprehensive logging features without requiring additional configuration. Alternatively, you can view your logs in **Explore** by selecting **Logs** from the datasource dropdown, or via the **Logging** tab. ## Python example !!! info - The following example relies on a user having first [instrumented a Python application](/Monitor-your-data/OpenTelemetry/Instrumentation/Python/) to ship data to FR Cloud. + The following example relies on a user having first [instrumented a Python application](/Monitor-your-data/OpenTelemetry/Instrumentation/Python/) to ship data to OpsPilot. -In the FR Cloud **Logging** window, open the **Job** dropdown and select `fib_by_iteration`. All the log messages emitted by the Python code will appear. +In the OpsPilot **Logging** window, open the **Job** dropdown and select `fib_by_iteration`. All the log messages emitted by the Python code will appear. *Logs supplied by Python* \ No newline at end of file diff --git a/docs/Monitor-your-data/OpenTelemetry/Visualize/Metrics.md b/docs/Monitor-your-data/OpenTelemetry/Visualize/Metrics.md index c959b53..87b68f7 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Visualize/Metrics.md +++ b/docs/Monitor-your-data/OpenTelemetry/Visualize/Metrics.md @@ -3,7 +3,7 @@ Metrics provide ongoing visibility into numerical and statistical data about your applications and services. For example, you can track CPU utilization, memory usage, or concurrent user counts in real-time. -To visualize your OTel metrics, simply navigate to the **Explore** tab in FusionReactor Cloud. Alternatively, create your own personalized dashboards to provide a tailored view of your application's OTel metrics. +To visualize your OTel metrics, simply navigate to the **Explore** tab in OpsPilot. Alternatively, create your own personalized dashboards to provide a tailored view of your application's OTel metrics. !!! info "Learn more" [Create a custom dashboard](/Getting-started/Tutorials/create-dashboard/) @@ -11,9 +11,9 @@ To visualize your OTel metrics, simply navigate to the **Explore** tab in Fusion ## Python example !!! info - The following example relies on a user having first [instrumented a Python application](/Monitor-your-data/OpenTelemetry/Instrumentation/Python/) to ship data to FR Cloud. + The following example relies on a user having first [instrumented a Python application](/Monitor-your-data/OpenTelemetry/Instrumentation/Python/) to ship data to OpsPilot. -In the FR Cloud **Explore** window, ensure the metrics datasource is selected. Then either use the **Builder** to find your metric (you can search for `job`: `fib_by_iteration`), or use the following in **Code** search mode: `fib_iteration_counter_total{job="fib_by_iteration"}`. You'll get a graph and table of the metric. +In the OpsPilot **Explore** window, ensure the metrics datasource is selected. Then either use the **Builder** to find your metric (you can search for `job`: `fib_by_iteration`), or use the following in **Code** search mode: `fib_iteration_counter_total{job="fib_by_iteration"}`. You'll get a graph and table of the metric. *Metrics supplied by Python* diff --git a/docs/Monitor-your-data/OpenTelemetry/Visualize/Traces.md b/docs/Monitor-your-data/OpenTelemetry/Visualize/Traces.md index ce67cff..7046aad 100644 --- a/docs/Monitor-your-data/OpenTelemetry/Visualize/Traces.md +++ b/docs/Monitor-your-data/OpenTelemetry/Visualize/Traces.md @@ -4,14 +4,14 @@ Traces represent individual execution flows within your application, capturing w A trace typically represents a single request or operation, and serves as a container for spans. These spans are linked together under a unique trace ID, with each span representing an individual step in your business logic. -To visualize your OTel traces, simply navigate to FusionReactor Cloud and access the **Show Traces** dashboards, which provide comprehensive tracing features without requiring additional configuration. Alternatively, you can view your traces in **Explore** by selecting **Traces** from the datasource dropdown. +To visualize your OTel traces, simply navigate to OpsPilot and access the **Show Traces** dashboards, which provide comprehensive tracing features without requiring additional configuration. Alternatively, you can view your traces in **Explore** by selecting **Traces** from the datasource dropdown. ## Python example !!! info - The following example relies on a user having first [instrumented a Python application](/Monitor-your-data/OpenTelemetry/Instrumentation/Python/) to ship data to FR Cloud. + The following example relies on a user having first [instrumented a Python application](/Monitor-your-data/OpenTelemetry/Instrumentation/Python/) to ship data to OpsPilot. -In the FR Cloud **Explore** window, ensure the `Traces` datasource is selected. Using the `Search` query type, select `Resource Service Name = fib_by_iteration`. Click the **Run Query** button at the top left to execute the query. +In the OpsPilot **Explore** window, ensure the `Traces` datasource is selected. Using the `Search` query type, select `Resource Service Name = fib_by_iteration`. Click the **Run Query** button at the top left to execute the query. Several `fib-outer` spans will appear. Click on one to open the span split view, which displays the inner spans for that execution. Click any inner span on the right to view more information, including the `iteration` attribute set in the code. diff --git a/docs/Troubleshooting/Cloned-FusionReactor-Instances.md b/docs/Troubleshooting/Cloned-FusionReactor-Instances.md index 9922863..42f2e93 100644 --- a/docs/Troubleshooting/Cloned-FusionReactor-Instances.md +++ b/docs/Troubleshooting/Cloned-FusionReactor-Instances.md @@ -4,7 +4,7 @@ All FusionReactor instances have a unique identifier assigned to them when they are first created, in the context of FusionReactor this is called the FRUID. Throughout the versions of FusionReactor, how this FRUID was generated and stored has been altered but the concept of having a FRUID has been consistent. -There is also a GRUID or globally unique identifier assigned to each instance, this is used by external sources such as the **Enterprise Dashboard**, **FusionAnalytics** and the **FusionReactor Cloud**. +There is also a GRUID or globally unique identifier assigned to each instance, this is used by external sources such as the **Enterprise Dashboard**, **FusionAnalytics** and the **OpsPilot**. Cloning FusionReactor refers to two instances of FusionReactor having the same FRUID or GRUID, so they are identified as the same unique instance although there are two distinct copies. @@ -18,7 +18,7 @@ Cloning FusionReactor refers to two instances of FusionReactor having the same F We recommend the base virtual image be fixed so that it will not cause cloned instances to occur. -While with a cloned instance both instances with the same FRUID and GRUID pair will appear to operate as normal, in our external servers such as our licensing server, the **FusionAnalaytics** target and the **FusionReactor Cloud** will see your two or more distinct instances as one single instance. +While with a cloned instance both instances with the same FRUID and GRUID pair will appear to operate as normal, in our external servers such as our licensing server, the **FusionAnalaytics** target and the **OpsPilot** will see your two or more distinct instances as one single instance. When this is the case the following will occur: @@ -26,7 +26,7 @@ When this is the case the following will occur: - In **FusionAnalytics** all data from multiple instances is merged so you won't know if one particular instance is experiencing issues as your metrics will be inaccurate. -- In the **FusionReactor Cloud**, rather than seeing and being able to analyze all your instances, you will only have access to some of your data under one single instance and the rest will not be available to you. +- In the **OpsPilot**, rather than seeing and being able to analyze all your instances, you will only have access to some of your data under one single instance and the rest will not be available to you. ## How to stop instances becoming cloned diff --git a/docs/Troubleshooting/Cloud-find-slow-pages.md b/docs/Troubleshooting/Cloud-find-slow-pages.md index ced55f7..395610c 100644 --- a/docs/Troubleshooting/Cloud-find-slow-pages.md +++ b/docs/Troubleshooting/Cloud-find-slow-pages.md @@ -1,6 +1,6 @@ # How to find data on your slowest traces using Dashboards -FusionReactor Cloud dashboards such as the Request Performance dashboard let you identify your slowest traces by ranking them by total time spent, helping you pinpoint resource-intensive operations in your applications. +OpsPilot dashboards such as the Request Performance dashboard let you identify your slowest traces by ranking them by total time spent, helping you pinpoint resource-intensive operations in your applications. !!! info "This feature is part of OpsPilot" This functionality is available in **OpsPilot**, our cloud-native observability platform. diff --git a/docs/Troubleshooting/Cloud-has-moved.md b/docs/Troubleshooting/Cloud-has-moved.md index 26d43d0..a5ed144 100644 --- a/docs/Troubleshooting/Cloud-has-moved.md +++ b/docs/Troubleshooting/Cloud-has-moved.md @@ -1,6 +1,6 @@ -# FusionReactor Has Moved +# OpsPilot Has Moved -FusionReactor Cloud has relocated to app.fusionreactor.io - if you are having trouble accessing the site, clearing your browser cache or performing a hard refresh should resolve the issue. +OpsPilot has relocated to app.opspilot.com - if you are having trouble accessing the site, clearing your browser cache or performing a hard refresh should resolve the issue. !!! info "This feature is part of OpsPilot" This functionality is available in **OpsPilot**, our cloud-native observability platform. diff --git a/docs/Troubleshooting/Cloud-historical-data.md b/docs/Troubleshooting/Cloud-historical-data.md index 0d2d2ac..2809d06 100644 --- a/docs/Troubleshooting/Cloud-historical-data.md +++ b/docs/Troubleshooting/Cloud-historical-data.md @@ -1,6 +1,6 @@ # How to view historical data -FusionReactor Cloud stores up to 13 months of metric data and up to 30 days of trace and log data, accessible through the Servers view, Applications list, and the Explore feature using the time picker. +OpsPilot stores up to 13 months of metric data and up to 30 days of trace and log data, accessible through the Servers view, Applications list, and the Explore feature using the time picker. !!! info "This feature is part of OpsPilot" This functionality is available in **OpsPilot**, our cloud-native observability platform. diff --git a/docs/Troubleshooting/Cloud-offline.md b/docs/Troubleshooting/Cloud-offline.md index ffb6492..39d5637 100644 --- a/docs/Troubleshooting/Cloud-offline.md +++ b/docs/Troubleshooting/Cloud-offline.md @@ -1,6 +1,6 @@ # How to create an alert for offline servers -This guide explains how to configure alert rules in FusionReactor Cloud that fire when any instance - or a specific job - has been offline for five minutes, using PromQL functions such as `unless` and `absent`. +This guide explains how to configure alert rules in OpsPilot that fire when any instance - or a specific job - has been offline for five minutes, using PromQL functions such as `unless` and `absent`. !!! info "This feature is part of OpsPilot" This functionality is available in **OpsPilot**, our cloud-native observability platform. diff --git a/docs/Troubleshooting/Configuration/FusionReactor-System-Properties.md b/docs/Troubleshooting/Configuration/FusionReactor-System-Properties.md index 327565a..6855e6e 100644 --- a/docs/Troubleshooting/Configuration/FusionReactor-System-Properties.md +++ b/docs/Troubleshooting/Configuration/FusionReactor-System-Properties.md @@ -59,7 +59,7 @@ Property | Default value | Values accepted | Version added | Description {!Common/ED_Sys_Props!} -## FusionReactor Cloud +## OpsPilot Property | Default value | Values accepted | Version added | Description --- | --- | --- | --- | --- @@ -213,7 +213,7 @@ Property | Default value | Version added | Description `fr.jdbc.skip_get_connection_parser`| false | 12.1.0 | Can prevent blocked threads when using JDBC but reduces monitoring capability. `fr.jdbc.connection_parser_type`| MySQL | 12.1.0 | When `-Dfr.jdbc.skip_get_connection_parser=true`, will attempt to parse the connection as the given database type. Currently, only `oracle` and `mysql` are supported. -## FR Cloud UI Tunnel +## OpsPilot UI Tunnel | Property | Default value | Version added | Description | |--------------------|---------------|---------------|--------------------------------------| | `fr.ui.ws.enabled` | true | 12.1.0 | Enable/disable the websocket tunnel. | diff --git a/docs/Troubleshooting/Optimize-data.md b/docs/Troubleshooting/Optimize-data.md index c6e51f0..422769b 100644 --- a/docs/Troubleshooting/Optimize-data.md +++ b/docs/Troubleshooting/Optimize-data.md @@ -1,6 +1,6 @@ # How to reduce trace sampling data and optimize billing costs -This guide explains how to reduce the volume of trace data sent to FusionReactor Cloud by adjusting the sampling ratio on the FusionReactor Java agent, helping you manage costs while maintaining effective observability. +This guide explains how to reduce the volume of trace data sent to OpsPilot by adjusting the sampling ratio on the FusionReactor Java agent, helping you manage costs while maintaining effective observability. !!! info "This feature is part of OpsPilot" This functionality is available in **OpsPilot**, our cloud-native observability platform. diff --git a/docs/Troubleshooting/trouble.md b/docs/Troubleshooting/trouble.md index 27f1408..589517a 100644 --- a/docs/Troubleshooting/trouble.md +++ b/docs/Troubleshooting/trouble.md @@ -1,12 +1,12 @@ # Troubleshooting Cloud connections ## System status -The status of various components of the **FusionReactor Cloud** system can be seen [here](https://fusionreactor-status.freshstatus.io/). +The status of various components of the **OpsPilot** system can be seen [here](https://fusionreactor-status.freshstatus.io/). ## Missing, incomplete or malformed data ### Network issues -FusionReactor is designed to be resilient to connectivity issues when shipping data to **FusionReactor Cloud**. +FusionReactor is designed to be resilient to connectivity issues when shipping data to **OpsPilot**. If your instance of FusionReactor has connectivity issues up to 60 mins of data is kept locally, once connectivity has been restored this data will be shipped intelligently in order to refrain from overloading the transport system. @@ -14,7 +14,7 @@ Data will then appear to 'back fill' and gaps in the data will be removed. ### Live functionality not working correctly -Some functionality of **FusionReactor Cloud** requires a web socket connection to communicate directly with the FusionReactor instance. Examples of this functionality are recent or running transactions and the live graphing modes. +Some functionality of **OpsPilot** requires a web socket connection to communicate directly with the FusionReactor instance. Examples of this functionality are recent or running transactions and the live graphing modes. If you are experiencing issues with these areas of the software then you should refer to the following sections of this guide. @@ -78,16 +78,16 @@ Below is an example using IBM WebSphere, which supplies its own keystore. Adapt ### Firewall -Some users run FusionReactor behind restricted firewalls which do not allow all outbound connections. In this case, these users may need to add specific firewall rules to allow FusionReactor to communicate with **FusionReactor Cloud**. +Some users run FusionReactor behind restricted firewalls which do not allow all outbound connections. In this case, these users may need to add specific firewall rules to allow FusionReactor to communicate with **OpsPilot**. #### Using DNS firewall rules -In order to communicate with **FusionReactor Cloud**, each FusionReactor instance attempts to connect to the following services, which are identified by their DNS names: +In order to communicate with **OpsPilot**, each FusionReactor instance attempts to connect to the following services, which are identified by their DNS names: * wss://cc.fusionreactor.io - port tcp/2804 * https://api.fusionreactor.io - port tcp/443 -These services require outgoing firewall rules for FusionReactor to communicate with FusionReactor Cloud. All communications are protected by SSL cyphers. +These services require outgoing firewall rules for FusionReactor to communicate with OpsPilot. All communications are protected by SSL cyphers. !!! tip If possible, the firewall should be configured with the DNS names of these services, since they can change in response to scaling events. @@ -169,7 +169,7 @@ In order to keep the size of shipped data within an acceptable margin, a culling The algorithm looks at culling subtransactions of the long bucket first, then slow, and then error last. We do it in this order so that the error transactions are less likely to be trimmed because they're most important. -If subtransactions were trimmed from the shipped data, this will be indicated in **FusionReactor Cloud**. +If subtransactions were trimmed from the shipped data, this will be indicated in **OpsPilot**. ___ diff --git a/docs/UI/Overview.md b/docs/UI/Overview.md index 064dcd4..8cba216 100644 --- a/docs/UI/Overview.md +++ b/docs/UI/Overview.md @@ -211,24 +211,24 @@ The Cloud Status icons are only shown in a Cloud-licensed FusionReactor. The Cloud status indicator appears to the left of the clock. The indicator shows you the current status of the instance's connection to -FusionReactor Cloud. +OpsPilot. When a Cloud license is installed, FusionReactor will attempt to make two connection to the Cloud: -- A **Control Channel **connection, which enables FusionReactor Cloud +- A **Control Channel **connection, which enables OpsPilot to interact directly with this instance. This allows FusionReactor to provide immediate responses to requests for data: running transactions, stack traces etc. - A **Metric Transport** connection, which ships historical and - statistical information to FusionReactor Cloud every minute. + statistical information to OpsPilot every minute. |Icon|Status|Meaning| |--- |--- |--- | ||OK|Both the Control Channel and at least one Datapack Transport are available and successfully connected.| -||Degraded|The Control Channel connection has failed, but at least one Metric Transport is successfully uploading periodic data. FusionReactor cloud will show statistical data, but immediate requests for data will not run successfully, and may time out.| -||Degraded|The Metric Transport is failing to upload data, but a Control Channel connection is established. FusionReactor cloud will not show any new statistical data while in this state.| -||Disconnected|Neither the Control Channel nor any Metric Transport could connect to FusionReactor cloud.| +||Degraded|The Control Channel connection has failed, but at least one Metric Transport is successfully uploading periodic data. OpsPilot will show statistical data, but immediate requests for data will not run successfully, and may time out.| +||Degraded|The Metric Transport is failing to upload data, but a Control Channel connection is established. OpsPilot will not show any new statistical data while in this state.| +||Disconnected|Neither the Control Channel nor any Metric Transport could connect to OpsPilot.| FusionReactor only starts attempting to transfer periodic information one minute after startup. If the Datapack Transport cannot connect, but @@ -238,10 +238,10 @@ to a minute after starting up until the first datapack fails. The Cloud menu item can be dropped down to allow access to: - **Configure Cloud**: The user can turn on data obfuscation for data - sent to FusionReactor cloud, and enable **Class Decompiling**, which - allows FusionReactor Cloud to request the source code for Java + sent to OpsPilot, and enable **Class Decompiling**, which + allows OpsPilot to request the source code for Java classes, where this is available. -- **Open Cloud:** Opens the FusionReactor Cloud application in a new +- **Open Cloud:** Opens the OpsPilot application in a new tab or window. - **Status: **Shows the status of the two communications channels, along with some hints to problem resolution (where applicable) and a