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
Copy file name to clipboardExpand all lines: src/content/docs/ai-gateway/guardrails/set-up-guardrail.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,14 +28,14 @@ After enabling Guardrails, you can monitor results through **AI Gateway Logs** i
28
28
29
29
## Error handling and blocked requests
30
30
31
-
When a request is blocked by guardrails, you will receive a structured error response. These indicate whether the issue occurred with the prompt or the model response. Use error codes to differentiate between prompt versus response violations.
31
+
When a request is blocked by guardrails, you will receive a structured error response. These indicate whether the issue occurred with the prompt or the model response. Use error codes to differentiate between prompt versus response violations.
32
32
33
33
-**Prompt blocked**
34
34
-`"code": 2016`
35
35
-`"message": "Prompt blocked due to security configurations"`
36
36
37
37
-**Response blocked**
38
-
-`"code": 2017`
38
+
-`"code": 2017`
39
39
-`"message": "Response blocked due to security configurations"`
40
40
41
41
You should catch these errors in your application logic and implement error handling accordingly.
Copy file name to clipboardExpand all lines: src/content/docs/analytics/account-and-zone-analytics/analytics-with-workers.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ For a breakdown of subrequest traffic (origin facing traffic), you may go to the
31
31
32
32
**Why do I not have any analytics for Workers?**
33
33
34
-
* If you are not currently using Workers (don't have Workers deployed on any routes or filters), we will not have any information to show you.
34
+
* If you are not currently using Workers (do not have Workers deployed on any routes or filters), we will not have any information to show you.
35
35
* If your Worker sends a static response back to the client without ever calling fetch() to an origin, you are not making any subrequests, thus, all traffic will be shown in zone Analytics
Copy file name to clipboardExpand all lines: src/content/docs/analytics/dashboards.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,10 +10,10 @@ Custom dashboards allow you to create tailored dashboards to monitor application
10
10
11
11
Dashboards provide a visual interface that displays key metrics and analytics, helping you monitor and analyze data efficiently. Different dashboards serve different purposes. For example, a security dashboard tracks attack attempts and threats, a performance dashboard monitors API latency and uptime, and a usage dashboard analyzes traffic patterns and user behavior.
12
12
13
-
Different metrics serve distinct roles in providing insights into your application’s performance. For example, total HTTP requests offers an overview of traffic volume, while average response time helps assess application speed. Additionally, usage metrics such as traffic patterns and user behavior provide insight into how users interact with your application. These metrics together enable you to spot trends, identify problems, and make informed, data-driven decisions.
13
+
Different metrics serve distinct roles in providing insights into your application's performance. For example, total HTTP requests offers an overview of traffic volume, while average response time helps assess application speed. Additionally, usage metrics such as traffic patterns and user behavior provide insight into how users interact with your application. These metrics together enable you to spot trends, identify problems, and make informed, data-driven decisions.
14
14
15
15
:::note
16
-
Custom Dashboards is currently available to customers participating in the Log Explorer beta. To begin using custom dashboards, you will first need to request access to [Log Explorer](/logs/log-explorer/).
16
+
Custom Dashboards is currently available to customers participating in the Log Explorer beta. To begin using custom dashboards, you will first need to request access to [Log Explorer](/logs/log-explorer/).
17
17
:::
18
18
19
19
## Create a new dashboard
@@ -29,14 +29,14 @@ Choosing between these options depends on whether you need a quick setup with pr
29
29
30
30
### Create a dashboard from scratch
31
31
32
-
When creating a dashboard from scratch, select the option **Create a new**. You can follow the instructions in the following sections to start adding charts to your dashboard.
32
+
When creating a dashboard from scratch, select the option **Create a new**. You can follow the instructions in the following sections to start adding charts to your dashboard.
33
33
34
34
#### Create a new chart
35
35
36
36
To create a new chart, select **Add chart**. There are two ways to create a chart:
37
37
38
-
-**Use a prompt**: Enter a query like `Compare status code ranges over time`. The AI model decides the most appropriate visualization and constructs your chart configuration.
39
-
-**Customize your chart**: Select the chart elements manually, including the chart type, title, dataset to query, metrics, and filters. This option gives you full control over your chart’s structure.
38
+
-**Use a prompt**: Enter a query like `Compare status code ranges over time.` The AI model decides the most appropriate visualization and constructs your chart configuration.
39
+
-**Customize your chart**: Select the chart elements manually, including the chart type, title, dataset to query, metrics, and filters. This option gives you full control over your chart’s structure.
40
40
41
41
Refer to the following sections for more information about the charts, datasets, fields, metrics, and filters available.
42
42
@@ -79,7 +79,7 @@ Alternatively, you can choose to create your dashboard using a pre-designed dash
79
79
80
80
-**Bot monitoring**: Allows you to identify automated traffic accessing your website.
81
81
-**API Security**: Allows you to monitor data transfers and exceptions for API endpoints in your application.
82
-
-**API Performance**: Allows you to view timing data for API endpoints in your application, along with error rates.
82
+
-**API Performance**: Allows you to view timing data for API endpoints in your application, along with error rates.
83
83
-**Account takeover**: Allows you to monitor login attempts, usage of leaked credentials, and account takeover attacks.
![hyperlint-ai[bot]](https://avatars.githubusercontent.com/in/718456?v=4&size=40){kind=avatar}
0 commit comments