You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add Grafana Cloud Frontend functionality to the Frontend app.
This will allow the use of a Frontend endpoint to be used,
to use Grafana Frontend functionality in Cloud.
The `mythical-server` service has been updated to provide configuration
for the Faro Web SDK to ensure that either a local instance of
Alloy is used for data collection, or Grafana Cloud Frontend.
Signed-off-by: Heds Simons <hedley.simons@grafana.com>
Copy file name to clipboardExpand all lines: README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -211,6 +211,14 @@ Note that this service is optional, and is only currently available in the local
211
211
212
212
Faro is designed to continue to propagate data across frontend sessions to backend server infrastructure, and as such includes the ability to send relevant state information in headers. For traces, this is based open the OpenTelemetry Tracing Specification, and utilises the `tracestate` and `traceparent` headers to propagate data. In the case of this example, this will show traces starting in the `mythical-frontend` service.
213
213
214
+
The default setup is to send Faro data to the local Alloy instance, which will count it as a propagated trace that will include the `mythical-server` service as part of the trace.
215
+
216
+
For Grafana Cloud, using the [`docker-compose-cloud.yml`](docker-compose-cloud.yml) manifest, you can instead use Grafana Frontend to show session data, as well as statistics on user browser data such as time to first byte, etc. To do so, change the following environment variables in the `mythical-server` configuration:
217
+
*`FARO_ENDPOINT` to the URL specified in an initialised Grafana Frontend application project, notably the `url` field in the `Settings -> Web SDK Config` section.
218
+
*`USE_GRAFANA_CLOUD` to `true`.
219
+
This will allow you to send Faro data to Grafana Cloud, and see linked traces and logs as part of Grafana Frontend.
220
+
221
+
214
222
### Beyla
215
223
216
224
Beyla is an eBPF-based tool for generating metrics and trace data without the need for application instrumentation. For more details about Beyla, read the [documentation](https://grafana.com/docs/grafana-cloud/monitor-applications/beyla/).
@@ -333,6 +341,8 @@ This demo can be run against Grafana Cloud by configuring the `alloy/endpoints-c
333
341
334
342
The Grafana Alloy will send all the signals to the Grafana Cloud stack specified in the `alloy/endpoints-cloud.json` file.
335
343
344
+
*Note:* See the [`Faro Web SDK`](#faro-web-sdk) for instructions on how to configure the right URL endpoint to send Faro data to Grafana Frontend. It is *vital* to note that you must configure your browser to disable the same-origin policies to allow the local running of a web-server that will send to Grafana Frontend (and to include `localhost` in your allowed domains). For example, in Chrome you can achieve this with the `--disable-web-security` flag.
345
+
336
346
## Using the OpenTelemetry Collector
337
347
338
348
You can also use an alternative environment that uses the OpenTelemetry Collector in place of Grafana Alloy.
0 commit comments