Update docs about query API and alerts (#1098)

Author: alexmojaki

docs/guides/web-ui/alerts.md

@@ -26,21 +26,15 @@ On our example, we're going to set up an alert that will trigger when an excepti
 and the route is `/members/{user_id}`.
 
 ```sql
-SELECT * FROM records  -- (1)!
+SELECT trace_id, exception_type, exception_message FROM records  -- (1)!
 WHERE
-    is_exception and  -- (2)!
-    service_name = 'api' and  -- (3)!
-    attributes->>'http.route' = '/members/{user_id}'  -- (4)!
+    is_exception and
+    service_name = 'api' and
+    attributes->>'http.route' = '/members/{user_id}'  -- (2)!
 ```
 
-1. The `SELECT * FROM records` statement is the base query that will be executed. The **records** table contains the spans and logs data.
-
-    You can use this table to filter the data you want to analyze.
-
-2. The `is_exception` field is a boolean field that indicates whether the record is an exception.
-3. The `service_name` field contains the name of the service that generated the record.
-4. The `attributes` field is a [JSONB] field that contains additional information about the record.
-5. In this case, we're using the `http.route` attribute to filter the records by route.
+1. The `SELECT ... FROM records` statement is the base query that will be executed. The **records** table contains the spans and logs data. `trace_id` links to the trace in the live view when viewing the alert run results in the web UI.
+2. The `attributes` field is a JSON field that contains additional information about the record. In this case, we're using the `http.route` attribute to filter the records by route.
 
 The **Time window** field allows you to specify the time range over which the query will be executed.
 
@@ -75,4 +69,3 @@ You can configure an alert by clicking on the **Configuration** button on the ri
 You can update the alert, or delete it by clicking the **Delete** button. If instead of deleting the alert, you want to disable it, you can click on the **Active** switch.
 
 [Slack format]: https://api.slack.com/reference/surfaces/formatting
-[JSONB]: https://www.postgresql.org/docs/current/datatype-json.html

docs/how-to-guides/query-api.md

@@ -144,7 +144,7 @@ client library, such as `requests` in Python. Below are the general steps and an
 
 ### General Steps to Make a Direct HTTP Request
 
-1. **Set the Endpoint URL**: The base URL for the Logfire API is `https://logfire-api.pydantic.dev`.
+1. **Set the Endpoint URL**: The base URL for the Logfire API is `https://logfire-us.pydantic.dev` for accounts in the US region, and `https://logfire-eu.pydantic.dev` for accounts in the EU region.
 
 2. **Add Authentication**: Include the read token in your request headers to authenticate.
    The header key should be `Authorization` with the value `Bearer <your_read_token_here>`.
@@ -162,7 +162,7 @@ You can also use the `Accept` header to specify the desired format for the respo
 import requests
 
 # Define the base URL and your read token
-base_url = 'https://logfire-api.pydantic.dev'
+base_url = 'https://logfire-us.pydantic.dev'  # or 'https://logfire-eu.pydantic.dev' for EU accounts
 read_token = '<your_read_token_here>'
 
 # Set the headers for authentication