docs(opspilot): Rename FusionReactor Cloud references to OpsPilot

docs/Admin-and-data/Licensing/Static-Licensing-Endpoints.md

@@ -2,7 +2,7 @@
 
 # Static endpoints
 
-Some users run FusionReactor behind restricted firewalls which don't 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 don't 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
 
@@ -14,7 +14,7 @@ In order to communicate with the FusionReactor infrastructure, each FusionReacto
 
 ### Firewall configuration
 
-- Allow outbound SSL traffic to FusionReactor Cloud services.
+- Allow outbound SSL traffic to OpsPilot services.
 - Configure rules using DNS names (recommended) for automatic updates.
 - If using IP addresses, verify current values with `nslookup`.
 

docs/Admin-and-data/Limits.md

@@ -1,6 +1,6 @@
-# Limit data for FR Cloud ingest
+# Limit data for OpsPilot ingest
 
-FR Cloud enforces rate limits for ingested data.  The ingest system will return `429: Too Many Requests` when this condition occurs; clients can then take appropriate action.
+OpsPilot enforces rate limits for ingested data.  The ingest system will return `429: Too Many Requests` when this condition occurs; clients can then take appropriate action.
 
 ## Metrics
 
@@ -20,4 +20,4 @@ FR Cloud enforces rate limits for ingested data.  The ingest system will return
 
 
 !!! info 
-    [How to reduce billing usage costs in FR Cloud](/Troubleshooting/Optimize-data/)
+    [How to reduce billing usage costs in OpsPilot](/Troubleshooting/Optimize-data/)

docs/Admin-and-data/Third-Party-Licenses/licenses.md

@@ -8,7 +8,7 @@ search:
 
 ## FusionReactor use of Grafana
 
