rename logs for clarity

This commit is contained in:
miloschwartz
2026-04-20 15:05:24 -07:00
parent aafbc1c6d2
commit 4743b56ff1
4 changed files with 38 additions and 38 deletions

View File

@@ -1,6 +1,6 @@
---
title: "Access Logs"
description: "Access logs are a record of each access attempt to a Pangolin resource"
title: "Authentication Logs"
description: "Authentication logs are a record of each authenticated access attempt to a resource"
---
import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
@@ -9,15 +9,15 @@ import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
Access logs provide detailed information about each access attempt made to your Pangolin resources. These logs help you monitor and analyze user activity each time they attempt to authenticate.
Authentication logs provide detailed information about each access attempt made to your Pangolin resources. These logs help you monitor and analyze user activity each time they attempt to authenticate.
<Note>
Access logs are only available in [Pangolin Cloud](https://app.pangolin.net/auth/signup) or self-hosted [Enterprise Edition](/self-host/enterprise-edition).
Authentication logs are only available in [Pangolin Cloud](https://app.pangolin.net/auth/signup) or self-hosted [Enterprise Edition](/self-host/enterprise-edition).
</Note>
## What are Access Logs?
## What are Authentication Logs?
Access logs capture authentication events when users or API keys attempt to access a resource. They record whether the authentication was successful or failed, along with contextual information about the attempt. These logs are useful for:
Authentication logs capture authentication events when users or API keys attempt to access a resource. They record whether the authentication was successful or failed, along with contextual information about the attempt. These logs are useful for:
- Monitoring authentication patterns and login attempts
- Tracking which users are accessing which resources
@@ -29,11 +29,11 @@ Access logs capture authentication events when users or API keys attempt to acce
<img src="/images/access_logs.png" centered/>
</Frame>
<Tip>Make sure to enable access logs in the org settings</Tip>
<Tip>Make sure to enable authentication logs in the org settings</Tip>
## Access Log Fields
## Authentication Log Fields
Each access log entry contains the following fields:
Each authentication log entry contains the following fields:
| Field | Type | Description |
|-------|------|-------------|
@@ -51,7 +51,7 @@ Each access log entry contains the following fields:
## Log Retention
Access log retention is controlled by the organization setting. By default, access logs are retained for 0 days (disabled).
Authentication log retention is controlled by the organization setting. By default, authentication logs are retained for 0 days (disabled).
## Exporting

View File

@@ -1,6 +1,6 @@
---
title: "Action Logs"
description: "Action logs are a record of each event taken by users in the Pangolin system"
title: "Admin Action Logs"
description: "Admin Action logs are a record of each event taken by users in the organization"
---
import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
@@ -9,15 +9,15 @@ import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
Action logs provide an audit trail of administrative actions and configuration changes made within your Pangolin organization. These logs help you track who made what changes and when.
Admin Action logs provide an audit trail of administrative actions and configuration changes made within your Pangolin organization. These logs help you track who made what changes and when.
<Note>
Action logs are only available in [Pangolin Cloud](https://app.pangolin.net/auth/signup) or self-hosted [Enterprise Edition](/self-host/enterprise-edition).
Admin Action logs are only available in [Pangolin Cloud](https://app.pangolin.net/auth/signup) or self-hosted [Enterprise Edition](/self-host/enterprise-edition).
</Note>
## What are Action Logs?
## What are Admin Action Logs?
Action logs capture administrative events and configuration changes performed by users or API keys in the Pangolin dashboard. They record management operations such as creating resources, modifying settings, managing users, and other organizational changes. These logs are useful for:
Admin Action logs capture administrative events and configuration changes performed by users or API keys in the Pangolin dashboard. They record management operations such as creating resources, modifying settings, managing users, and other organizational changes. These logs are useful for:
- Maintaining an audit trail of configuration changes
- Tracking administrative actions for compliance
@@ -31,7 +31,7 @@ Action logs capture administrative events and configuration changes performed by
<Tip>Make sure to enable access logs in the org settings</Tip>
## Action Log Fields
## Admin Action Log Fields
Each action log entry contains the following fields:
@@ -46,7 +46,7 @@ Each action log entry contains the following fields:
## Log Retention
Action log retention is controlled by the organization settings. By default, action logs are retained for 0 days (disabled).
Admin Action log retention is controlled by the organization settings. By default, admin action logs are retained for 0 days (disabled).
## Exporting

View File

@@ -1,21 +1,21 @@
---
title: "Connection Logs"
description: "Connection logs are a record of TCP and UDP sessions between Pangolin clients and private site resources"
title: "Network Logs"
description: "Network logs are a record of TCP and UDP sessions between clients and private resources on sites"
---
import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
<PangolinCloudTocCta />
Connection logs record each TCP and UDP session that traverses the tunnel between Pangolin clients and resources on your sites. They apply to private resources reached through the Pangolin client (and related tunnel traffic), not to public resources served only through the reverse proxy. You can see which clients and users opened sessions to which private resources, the source and destination addresses and protocols (TCP and UDP), the start and end times of the sessions, and more.
Network logs record each TCP and UDP session that traverses the tunnel between Pangolin clients and resources on your sites. They apply to private resources reached through the Pangolin client (and related tunnel traffic), not to public resources served only through the reverse proxy. You can see which clients and users opened sessions to which private resources, the source and destination addresses and protocols (TCP and UDP), the start and end times of the sessions, and more.
<Note>
Connection logs are only available in [Pangolin Cloud](https://app.pangolin.net/auth/signup) or self-hosted [Enterprise Edition](/self-host/enterprise-edition).
Network logs are only available in [Pangolin Cloud](https://app.pangolin.net/auth/signup) or self-hosted [Enterprise Edition](/self-host/enterprise-edition).
</Note>
## What are Connection Logs?
## What are Network Logs?
Connection logs capture tunnel sessions from clients to private resources. They are useful for:
Network logs capture tunnel sessions from clients to private resources. They are useful for:
- Observing which clients and users opened sessions to which private resources
- Reviewing source and destination addresses and protocols (TCP and UDP)
@@ -23,11 +23,11 @@ Connection logs capture tunnel sessions from clients to private resources. They
- Auditing session start and end times for troubleshooting and compliance
<Tip>Make sure to enable connection logging in the org settings</Tip>
<Tip>Make sure to enable network logging in the org settings</Tip>
## Connection Log Fields
## Network Log Fields
Each connection log entry contains the following fields:
Each network log entry contains the following fields:
| Field | Type | Description |
|-------|------|-------------|
@@ -44,10 +44,10 @@ Each connection log entry contains the following fields:
## Log Retention
Connection log retention is controlled by the organization setting. By default, connection logs are retained for 0 days (disabled).
Network log retention is controlled by the organization setting. By default, network logs are retained for 0 days (disabled).
<Note>
Connection logs can generate significant data volume depending on session churn and traffic. Consider your storage capacity when configuring retention periods.
Network logs can generate significant data volume depending on session churn and traffic. Consider your storage capacity when configuring retention periods.
</Note>
## Exporting

View File

@@ -1,5 +1,5 @@
---
title: "Request Logs"
title: "HTTPS Request Logs"
description: "Request logs are a record of each HTTP request to a resource"
---
@@ -9,11 +9,11 @@ import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
Request logs provide detailed information about every HTTP request made to your Pangolin resources. These logs capture both successful and denied requests along with comprehensive request metadata.
HTTPS Request logs provide detailed information about every HTTP request made to your Pangolin resources. These logs capture both successful and denied requests along with comprehensive request metadata.
## What are Request Logs?
## What are HTTPS Request Logs?
Request logs capture every HTTP request that passes through Pangolin's reverse proxy, including the request details, the decision made (allow or deny), and the reason for that decision. These logs are useful for:
HTTPS Request logs capture every HTTPS request that passes through a reverse proxy, including the request details, the decision made (allow or deny), and the reason for that decision. These logs are useful for:
- Monitoring traffic patterns and request volumes
- Debugging access issues and rule configurations
@@ -26,9 +26,9 @@ Request logs capture every HTTP request that passes through Pangolin's reverse p
<img src="/images/request_logs.png" centered/>
</Frame>
## Request Log Fields
## HTTPS Request Log Fields
Each request log entry contains the following fields:
Each HTTPS request log entry contains the following fields:
| Field | Type | Description |
|-------|------|-------------|
@@ -54,12 +54,12 @@ Each request log entry contains the following fields:
## Log Retention
Request log retention is controlled by the organization setting. By default, request logs are retained for 7 days.
HTTPS Request log retention is controlled by the organization setting. By default, HTTPS request logs are retained for 7 days.
<Note>
Request logs can generate significant data volume depending on your traffic. Consider your storage capacity when configuring retention periods.
HTTPS Request logs can generate significant data volume depending on your traffic. Consider your storage capacity when configuring retention periods.
</Note>
## Exporting
Logs can be exported into CSV format for external analysis and archival. Logs can be exported from the table view in the Pangolin dashboard or via the Pangolin API. When exporting, you can specify date ranges and filters to narrow down the logs you need.
Logs can be exported into CSV format for external analysis and archival. Logs can be exported from the table view in the Pangolin dashboard or via the Pangolin API. When exporting, you can specify date ranges and filters to narrow down the logs you need.