-Parts of **FusionReactor Cloud** use [Grafana](https://grafana.com/) and other open source software.
+Parts of **OpsPilot** use [Grafana](https://grafana.com/) and other open source software.
 
 ### Copyright notice for Grafana
 

docs/Data-insights/Extras/fr-observability-agent.md

@@ -4,7 +4,7 @@
     Installation requires FRAM to be licensed with a valid Cloud license.
 
 ## Introduction
-Starting with FusionReactor 12, the Observability Agent can be installed via FRAM's on-prem UI for a simpler way to configure, and get started with, sending data from non-FusionReactor sources to FusionReactor Cloud.
+Starting with FusionReactor 12, the Observability Agent can be installed via FRAM's on-prem UI for a simpler way to configure, and get started with, sending data from non-FusionReactor sources to OpsPilot.
 
 This enables the ability to analyse metrics within **Explore** and **Integration Dashboards**, providing insight into potential issues concerning your data sources.
 

docs/Data-insights/Features/Logs/Cloud-Settings.md

@@ -108,7 +108,7 @@ Testing your scrape pattern displays a list of matching log files that will now
 
 ## Log exclusion
 
-Log exclusions can exclude any logs sending to the FusionReactor cloud, either for security or to reduce data volume.
+Log exclusions can exclude any logs sending to OpsPilot, either for security or to reduce data volume.
 
 Similar to the scrape pattern you can add a regex pattern match for logs that will be blacklisted from sending, with the option of using the wildcard character: ```*```
 

docs/Data-insights/Features/Logs/Files/Cloud-State-Log.md

@@ -1,6 +1,6 @@
 # Cloud State Log
 
-**Available exclusively with FusionReactor Cloud licenses.**
+**Available exclusively with OpsPilot licenses.**
 
 This log records changes in the state of the **Control Channel**, the cloud connection channel. For a detailed overview of the channel’s status, see the [Cloud Status page](/Monitor-your-data/FR-Agent/Agent/Cloud-Status).
 

docs/Data-insights/Features/Settings/Logging-Cloud.md

@@ -108,7 +108,7 @@ Testing your scrape pattern displays a list of matching log files that will now
 
 ## Log exclusion
 
-Log exclusions can exclude any logs sending to the FusionReactor cloud, either for security or to reduce data volume.
+Log exclusions can exclude any logs sending to OpsPilot, either for security or to reduce data volume.
 
 Similar to the scrape pattern you can add a regex pattern match for logs that will be blacklisted from sending, with the option of using the wildcard character: ```*```
 

docs/Data-insights/Features/Settings/Main-Menu.md

@@ -8,7 +8,7 @@ The FusionReactor Settings page lets you modify the FusionReactor in order to:
 * Secure the FusionReactor API
 * Configure Application and Transaction name detection
 * Configure FusionReactor to either track or ignore specific URLS
-* Configure a proxy for FusionReactor to contact its external servers for licensing and the FusionReactor Cloud
+* Configure a proxy for FusionReactor to contact its external servers for licensing and the OpsPilot
 * Configure which error types should be tracked in FusionReactor
 
 !!! note

docs/Data-insights/Features/timepicker.md

@@ -1,6 +1,6 @@
 # Time picker
 
-The time picker allows users to select the time period they are interested in within certain areas of FusionReactor Cloud. The time picker can be accessed from any screen where it's supported by either: 
+The time picker allows users to select the time period they are interested in within certain areas of OpsPilot. The time picker can be accessed from any screen where it's supported by either: 
 
 * Clicking its icon in the top navigation bar displays the [context menu](timepicker.md#context-menu).
 
@@ -14,7 +14,7 @@ The context menu allows refreshing of data for the current time frame, access to
 
 ### Refresh interval 
 
-The refresh interval controls how often FusionReactor Cloud should poll for new data.
+The refresh interval controls how often OpsPilot should poll for new data.
 
 ## Configuration options
 ![!Screenshot](../../Data-insights/Features/timepicker.png)

docs/Getting-started/set-up-integrations.md

@@ -6,15 +6,15 @@ Welcome to the **Set up integrations** guide. This page introduces the **Observa
 
 ## Observability Agent overview
 
-The **Observability Agent** by FusionReactor is built as a wrapper around **Grafana Alloy**, providing a simplified way to forward metrics from various parts of your tech stack to **FusionReactor Cloud** - all with minimal configuration.
+The **Observability Agent** by FusionReactor is built as a wrapper around **Grafana Alloy**, providing a simplified way to forward metrics from various parts of your tech stack to **OpsPilot** - all with minimal configuration.
 
 
 
 ### Key features
 
 - **Centralized Monitoring**: Collect metrics from across your entire stack - ColdFusion, Java, databases, servers, containers, and more.
 - **Simple Installation**: Deploy quickly using **FRAM**, **Docker**, or install snippets.
-- **Cloud Dashboards**: Visualize data in **Explore** and the **Integration Dashboards** in FusionReactor Cloud.
+- **Cloud Dashboards**: Visualize data in **Explore** and the **Integration Dashboards** in OpsPilot.
 
 
 
@@ -38,7 +38,7 @@ You can monitor a wide variety of infrastructure components using supported expo
 
 #### **Step 1**: Generate an API Key
 
-Head to your [FusionReactor Cloud Account Settings](https://app.fusionreactor.io/account/settings) to create an API key.
+Head to your [OpsPilot Account Settings](https://app.fusionreactor.io/account/settings) to create an API key.
 
 
 #### **Step 2**: Install the Observability Agent
@@ -59,6 +59,6 @@ Choose the appropriate installation method:
 Once installed, your metrics will appear in:
 
 - **Explore**
-- **Integration Dashboards** inside **FusionReactor Cloud**
+- **Integration Dashboards** inside **OpsPilot**
 
 

docs/Latest-updates/Downloads.md

@@ -175,7 +175,7 @@ detect which services are running on your machine, and automatically create a co
 
 ### FRAM
 
-After you have installed or upgraded your FRAM version, you’ll find the Observability Agent installer on the FRAM summary screen. Click the **Install** button, then **Configure Install**, and here you can configure your integrations to start monitoring them with FusionReactor Cloud.
+After you have installed or upgraded your FRAM version, you’ll find the Observability Agent installer on the FRAM summary screen. Click the **Install** button, then **Configure Install**, and here you can configure your integrations to start monitoring them with OpsPilot.
 
 !!! note
     To install the Observability Agent via FRAM, you must have a minimum version of FusionReactor 12.
@@ -248,7 +248,7 @@ Change `CLUSTER_NAME` to your Kubernetes cluster name.
 
 - `fr-cloud-authentication-secret.yaml`
 
-Change `PASSWORD` to your FR Cloud API key. 
+Change `PASSWORD` to your OpsPilot API key. 
 
 **Step 3**: Run the following commands to create a new namespace to hold & deploy stack 
 

docs/Monitor-your-data/FR-Agent/Agent/Cloud-Status.md

@@ -35,13 +35,12 @@ the system changes from Degraded to **Failed**.
 ## Control Channel
 
 The **Control Channel **is used to provided a two-way communications
-channel between FusionReactor and FusionReactor Cloud.  It's used to
+channel between FusionReactor and OpsPilot.  It's used to
 provide immediate, accurate information to the Cloud and is the basis
 for real-time functionality like **Stack trace**, **Running
 Requests **etc.
 
-This channel is established between FusionReactor and FusionReactor
-Cloud when the instance starts.  FusionReactor tries to keep this
+This channel is established between FusionReactor and OpsPilot when the instance starts.  FusionReactor tries to keep this
 channel open as long as the instance is running, and will attempt to
 reconnect it if it becomes unavailable.
 
@@ -53,7 +52,7 @@ when you can expect to see that item.
 |Text|Appears|Description|
 |--- |--- |--- |
 |Status|Always|A short description about the state of the connection.|
-|Endpoint|Always|A URL describing the server, protocol and port used by this instance to establish a connection to FusionReactor Cloud|
+|Endpoint|Always|A URL describing the server, protocol and port used by this instance to establish a connection to OpsPilot|
 |Connected Since|Connected|A date/time string representing the instant at which the connection was established.|
 |Disconnected Since|Disconnected|A date/time string representing the instant at which the connection was lost.|
 |Attempting to Reconnect|Disconnected|Yes/No. Indicates whether the Control Channel system is attempting to reconnect. This should normally be Yes. Some types of forced disconnect may result in No, however. If this is the case, FusionReactor will attempt to reestablish the connection only on the next instance restart.|
@@ -65,13 +64,13 @@ when you can expect to see that item.
 |--- |--- |--- |
 |Network - DNS|An exception of the form "Can't resolve xx.yy"|The endpoint couldn't be resolved from a name into an IP address. <br><br>Ensure the instance is configured to use a DNS server that can resolve standard IP4 internet addresses.<br>Ensure the instance is connected to the network.|
 |Network - Connection|An exception of the form "Couldn't connect to xx.yy" or "Timed out connecting to xx.yy"|The endpoint couldn't be contacted.<br><br>Ensure the instance is connected to the network.<br>Ensure the instance can connect through your firewall to the Control Channel. Information on required firewall punches and static routing (if required) can be found in technote [FRS-418] FusionReactor Cloud Firewall DNS and Static IP address rules.
-FusionReactor Cloud may be experience network connectivity issues. In this case, the connection will be periodically retried by FusionReactor, and will reconnect up to a maximum of one minute after FusionReactor Cloud becomes available.|
+OpsPilot may be experience network connectivity issues. In this case, the connection will be periodically retried by FusionReactor, and will reconnect up to a maximum of one minute after OpsPilot becomes available.|
 
 ## Telemetry Shippers
 
 The **Telemetry Shippers** periodically collect useful information, such as metrics, logs and spans/traces (transactions),
 gathered by the FusionReactor agent, packages them
-into the appropriate form and sends them to the Cloud.  FusionReactor Cloud then ingests this data and makes it
+into the appropriate form and sends them to the Cloud.  OpsPilot then ingests this data and makes it
 available to you in various useful forms.
 
 PrometheusRemoteWriteShipper is responsible for metrics, LogShipper for logs and SpanShipper for spans/traces (transactions).
@@ -81,7 +80,7 @@ transferred are stored in a queue (one for each shipper).  These queues have a
 earlier data requests are dropped to make room for newer ones.
 
 When the connection returns, the Telemetry Shippers sends any queued requests.  During the period of outage, you
-may see holes appearing in data within FusionReactor Cloud.  Once
+may see holes appearing in data within OpsPilot.  Once
 these messages start flowing again, these void areas should close.  While this backfill
 occurs, you may see a **Metric Lag Warning** on this page.
 

docs/Monitor-your-data/FR-Agent/Configuration/FusionReactor-System-Properties.md

@@ -84,7 +84,7 @@ fr.ed.ds.target | Not defined | hostname:port | 8.1.0 | If specified, causes the
 fr.ed.ds.groups | Not defined | Comma-separated list | 8.1.0 | If provided, the instance will auto-register with the ED DS, specifying it is a part of the given groups.
 
 
-## FusionReactor Cloud
+## OpsPilot
 
 Property | Default value | Values accepted | Version added | Description
 --- | --- | --- | --- | ---
@@ -215,7 +215,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. |

docs/Monitor-your-data/FR-Agent/Configuration/OTel-shipping-config.md

@@ -2,14 +2,14 @@
 
 ## Overview
 
-The FusionReactor agent now supports shipping observability data to any OpenTelemetry (OTel) compatible provider. By default, the agent ships to FusionReactor Cloud, but you can configure it to send data to any single OTel endpoint or use an OTel collector or Grafana Alloy to send data to multiple destinations simultaneously.
+The FusionReactor agent now supports shipping observability data to any OpenTelemetry (OTel) compatible provider. By default, the agent ships to OpsPilot, but you can configure it to send data to any single OTel endpoint or use an OTel collector or Grafana Alloy to send data to multiple destinations simultaneously.
 
 <div style="padding:56.25% 0 0 0;position:relative;"><iframe src="https://player.vimeo.com/video/1139978038?badge=0&amp;autopause=0&amp;player_id=0&amp;app_id=58479" frameborder="0" allow="autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share" referrerpolicy="strict-origin-when-cross-origin" style="position:absolute;top:0;left:0;width:100%;height:100%;" title="OTel Shipping Configuration"></iframe></div><script src="https://player.vimeo.com/api/player.js"></script>
 
 ## Key Concepts
 
 ### Default behavior
-- **FusionReactor Cloud is the default destination** - no configuration needed.
+- **OpsPilot is the default destination** - no configuration needed.
 - All metrics, traces, and logs are automatically shipped to FusionReactor.
 
 ### Single endpoint shipping

docs/Monitor-your-data/FR-Agent/Installation/Docker.md

@@ -58,8 +58,7 @@ RUN mkdir -p /opt/fusionreactor/instance/{Instance Name}/conf
 ```
 
 ## System properties to add to a container
-FusionReactor has System properties to configure the instance password, license key, Enterprise Dashboard and FusionReactor
- Cloud. These arguments can be found in [FusionReactor System Properties](../Configuration/FusionReactor-System-Properties.md).
+FusionReactor has System properties to configure the instance password, license key, Enterprise Dashboard and OpsPilot. These arguments can be found in [FusionReactor System Properties](../Configuration/FusionReactor-System-Properties.md).
 
 ## Persisting log files using Docker volumes
 To persist the FusionReactor logs outside of the container, you can use a Docker volume so that logs are stored on the host machine. For example:

docs/Monitor-your-data/FR-Agent/More/Distributed-Tracing/attributes.md

@@ -10,7 +10,7 @@ Attributes are information providing extra insight into the span.
 !!! note "Potential cause of truncated attribute values"
     An attribute value ending in `...` indicates that it has been truncated to limit data size.
 
-## FusionReactor Cloud UI attributes
+## OpsPilot UI attributes
 These are attributes required for transaction rendering in FusionReactor's Cloud UI.
 
 | Attribute Key/Name | Attribute Value |
@@ -118,7 +118,7 @@ Add to JVM arguments/options by prepending with `-D`.
 
 | Property key | Default | Description |
 | -- | -- | -------- |
-| `fr.observability.trace.attributes.datapack.enabled` | `true` | If enabled, sets datapack (cloud UI) attributes on spans. WARNING: Transactions/spans will no longer be rendered in the FusionReactor Cloud UI. |
+| `fr.observability.trace.attributes.datapack.enabled` | `true` | If enabled, sets datapack (cloud UI) attributes on spans. WARNING: Transactions/spans will no longer be rendered in the OpsPilot UI. |
 | `fr.observability.trace.attributes.datapack.obfuscation.enabled`  | `false`  | If enabled, attempts to obfuscate datapack span attributes. |
 | `fr.observability.trace.attributes.semantics.enabled`             | `true`  | If enabled, sets semantic attributes on spans. |
 | `fr.observability.trace.attributes.semantics.obfuscation.enabled` | `false` | If enabled, doesn't set or obfuscates `net.peer.port`, `net.peer.name`, `net.peer.ip`, `db.statement`, query string in `http.url` (for FusionRequest/WebRequests), `http.client_ip`, and `db.cassandra.coordinator.dc` semantic attributes. |

docs/Monitor-your-data/Katie/install.md

@@ -98,7 +98,7 @@ For Claude Desktop, the configuration to communicate with this is:
 
 ## Configuring Claude Code
 
-This configuration uses the **MCP** in a local Docker container to connect to **FusionReactor Cloud**.
+This configuration uses the **MCP** in a local Docker container to connect to **OpsPilot**.
 
 ### 1. Start the Docker container locally
 
@@ -145,7 +145,7 @@ claude mcp list
 
 | Prompt | Description |
 |-------|-------------|
-| `What clusters are connected?` | See what clusters are connected via their Katie Agents to FusionReactor Cloud. |
+| `What clusters are connected?` | See what clusters are connected via their Katie Agents to OpsPilot. |
 | `What namespaces are available?` | Self-explanatory. |
 | `List all the pods in the 'otel-demo' namespace, along with their resource requirements and usage.` | Self-explanatory. |
 | `Are any pods in trouble?` | Gets a short summary of any pod problems. |

docs/Monitor-your-data/Katie/overview.md

@@ -34,13 +34,13 @@ ip-172-20-6-214 is at risk - no pod scheduling capacity remaining.
 ## Prerequisites
 
 * Katie consists of two elements: an agent, which runs in your Kubernetes cluster, and an MCP tool, which you run locally on your computer.  
-* Communication between the two is facilitated by **FusionReactor Cloud**.
+* Communication between the two is facilitated by **OpsPilot**.
 
 ## Next Steps: Install Katie Components
 
 ### Katie Agent
 
-The Katie Agent is a single pod that runs inside your cluster and responds to live data requests from FusionReactor Cloud.
+The Katie Agent is a single pod that runs inside your cluster and responds to live data requests from OpsPilot.
 
 As a cluster administrator, you’ll need to install the Katie Agent in each Kubernetes cluster you want to integrate with AI. The easiest way to do this is by using our Helm chart. Installation instructions are available on our [GitHub repository](https://github.com/intergral/katie-helm).