📝 docs: Add documentation
This commit is contained in:
web@ppanel
@@ -0,0 +1,136 @@
|
||||
<div v-pre>
|
||||
|
||||
# Balance Log
|
||||
|
||||
View user balance change records including recharges, consumption, rewards, and all balance operations.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### User
|
||||
User with balance change (clickable for details).
|
||||
|
||||
### Amount
|
||||
Balance change amount:
|
||||
- Positive for increase
|
||||
- Negative for decrease
|
||||
|
||||
### Order No.
|
||||
Associated order number (clickable for order details).
|
||||
|
||||
### Balance
|
||||
User balance after change.
|
||||
|
||||
### Type
|
||||
Balance change type (displayed as Badge):
|
||||
|
||||
**Traffic Reset (23x)**:
|
||||
- Auto Reset (231)
|
||||
- Advance Reset (232)
|
||||
- Paid Reset (233)
|
||||
|
||||
**Recharge/Withdrawal (32x)**:
|
||||
- Recharge (321)
|
||||
- Withdraw (322)
|
||||
- Payment (323)
|
||||
- Refund (324)
|
||||
- Reward (325)
|
||||
- Admin Adjust (326)
|
||||
|
||||
**Purchase (33x)**:
|
||||
- Purchase (331)
|
||||
- Renewal (332)
|
||||
- Refund (333)
|
||||
- Withdraw (334)
|
||||
- Admin Adjust (335)
|
||||
|
||||
**Adjustment (34x)**:
|
||||
- Increase (341)
|
||||
- Reduce (342)
|
||||
|
||||
### Time
|
||||
Balance change time.
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Date Filter
|
||||
Select date to view balance records, defaults to today.
|
||||
|
||||
### User ID Filter
|
||||
Input user ID to view that user's balance changes.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's Recharges
|
||||
|
||||
1. Shows today's balance records by default
|
||||
2. Filter by "Recharge" type
|
||||
3. Calculate total recharge amount
|
||||
4. Analyze recharging users
|
||||
|
||||
### Scenario 2: Track User Balance
|
||||
|
||||
**View User Consumption**:
|
||||
1. Filter by user ID
|
||||
2. View all balance changes
|
||||
3. Analyze spending habits
|
||||
4. Verify billing accuracy
|
||||
|
||||
### Scenario 3: Investigate Abnormal Transactions
|
||||
|
||||
**Check Large Amounts**:
|
||||
1. Browse balance records
|
||||
2. Focus on large recharges/expenses
|
||||
3. Click order number for details
|
||||
4. Verify transaction legitimacy
|
||||
|
||||
### Scenario 4: Admin Balance Adjustment
|
||||
|
||||
**Verify After Manual Adjustment**:
|
||||
1. Filter "Admin Adjust" type
|
||||
2. View adjustment records
|
||||
3. Verify adjustment correctness
|
||||
4. Notify user (if needed)
|
||||
|
||||
## Balance Type Description
|
||||
|
||||
### Recharge Related
|
||||
- **Recharge**: User recharges via payment channel
|
||||
- **Reward**: Referral reward, event reward
|
||||
- **Refund**: Order refund to balance
|
||||
|
||||
### Consumption Related
|
||||
- **Purchase**: Buy new plan
|
||||
- **Renewal**: Renew existing plan
|
||||
- **Payment**: Other payment operations
|
||||
|
||||
### Adjustment Related
|
||||
- **Admin Adjust**: Manually increase or decrease balance
|
||||
- **Withdraw**: User requests withdrawal (deducts balance)
|
||||
|
||||
## Financial Reconciliation
|
||||
|
||||
### Daily Reconciliation
|
||||
Check daily:
|
||||
1. Total recharge matches payment platform
|
||||
2. Total consumption matches order total
|
||||
3. No abnormal large changes
|
||||
4. Refund records complete
|
||||
|
||||
### Monthly Reconciliation
|
||||
Monthly summary:
|
||||
1. Total recharge amount
|
||||
2. Total consumption amount
|
||||
3. Total balance change
|
||||
4. Transaction fee expenses
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention time per system config
|
||||
2. **Amount Sign**: Pay attention to positive/negative meaning
|
||||
3. **Order Association**: Can trace source with order number
|
||||
4. **Type Recognition**: Quickly identify operations by type code
|
||||
5. **Balance Snapshot**: Records balance after change
|
||||
6. **Admin Operations**: Admin adjustments are recorded
|
||||
7. **Regular Reconciliation**: Recommended daily financial verification
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,80 @@
|
||||
<div v-pre>
|
||||
|
||||
# Commission Log
|
||||
|
||||
View user referral commission records including commission sources and amounts.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### User
|
||||
User receiving commission (clickable for details).
|
||||
|
||||
### Amount
|
||||
Commission amount.
|
||||
|
||||
### Order No.
|
||||
Order that generated commission (clickable for order details).
|
||||
|
||||
### Type
|
||||
Commission type (displayed as Badge):
|
||||
- Referral commission
|
||||
- Cashback commission
|
||||
- Reward commission
|
||||
- Other types
|
||||
|
||||
### Time
|
||||
Commission issued time.
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Date Filter
|
||||
Select date to view commission records, defaults to today.
|
||||
|
||||
### User ID Filter
|
||||
Input user ID to view that user's commission records.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's Commissions
|
||||
|
||||
1. Shows today's commission records by default
|
||||
2. Calculate total commission amount
|
||||
3. Analyze referral effectiveness
|
||||
|
||||
### Scenario 2: Track User Commissions
|
||||
|
||||
**View Referral Earnings**:
|
||||
1. Filter by user ID
|
||||
2. View all commission records
|
||||
3. Calculate cumulative earnings
|
||||
4. Verify commission accuracy
|
||||
|
||||
### Scenario 3: Analyze Referral Performance
|
||||
|
||||
**Calculate Referral Data**:
|
||||
1. Select time range
|
||||
2. View commission records
|
||||
3. Identify top referrers
|
||||
4. Optimize referral strategy
|
||||
|
||||
## Commission Rules
|
||||
|
||||
### Commission Sources
|
||||
- **Referral Commission**: Generated from referred user purchases
|
||||
- **Cashback Commission**: Cashback from own purchases
|
||||
- **Reward Commission**: Activity rewards
|
||||
|
||||
### Commission Calculation
|
||||
- Percentage of order amount
|
||||
- Real-time or periodic settlement
|
||||
- Linked to original order
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention per system config
|
||||
2. **Order Association**: Can trace commission source
|
||||
3. **Type Recognition**: Quick categorization by type
|
||||
4. **Real-time Stats**: View referral effectiveness
|
||||
5. **Regular Reconciliation**: Verify commission issuance accuracy
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,149 @@
|
||||
<div v-pre>
|
||||
|
||||
# Email Log
|
||||
|
||||
View all email records sent by the system including sending status and content.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### Platform
|
||||
Email sending platform (displayed as Badge):
|
||||
- SMTP
|
||||
- SendGrid
|
||||
- Mailgun
|
||||
- AWS SES
|
||||
- Other email providers
|
||||
|
||||
### To
|
||||
Recipient email address.
|
||||
|
||||
### Subject
|
||||
Email subject.
|
||||
|
||||
### Content
|
||||
Email content (displayed as JSON):
|
||||
- Plain text content
|
||||
- HTML content
|
||||
- Template variables
|
||||
- Max width 480px
|
||||
|
||||
### Status
|
||||
Email sending status (displayed as Badge):
|
||||
- **Sent** (Green) - Successfully sent
|
||||
- **Failed** (Red) - Send failed
|
||||
- **Unknown** (Gray) - Unknown status
|
||||
|
||||
### Time
|
||||
Email sending time.
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Keyword Search
|
||||
Search recipient address or email subject.
|
||||
|
||||
### Date Filter
|
||||
Select date to view email records, defaults to today.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's Emails
|
||||
|
||||
1. Shows today's email records by default
|
||||
2. Check sending quantity
|
||||
3. Check sending status
|
||||
4. Calculate success rate
|
||||
|
||||
### Scenario 2: Investigate Send Failures
|
||||
|
||||
**Check Failed Emails**:
|
||||
1. Filter "Failed" status
|
||||
2. View recipient addresses
|
||||
3. Check email content
|
||||
4. Analyze failure reasons
|
||||
5. Resend or fix configuration
|
||||
|
||||
### Scenario 3: Verify Email Content
|
||||
|
||||
**Check Email Templates**:
|
||||
1. Search specific subject
|
||||
2. View email content
|
||||
3. Verify variable replacement
|
||||
4. Confirm format correctness
|
||||
|
||||
### Scenario 4: Track User Emails
|
||||
|
||||
**View User Received Emails**:
|
||||
1. Search user email
|
||||
2. View all emails
|
||||
3. Confirm delivery
|
||||
4. Verify email types
|
||||
|
||||
## Email Types
|
||||
|
||||
### System Emails
|
||||
- Registration verification
|
||||
- Password reset
|
||||
- Login verification code
|
||||
- Account notifications
|
||||
|
||||
### Marketing Emails
|
||||
- Promotional emails
|
||||
- Activity notifications
|
||||
- Offer information
|
||||
- Product updates
|
||||
|
||||
### Transactional Emails
|
||||
- Order confirmation
|
||||
- Payment success
|
||||
- Invoice notification
|
||||
- Expiration reminder
|
||||
|
||||
## Sending Monitoring
|
||||
|
||||
### Success Rate Monitoring
|
||||
Watch metrics:
|
||||
- Daily total sent
|
||||
- Send success rate
|
||||
- Failure rate trends
|
||||
- Platform-specific performance
|
||||
|
||||
### Exception Handling
|
||||
When issues found:
|
||||
1. Check SMTP configuration
|
||||
2. Verify email provider status
|
||||
3. Check rate limits
|
||||
4. Review error logs
|
||||
|
||||
## Email Content Description
|
||||
|
||||
### JSON Format
|
||||
Content field contains:
|
||||
```json
|
||||
{
|
||||
"text": "Plain text content",
|
||||
"html": "<p>HTML content</p>",
|
||||
"variables": {
|
||||
"username": "Username",
|
||||
"code": "Verification code"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Variable Replacement
|
||||
- {{username}}: Username
|
||||
- {{code}}: Verification code
|
||||
- {{link}}: Link address
|
||||
- {{expire}}: Expiration time
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention per system config
|
||||
2. **Content Truncation**: Long content may be truncated
|
||||
3. **JSON Display**: Content shown as JSON format
|
||||
4. **Platform Recognition**: Identify sending channel by platform field
|
||||
5. **Status Monitoring**: Watch for failed send records
|
||||
6. **Privacy Protection**: Email content may contain sensitive info
|
||||
7. **Regular Checks**: Daily sending status review
|
||||
8. **Quota Management**: Mind email provider quota limits
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,129 @@
|
||||
<div v-pre>
|
||||
|
||||
# Gift Log
|
||||
|
||||
View traffic, duration, balance gift records including gift sources and remarks.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### User
|
||||
User receiving gift (clickable for details).
|
||||
|
||||
### Subscribe
|
||||
Associated subscription ID (clickable for subscription details).
|
||||
|
||||
### Order No.
|
||||
Associated order number (clickable for order details).
|
||||
|
||||
### Amount
|
||||
Gift amount (shown for balance gifts).
|
||||
|
||||
### Balance
|
||||
User balance after gift.
|
||||
|
||||
### Type
|
||||
Gift type (displayed as Badge):
|
||||
- Traffic gift
|
||||
- Duration gift
|
||||
- Balance gift
|
||||
- Activity gift
|
||||
- Admin gift
|
||||
|
||||
### Remark
|
||||
Gift remark description.
|
||||
|
||||
### Time
|
||||
Gift time.
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Date Filter
|
||||
Select date to view gift records, defaults to today.
|
||||
|
||||
### User ID Filter
|
||||
Input user ID to view that user's gift records.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's Gifts
|
||||
|
||||
1. Shows today's gift records by default
|
||||
2. Calculate gift quantity
|
||||
3. Analyze gift costs
|
||||
|
||||
### Scenario 2: Track User Gifts
|
||||
|
||||
**View User Received**:
|
||||
1. Filter by user ID
|
||||
2. View all gift records
|
||||
3. Verify gifts credited
|
||||
4. Check gift sources
|
||||
|
||||
### Scenario 3: Verify Activity Gifts
|
||||
|
||||
**Verify Activity Distribution**:
|
||||
1. Filter by activity time
|
||||
2. View gift records
|
||||
3. Check distribution quantity
|
||||
4. Verify remark information
|
||||
|
||||
### Scenario 4: Admin Gift Records
|
||||
|
||||
**View Manual Gifts**:
|
||||
1. Filter "Admin Gift" type
|
||||
2. View gift records
|
||||
3. Verify operation correctness
|
||||
4. Check remark reasons
|
||||
|
||||
## Gift Type Description
|
||||
|
||||
### Traffic Gift
|
||||
- Gift traffic package
|
||||
- Increase subscription traffic
|
||||
- Shown in subscription details
|
||||
|
||||
### Duration Gift
|
||||
- Extend subscription time
|
||||
- Add valid days
|
||||
- Shown in subscription details
|
||||
|
||||
### Balance Gift
|
||||
- Gift account balance
|
||||
- Can be used to buy plans
|
||||
- Shows amount and balance
|
||||
|
||||
### Activity Gift
|
||||
- Marketing activity rewards
|
||||
- Batch distribution
|
||||
- With activity remarks
|
||||
|
||||
### Admin Gift
|
||||
- Manual gift operation
|
||||
- Requires reason remark
|
||||
- For compensation or rewards
|
||||
|
||||
## Cost Analysis
|
||||
|
||||
### Gift Statistics
|
||||
Daily/monthly stats:
|
||||
1. Total traffic gifted
|
||||
2. Total days gifted
|
||||
3. Total balance gifted
|
||||
4. Statistics by type
|
||||
|
||||
### Effect Evaluation
|
||||
- User retention after gifts
|
||||
- User payment after gifts
|
||||
- ROI analysis
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention per system config
|
||||
2. **Subscription Association**: Traffic and duration gifts linked to subscriptions
|
||||
3. **Balance Records**: Balance gifts record amount changes
|
||||
4. **Remark Important**: Manual gifts must have remarks
|
||||
5. **Type Recognition**: Distinguish gift sources by type
|
||||
6. **Cost Statistics**: Regularly analyze gift costs
|
||||
7. **Prevent Abuse**: Watch for abnormally large gifts
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,93 @@
|
||||
<div v-pre>
|
||||
|
||||
# Login Log
|
||||
|
||||
View user login records including login methods, IP addresses, and device information.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### User
|
||||
Logged in user, displays:
|
||||
- Login method Badge (Email/Phone/Google etc.)
|
||||
- User ID (clickable for details)
|
||||
|
||||
### IP Address
|
||||
Login IP address (clickable to view IP info).
|
||||
|
||||
### User Agent
|
||||
User device and browser information:
|
||||
- Hover to show full content
|
||||
- Truncated to avoid excessive length
|
||||
|
||||
### Success Status
|
||||
Whether login succeeded:
|
||||
- **Success** (Green Badge)
|
||||
- **Failed** (Red Badge)
|
||||
|
||||
### Time
|
||||
Login time.
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Date Filter
|
||||
Select date to view login records, defaults to today.
|
||||
|
||||
### User ID Filter
|
||||
Input user ID to view that user's login records.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's Logins
|
||||
|
||||
1. Shows today's login records by default
|
||||
2. Check login frequency
|
||||
3. Analyze active users
|
||||
|
||||
### Scenario 2: Investigate Abnormal Logins
|
||||
|
||||
**Check Failed Logins**:
|
||||
1. Filter failed login records
|
||||
2. View IP addresses
|
||||
3. Analyze failure reasons
|
||||
4. Ban IPs if necessary
|
||||
|
||||
**Check Remote Logins**:
|
||||
1. View user login IPs
|
||||
2. Click IP to view geolocation
|
||||
3. Compare with historical locations
|
||||
4. Notify user if anomalies found
|
||||
|
||||
### Scenario 3: Track User Logins
|
||||
|
||||
**View Specific User**:
|
||||
1. Filter by user ID
|
||||
2. View login history
|
||||
3. Analyze login devices
|
||||
4. Verify account security
|
||||
|
||||
## Security Monitoring
|
||||
|
||||
### Abnormal Patterns
|
||||
Watch for:
|
||||
- High volume of failed logins in short time
|
||||
- Multiple accounts from same IP
|
||||
- Logins from unusual countries/regions
|
||||
- Logins from rare device types
|
||||
|
||||
### Protection Measures
|
||||
When anomalies detected:
|
||||
1. Temporarily ban IP
|
||||
2. Force user password reset
|
||||
3. Send security notification
|
||||
4. Enable two-factor authentication
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Auto-cleaned per system config
|
||||
2. **IP Query**: Click IP to view geolocation
|
||||
3. **User Agent**: Contains OS and browser info
|
||||
4. **Privacy Protection**: Sensitive info only for admins
|
||||
5. **Failed Records**: Focus on failed login anomalies
|
||||
6. **Regular Checks**: Recommended daily login review
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,165 @@
|
||||
<div v-pre>
|
||||
|
||||
# SMS Log
|
||||
|
||||
View all SMS records sent by the system including sending status and content.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### Platform
|
||||
SMS sending platform (displayed as Badge):
|
||||
- Alibaba Cloud SMS
|
||||
- Tencent Cloud SMS
|
||||
- Twilio
|
||||
- AWS SNS
|
||||
- Other SMS providers
|
||||
|
||||
### To
|
||||
Recipient phone number.
|
||||
|
||||
### Subject
|
||||
SMS subject/type.
|
||||
|
||||
### Content
|
||||
SMS content (displayed as JSON):
|
||||
- SMS text
|
||||
- Template variables
|
||||
- Signature info
|
||||
- Max width 480px
|
||||
|
||||
### Status
|
||||
SMS sending status (displayed as Badge):
|
||||
- **Sent** (Green) - Successfully sent
|
||||
- **Failed** (Red) - Send failed
|
||||
- **Unknown** (Gray) - Unknown status
|
||||
|
||||
### Time
|
||||
SMS sending time.
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Keyword Search
|
||||
Search recipient phone number or SMS subject.
|
||||
|
||||
### Date Filter
|
||||
Select date to view SMS records, defaults to today.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's SMS
|
||||
|
||||
1. Shows today's SMS records by default
|
||||
2. Check sending quantity
|
||||
3. Check sending status
|
||||
4. Calculate success rate
|
||||
|
||||
### Scenario 2: Investigate Send Failures
|
||||
|
||||
**Check Failed SMS**:
|
||||
1. Filter "Failed" status
|
||||
2. View recipient numbers
|
||||
3. Check SMS content
|
||||
4. Analyze failure reasons (invalid number/insufficient balance/provider issues)
|
||||
5. Resend or fix configuration
|
||||
|
||||
### Scenario 3: Verify SMS Content
|
||||
|
||||
**Check SMS Templates**:
|
||||
1. Search specific subject
|
||||
2. View SMS content
|
||||
3. Verify variable replacement
|
||||
4. Confirm signature correctness
|
||||
|
||||
### Scenario 4: Track User SMS
|
||||
|
||||
**View User Received SMS**:
|
||||
1. Search user phone number
|
||||
2. View all SMS
|
||||
3. Confirm delivery
|
||||
4. Verify SMS types
|
||||
|
||||
## SMS Types
|
||||
|
||||
### Verification Code SMS
|
||||
- Registration verification code
|
||||
- Login verification code
|
||||
- Password reset code
|
||||
- Phone binding code
|
||||
|
||||
### Notification SMS
|
||||
- Order notifications
|
||||
- Payment success
|
||||
- Expiration reminders
|
||||
- System announcements
|
||||
|
||||
### Marketing SMS
|
||||
- Promotional SMS
|
||||
- Activity notifications
|
||||
- Offer information
|
||||
|
||||
## Sending Monitoring
|
||||
|
||||
### Success Rate Monitoring
|
||||
Watch metrics:
|
||||
- Daily total sent
|
||||
- Send success rate
|
||||
- Failure rate trends
|
||||
- Platform-specific performance
|
||||
|
||||
### Exception Handling
|
||||
When issues found:
|
||||
1. Check SMS provider configuration
|
||||
2. Verify API key validity
|
||||
3. Check balance and quota
|
||||
4. Review error logs
|
||||
5. Contact provider technical support
|
||||
|
||||
## SMS Content Description
|
||||
|
||||
### JSON Format
|
||||
Content field contains:
|
||||
```json
|
||||
{
|
||||
"template_id": "SMS_123456",
|
||||
"sign_name": "Brand Name",
|
||||
"params": {
|
||||
"code": "123456",
|
||||
"minutes": "5"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Template Variables
|
||||
- {{code}}: Verification code
|
||||
- {{minutes}}: Valid time
|
||||
- {{product}}: Product name
|
||||
- {{amount}}: Amount
|
||||
|
||||
## Cost Management
|
||||
|
||||
### Cost Statistics
|
||||
- Daily SMS count
|
||||
- Unit price calculation
|
||||
- Monthly expenses
|
||||
- Type distribution
|
||||
|
||||
### Cost Optimization
|
||||
- Control verification code frequency
|
||||
- Optimize SMS templates
|
||||
- Choose cost-effective providers
|
||||
- Avoid invalid sending
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention per system config
|
||||
2. **Content Truncation**: Long content may be truncated
|
||||
3. **JSON Display**: Content shown as JSON format
|
||||
4. **Platform Recognition**: Identify sending channel by platform field
|
||||
5. **Status Monitoring**: Watch for failed send records
|
||||
6. **Number Privacy**: Phone numbers are sensitive info
|
||||
7. **Regular Checks**: Daily sending status review
|
||||
8. **Quota Management**: Mind SMS provider quota and balance
|
||||
9. **Rate Limiting**: Prevent SMS flooding
|
||||
10. **Compliance**: Follow SMS sending laws and regulations
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,152 @@
|
||||
<div v-pre>
|
||||
|
||||
# Register Log
|
||||
|
||||
View user registration records including registration methods, IP addresses, and device information.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### User
|
||||
Registered user (clickable for details).
|
||||
|
||||
### Identifier
|
||||
Account identifier used for registration:
|
||||
- Registration method Badge (Email/Phone/Google etc.)
|
||||
- Specific account (email address/phone number etc.)
|
||||
|
||||
### IP Address
|
||||
Registration IP address (clickable to view IP info).
|
||||
|
||||
### User Agent
|
||||
Registration device and browser information:
|
||||
- Hover to show full content
|
||||
- Truncated to avoid excessive length
|
||||
|
||||
### Time
|
||||
Registration time.
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Date Filter
|
||||
Select date to view registration records, defaults to today.
|
||||
|
||||
### User ID Filter
|
||||
Input user ID to view that user's registration info.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's Registrations
|
||||
|
||||
1. Shows today's registration records by default
|
||||
2. Count registration quantity
|
||||
3. Analyze registration sources
|
||||
4. Identify registration method distribution
|
||||
|
||||
### Scenario 2: Track User Source
|
||||
|
||||
**View Registration Info**:
|
||||
1. View user registration record
|
||||
2. Confirm registration time
|
||||
3. Check registration IP location
|
||||
4. Analyze registration channel
|
||||
|
||||
### Scenario 3: Investigate Abnormal Registrations
|
||||
|
||||
**Check Suspicious Registrations**:
|
||||
1. View registration logs
|
||||
2. Focus on multiple registrations from same IP
|
||||
3. Check unusual countries/regions
|
||||
4. Identify batch registration behavior
|
||||
5. Limit registration if necessary
|
||||
|
||||
### Scenario 4: Analyze Registration Trends
|
||||
|
||||
**Calculate Registration Data**:
|
||||
1. Select time range
|
||||
2. Count total registrations
|
||||
3. Analyze registration peaks
|
||||
4. Evaluate promotion effectiveness
|
||||
|
||||
## Registration Methods
|
||||
|
||||
### Email Registration
|
||||
- Shows email address
|
||||
- Requires email verification
|
||||
- Most common method
|
||||
|
||||
### Phone Registration
|
||||
- Shows phone number
|
||||
- Requires SMS verification
|
||||
- Common in domestic market
|
||||
|
||||
### Social Account Registration
|
||||
- **Google**: Google account
|
||||
- **GitHub**: GitHub account
|
||||
- **Facebook**: Facebook account
|
||||
- **Apple**: Apple ID
|
||||
- **Telegram**: Telegram account
|
||||
|
||||
## Security Monitoring
|
||||
|
||||
### Abnormal Patterns
|
||||
Watch for:
|
||||
- High volume registrations in short time
|
||||
- Multiple registrations from same IP
|
||||
- Registrations from unusual countries/regions
|
||||
- Batch email/phone registrations
|
||||
- Temporary email registrations
|
||||
|
||||
### Protection Measures
|
||||
When anomalies detected:
|
||||
1. Enable registration CAPTCHA
|
||||
2. Limit registration rate per IP
|
||||
3. Ban suspicious IPs
|
||||
4. Enable email/phone verification
|
||||
5. Enable invitation code mechanism
|
||||
|
||||
## Registration Source Analysis
|
||||
|
||||
### Geographic Distribution
|
||||
- Country/region statistics
|
||||
- City distribution
|
||||
- Identify main markets
|
||||
|
||||
### Device Analysis
|
||||
From User Agent:
|
||||
- OS distribution
|
||||
- Browser types
|
||||
- Device types (PC/Mobile)
|
||||
- Identify user habits
|
||||
|
||||
### Registration Channels
|
||||
- Direct access
|
||||
- Search engines
|
||||
- Promotional links
|
||||
- Social media
|
||||
|
||||
## Data Statistics
|
||||
|
||||
### Daily Statistics
|
||||
- Daily new registrations
|
||||
- Registration conversion rate
|
||||
- Registration method ratio
|
||||
- Geographic distribution
|
||||
|
||||
### Promotion Evaluation
|
||||
- Registration volume during campaigns
|
||||
- Channel effectiveness
|
||||
- Post-registration retention
|
||||
- Post-registration payment rate
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention per system config
|
||||
2. **IP Tracking**: Can view IP geolocation
|
||||
3. **Device Recognition**: User Agent contains device info
|
||||
4. **Privacy Protection**: Registration info sensitive, keep confidential
|
||||
5. **Abnormal Monitoring**: Watch for batch and remote registrations
|
||||
6. **Method Distribution**: Understand user preferred registration methods
|
||||
7. **Regular Analysis**: Weekly registration trend analysis
|
||||
8. **Anti-fraud**: Prevent malicious batch registrations
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,145 @@
|
||||
<div v-pre>
|
||||
|
||||
# Reset Subscribe Log
|
||||
|
||||
View subscription traffic reset records including reset types and associated orders.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### User
|
||||
User owning the subscription (clickable for details).
|
||||
|
||||
### Subscribe ID
|
||||
Reset subscription ID (clickable for subscription details, hover for card).
|
||||
|
||||
### Type
|
||||
Reset type (displayed as Badge):
|
||||
- **Auto Reset** - Automatically reset by cycle
|
||||
- **Advance Reset** - User manually resets in advance
|
||||
- **Paid Reset** - Purchase traffic reset service
|
||||
|
||||
### Order No.
|
||||
Associated order number (shown for paid resets, clickable for order details).
|
||||
|
||||
### Time
|
||||
Reset time.
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Date Filter
|
||||
Select date to view reset records, defaults to today.
|
||||
|
||||
### Subscribe ID Filter
|
||||
Input subscription ID to view that subscription's reset records.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's Resets
|
||||
|
||||
1. Shows today's reset records by default
|
||||
2. Count reset quantity
|
||||
3. Analyze reset type distribution
|
||||
4. Identify high-frequency reset users
|
||||
|
||||
### Scenario 2: Track Subscription Resets
|
||||
|
||||
**View Subscription History**:
|
||||
1. Filter by subscription ID
|
||||
2. View all reset records
|
||||
3. Analyze reset frequency
|
||||
4. Verify resets are normal
|
||||
|
||||
### Scenario 3: Analyze Paid Resets
|
||||
|
||||
**Calculate Paid Data**:
|
||||
1. Filter "Paid Reset" type
|
||||
2. Count paid reset quantity
|
||||
3. Calculate paid reset revenue
|
||||
4. Analyze user demand
|
||||
|
||||
### Scenario 4: Investigate Abnormal Resets
|
||||
|
||||
**Check Suspicious Resets**:
|
||||
1. View reset logs
|
||||
2. Focus on high-frequency advance resets
|
||||
3. Identify abnormal reset behavior
|
||||
4. Verify order associations
|
||||
|
||||
## Reset Type Description
|
||||
|
||||
### Auto Reset
|
||||
- Automatically resets by subscription cycle
|
||||
- Monthly/weekly/daily reset
|
||||
- Executed by system scheduled task
|
||||
- Most common reset method
|
||||
|
||||
### Advance Reset
|
||||
- User manually resets in advance
|
||||
- Consumes reset count
|
||||
- Or purchase reset with payment
|
||||
- Suitable for traffic exhaustion
|
||||
|
||||
### Paid Reset
|
||||
- User purchases traffic reset service
|
||||
- Generates order record
|
||||
- Resets immediately after payment
|
||||
- Has associated order number
|
||||
|
||||
## Reset Rules
|
||||
|
||||
### Auto Reset Time
|
||||
- **Monthly Reset**: 1st of month at 00:00
|
||||
- **Weekly Reset**: Monday at 00:00
|
||||
- **Daily Reset**: Every day at 00:00
|
||||
|
||||
### Reset Count Limit
|
||||
- Plan includes reset count
|
||||
- Exceeding count requires payment
|
||||
- Count resets each cycle
|
||||
|
||||
### Paid Reset Pricing
|
||||
- Based on plan traffic config
|
||||
- Generally 20-30% of plan price
|
||||
- Configurable in product management
|
||||
|
||||
## Traffic Management
|
||||
|
||||
### Reset Strategy
|
||||
- Set reasonable reset cycle
|
||||
- Configure reset count limit
|
||||
- Price paid reset service
|
||||
- Notify users of reset rules
|
||||
|
||||
### User Reminders
|
||||
- Traffic near exhaustion reminder
|
||||
- Reset time reminder
|
||||
- Paid reset recommendation
|
||||
- Upgrade plan suggestion
|
||||
|
||||
## Data Statistics
|
||||
|
||||
### Reset Analysis
|
||||
Daily/monthly stats:
|
||||
- Auto reset count
|
||||
- Advance reset count
|
||||
- Paid reset count
|
||||
- Paid reset revenue
|
||||
|
||||
### User Behavior
|
||||
- High-frequency reset users
|
||||
- Paid reset conversion rate
|
||||
- Traffic usage after reset
|
||||
- Upgrade plan conversion
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention per system config
|
||||
2. **Subscription Association**: Each record linked to subscription ID
|
||||
3. **Type Recognition**: Distinguish reset method by type
|
||||
4. **Order Association**: Paid resets have order number
|
||||
5. **Time Accuracy**: Records precise reset time
|
||||
6. **Count Management**: Track user reset counts
|
||||
7. **Regular Analysis**: Weekly reset data analysis
|
||||
8. **Strategy Optimization**: Optimize reset rules based on data
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,149 @@
|
||||
<div v-pre>
|
||||
|
||||
# Server Traffic Log
|
||||
|
||||
View daily traffic statistics for each server with detailed traffic consumption breakdown.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### Server
|
||||
Server information display:
|
||||
- Server ID (displayed as Badge)
|
||||
- Server name
|
||||
|
||||
### Upload
|
||||
Daily upload traffic, auto-converts units (B/KB/MB/GB/TB).
|
||||
|
||||
### Download
|
||||
Daily download traffic, auto-converts units.
|
||||
|
||||
### Total
|
||||
Daily total traffic (upload + download).
|
||||
|
||||
### Date
|
||||
Traffic statistics date.
|
||||
|
||||
## Table Operations
|
||||
|
||||
### View Detail
|
||||
Click "Detail" button to jump to detailed traffic records page:
|
||||
- View detailed traffic for that date and server
|
||||
- Grouped by users
|
||||
- Aggregated by subscriptions
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Date Filter
|
||||
Select date to view traffic records, defaults to today.
|
||||
|
||||
### Server ID Filter
|
||||
Input server ID to view that server's traffic records.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's Traffic
|
||||
|
||||
1. Shows today's traffic records by default
|
||||
2. View traffic consumption per server
|
||||
3. Identify high-traffic servers
|
||||
4. Analyze traffic distribution
|
||||
|
||||
### Scenario 2: Track Server Load
|
||||
|
||||
**View Server Usage**:
|
||||
1. Filter by server ID
|
||||
2. View historical traffic records
|
||||
3. Analyze traffic trends
|
||||
4. Evaluate server load
|
||||
|
||||
### Scenario 3: Investigate Traffic Anomalies
|
||||
|
||||
**Check Abnormal Consumption**:
|
||||
1. Browse traffic records
|
||||
2. Focus on abnormally high-traffic servers
|
||||
3. Click "Detail" for breakdown
|
||||
4. Analyze traffic distribution by user
|
||||
5. Check for abuse
|
||||
|
||||
### Scenario 4: Traffic Statistics Analysis
|
||||
|
||||
**Generate Reports**:
|
||||
1. Select date range
|
||||
2. Export traffic data
|
||||
3. Analyze traffic peak times
|
||||
4. Optimize server resource allocation
|
||||
5. Plan capacity expansion
|
||||
|
||||
## Traffic Detail Page
|
||||
|
||||
After clicking "Detail" shows:
|
||||
|
||||
### User Traffic Breakdown
|
||||
- Traffic consumption per user
|
||||
- Subscription traffic statistics
|
||||
- Connection duration records
|
||||
|
||||
### Node Traffic Statistics
|
||||
- Total traffic per node
|
||||
- Traffic proportion analysis
|
||||
- User distribution
|
||||
|
||||
## Traffic Monitoring
|
||||
|
||||
### Normal Pattern
|
||||
- Evenly distributed traffic
|
||||
- Matches user count
|
||||
- Regular peak/valley patterns
|
||||
|
||||
### Abnormal Patterns
|
||||
Watch for:
|
||||
- Sudden traffic surge on single server
|
||||
- Severely uneven traffic distribution
|
||||
- High traffic in unusual time periods
|
||||
- Excessive traffic from single user
|
||||
|
||||
## Server Management
|
||||
|
||||
### Load Balancing
|
||||
Based on traffic data:
|
||||
- Identify high-load servers
|
||||
- Distribute users to other servers
|
||||
- Adjust server weights
|
||||
- Optimize node configuration
|
||||
|
||||
### Capacity Planning
|
||||
Based on traffic trends:
|
||||
- Predict traffic growth
|
||||
- Plan server expansion
|
||||
- Optimize bandwidth configuration
|
||||
- Control operating costs
|
||||
|
||||
## Data Analysis
|
||||
|
||||
### Traffic Statistics
|
||||
Daily/monthly stats:
|
||||
- Total traffic consumption
|
||||
- Server proportion
|
||||
- Traffic growth trends
|
||||
- Bandwidth utilization rate
|
||||
|
||||
### Cost Analysis
|
||||
- Traffic cost calculation
|
||||
- Server ROI analysis
|
||||
- Optimization opportunity identification
|
||||
- Cost control recommendations
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention per system config
|
||||
2. **Unit Conversion**: Auto-converts to readable units
|
||||
3. **Server Association**: Can view single server history
|
||||
4. **Detail Jump**: Click detail for user-level breakdown
|
||||
5. **Real-time**: Traffic data may have delay
|
||||
6. **Total Accuracy**: Total includes upload and download
|
||||
7. **Regular Analysis**: Recommended weekly traffic trend analysis
|
||||
8. **Load Monitoring**: Watch server load situation
|
||||
9. **Expansion Alert**: Expand when traffic nears limit
|
||||
10. **Cost Optimization**: Optimize config based on traffic data
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,120 @@
|
||||
<div v-pre>
|
||||
|
||||
# Subscribe Traffic Log
|
||||
|
||||
View daily traffic usage statistics for user subscriptions with detailed traffic consumption breakdown.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### User
|
||||
User consuming traffic (clickable for details).
|
||||
|
||||
### Subscribe
|
||||
Associated subscription ID (clickable for details, hover for card).
|
||||
|
||||
### Upload
|
||||
Daily upload traffic, auto-converts units (B/KB/MB/GB/TB).
|
||||
|
||||
### Download
|
||||
Daily download traffic, auto-converts units.
|
||||
|
||||
### Total
|
||||
Daily total traffic (upload + download).
|
||||
|
||||
### Date
|
||||
Traffic statistics date.
|
||||
|
||||
## Table Operations
|
||||
|
||||
### View Detail
|
||||
Click "Detail" button to jump to detailed traffic records page:
|
||||
- View detailed traffic for that date and subscription
|
||||
- Grouped by nodes
|
||||
- Aggregated by servers
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Date Filter
|
||||
Select date to view traffic records, defaults to today.
|
||||
|
||||
### User ID Filter
|
||||
Input user ID to view that user's traffic records.
|
||||
|
||||
### Subscribe ID Filter
|
||||
Input subscription ID to view that subscription's traffic records.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's Traffic
|
||||
|
||||
1. Shows today's traffic records by default
|
||||
2. View total traffic consumption
|
||||
3. Identify high-traffic users
|
||||
4. Analyze traffic trends
|
||||
|
||||
### Scenario 2: Track User Traffic
|
||||
|
||||
**View User Usage**:
|
||||
1. Filter by user ID
|
||||
2. View all subscription traffic
|
||||
3. Analyze usage habits
|
||||
4. Predict traffic needs
|
||||
|
||||
### Scenario 3: Investigate Traffic Anomalies
|
||||
|
||||
**Check Abnormal Consumption**:
|
||||
1. Browse traffic records
|
||||
2. Focus on unusually high traffic
|
||||
3. Click "Detail" for breakdown
|
||||
4. Analyze traffic distribution by node
|
||||
5. Check for abuse
|
||||
|
||||
### Scenario 4: Traffic Statistics Analysis
|
||||
|
||||
**Generate Reports**:
|
||||
1. Select date range
|
||||
2. Export traffic data
|
||||
3. Analyze traffic peak times
|
||||
4. Optimize node resource allocation
|
||||
|
||||
## Traffic Detail Page
|
||||
|
||||
After clicking "Detail" shows:
|
||||
|
||||
### Node Traffic Breakdown
|
||||
- Traffic consumption per node
|
||||
- Upload/download separately counted
|
||||
- Connection duration records
|
||||
|
||||
### Server Traffic Statistics
|
||||
- Total traffic per server
|
||||
- Traffic proportion analysis
|
||||
- Load situation assessment
|
||||
|
||||
## Traffic Monitoring
|
||||
|
||||
### Abnormal Patterns
|
||||
Watch for:
|
||||
- Sudden daily traffic surge
|
||||
- Traffic far exceeding plan limit
|
||||
- High traffic in unusual time periods
|
||||
- Single node excessive traffic
|
||||
|
||||
### Handling Measures
|
||||
When anomalies detected:
|
||||
1. View traffic details
|
||||
2. Confirm if abuse
|
||||
3. Throttle or suspend subscription
|
||||
4. Notify user for verification
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention time per system config
|
||||
2. **Unit Conversion**: Auto-converts to readable units
|
||||
3. **Subscription Association**: Can cross-query user's multiple subscriptions
|
||||
4. **Detail Jump**: Click detail for node-level breakdown
|
||||
5. **Real-time**: Traffic data may have delay
|
||||
6. **Total Accuracy**: Total includes upload and download
|
||||
7. **Regular Analysis**: Recommended weekly traffic trend analysis
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,127 @@
|
||||
<div v-pre>
|
||||
|
||||
# Subscribe Log
|
||||
|
||||
View user subscription link request records including IP, device, and time information.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### User
|
||||
User requesting subscription (clickable for details).
|
||||
|
||||
### Subscribe ID
|
||||
Requested subscription ID (clickable for subscription details, hover for card).
|
||||
|
||||
### IP Address
|
||||
Request IP address (clickable to view IP info).
|
||||
|
||||
### User Agent
|
||||
Client device and system information:
|
||||
- Hover to show full content
|
||||
- Truncated to avoid excessive length
|
||||
|
||||
### Time
|
||||
Request time.
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Date Filter
|
||||
Select date to view subscription records, defaults to today.
|
||||
|
||||
### User ID Filter
|
||||
Input user ID to view that user's subscription requests.
|
||||
|
||||
### Subscribe ID Filter
|
||||
Input subscription ID to view that subscription's request records.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Today's Requests
|
||||
|
||||
1. Shows today's subscription records by default
|
||||
2. Check request frequency
|
||||
3. Analyze active subscriptions
|
||||
4. Identify abnormal requests
|
||||
|
||||
### Scenario 2: Track User Requests
|
||||
|
||||
**View User Activity**:
|
||||
1. Filter by user ID
|
||||
2. View all subscription requests
|
||||
3. Analyze usage frequency
|
||||
4. Verify device types
|
||||
|
||||
### Scenario 3: Investigate Subscription Anomalies
|
||||
|
||||
**Check Abnormal Requests**:
|
||||
1. View subscription logs
|
||||
2. Focus on IP address changes
|
||||
3. Check User Agent
|
||||
4. Identify suspicious devices
|
||||
5. Ban subscription if necessary
|
||||
|
||||
### Scenario 4: Analyze Client Distribution
|
||||
|
||||
**Calculate Client Types**:
|
||||
1. View User Agent information
|
||||
2. Count client distribution
|
||||
3. Understand user habits
|
||||
4. Optimize client support
|
||||
|
||||
## Subscription Request Monitoring
|
||||
|
||||
### Normal Pattern
|
||||
- Periodic subscription link requests
|
||||
- Update node information
|
||||
- Sync configuration changes
|
||||
|
||||
### Abnormal Patterns
|
||||
Watch for:
|
||||
- High-frequency requests in short time
|
||||
- Multiple subscriptions from same IP
|
||||
- Access from unusual countries/regions
|
||||
- Unfamiliar client types
|
||||
|
||||
## Security Protection
|
||||
|
||||
### Detection Measures
|
||||
- Request rate limiting
|
||||
- IP whitelist/blacklist
|
||||
- Subscription token verification
|
||||
- Device count limit
|
||||
|
||||
### Handling Measures
|
||||
When abuse detected:
|
||||
1. Limit request rate
|
||||
2. Temporarily ban IP
|
||||
3. Reset subscription token
|
||||
4. Notify user for confirmation
|
||||
|
||||
## User Agent Analysis
|
||||
|
||||
### Common Clients
|
||||
- **Clash**: Clash for Windows/Mac/Android
|
||||
- **Shadowrocket**: iOS client
|
||||
- **V2rayN**: Windows client
|
||||
- **Quantumult**: iOS client
|
||||
- **Surfboard**: Android client
|
||||
|
||||
### Identification Info
|
||||
From User Agent:
|
||||
- Client name and version
|
||||
- OS type
|
||||
- Device model
|
||||
- System version
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention per system config
|
||||
2. **IP Tracking**: Can view IP geolocation
|
||||
3. **Device Recognition**: User Agent contains client info
|
||||
4. **Request Frequency**: Normal clients request periodically
|
||||
5. **Abnormal Monitoring**: Watch for high-frequency and remote requests
|
||||
6. **Privacy Protection**: IP and device info sensitive
|
||||
7. **Regular Analysis**: Weekly subscription request trend analysis
|
||||
8. **Prevent Leakage**: Subscription links should not be publicly shared
|
||||
|
||||
</div>
|
||||
@@ -0,0 +1,172 @@
|
||||
<div v-pre>
|
||||
|
||||
# Traffic Details Log
|
||||
|
||||
View detailed traffic consumption records with multi-dimensional filtering by server, user, and subscription.
|
||||
|
||||
## Table Column Description
|
||||
|
||||
### Server
|
||||
Server generating traffic:
|
||||
- Server name
|
||||
- Server ID
|
||||
|
||||
### User
|
||||
User consuming traffic (clickable for details).
|
||||
|
||||
### Subscribe
|
||||
Associated subscription ID (clickable for subscription details, hover for card).
|
||||
|
||||
### Upload
|
||||
Upload traffic, auto-converts units (B/KB/MB/GB/TB).
|
||||
|
||||
### Download
|
||||
Download traffic, auto-converts units.
|
||||
|
||||
### Time
|
||||
Traffic generation time.
|
||||
|
||||
## Filter Functions
|
||||
|
||||
### Date Filter
|
||||
Select date to view traffic details, defaults to today.
|
||||
|
||||
### Server ID Filter
|
||||
Input server ID to view that server's traffic details.
|
||||
|
||||
### User ID Filter
|
||||
Input user ID to view that user's traffic details.
|
||||
|
||||
### Subscribe ID Filter
|
||||
Input subscription ID to view that subscription's traffic details.
|
||||
|
||||
## Usage Scenarios
|
||||
|
||||
### Scenario 1: View Server Traffic Breakdown
|
||||
|
||||
Enter from server traffic log by clicking "Detail":
|
||||
1. Auto-fills date and server ID
|
||||
2. View all user traffic on that server
|
||||
3. Sort by user
|
||||
4. Identify high-traffic users
|
||||
|
||||
### Scenario 2: View User Traffic Details
|
||||
|
||||
Enter from subscribe traffic log by clicking "Detail":
|
||||
1. Auto-fills date, user ID, and subscription ID
|
||||
2. View that user's subscription traffic
|
||||
3. View distribution by server
|
||||
4. Analyze usage habits
|
||||
|
||||
### Scenario 3: Investigate Traffic Anomalies
|
||||
|
||||
**Detailed Investigation**:
|
||||
1. Select anomaly date
|
||||
2. Input relevant filter conditions
|
||||
3. View detailed traffic records
|
||||
4. Sort by time for analysis
|
||||
5. Identify abnormal traffic sources
|
||||
|
||||
### Scenario 4: Traffic Statistics Analysis
|
||||
|
||||
**Multi-dimensional Analysis**:
|
||||
1. Select time range
|
||||
2. Combine different filter conditions
|
||||
3. Export detailed data
|
||||
4. Generate traffic reports
|
||||
5. Develop optimization strategies
|
||||
|
||||
## Data Association
|
||||
|
||||
### Jump from Server Traffic
|
||||
- Brings server ID and date
|
||||
- View all traffic on that server
|
||||
- Can further filter by user
|
||||
|
||||
### Jump from Subscribe Traffic
|
||||
- Brings user ID, subscription ID, and date
|
||||
- View all traffic for that subscription
|
||||
- Can view different servers
|
||||
|
||||
## Traffic Analysis
|
||||
|
||||
### Time Distribution
|
||||
- View traffic time distribution
|
||||
- Identify usage peak times
|
||||
- Analyze user active hours
|
||||
- Optimize server scheduling
|
||||
|
||||
### Server Distribution
|
||||
- Count traffic proportion per server
|
||||
- Analyze load distribution
|
||||
- Identify popular servers
|
||||
- Optimize load balancing
|
||||
|
||||
### User Distribution
|
||||
- Identify high-traffic users
|
||||
- Analyze user usage habits
|
||||
- Check for abuse
|
||||
- Optimize plan configuration
|
||||
|
||||
## Traffic Monitoring
|
||||
|
||||
### Normal Pattern
|
||||
- Evenly distributed traffic
|
||||
- Time regularity
|
||||
- Matches user count
|
||||
- No abnormal peaks
|
||||
|
||||
### Abnormal Patterns
|
||||
Watch for:
|
||||
- Abnormally large single traffic
|
||||
- Traffic in unusual time periods
|
||||
- High-frequency requests from single user
|
||||
- Unreasonable traffic distribution
|
||||
|
||||
## Investigation Steps
|
||||
|
||||
### Discover Anomaly
|
||||
1. Find anomaly from statistics log
|
||||
2. Click detail to enter
|
||||
3. View detailed records
|
||||
|
||||
### Locate Problem
|
||||
1. Sort by time
|
||||
2. Identify abnormal records
|
||||
3. View user information
|
||||
4. Confirm subscription status
|
||||
|
||||
### Handling Measures
|
||||
1. Verify if normal usage
|
||||
2. Check for abuse
|
||||
3. Throttle or suspend subscription
|
||||
4. Notify user for confirmation
|
||||
|
||||
## Data Export
|
||||
|
||||
### Export Purpose
|
||||
- Generate traffic reports
|
||||
- Financial reconciliation
|
||||
- User analysis
|
||||
- Capacity planning
|
||||
|
||||
### Export Content
|
||||
- All column data
|
||||
- Filtered data
|
||||
- CSV or Excel format
|
||||
- Supports batch export
|
||||
|
||||
## Important Notes
|
||||
|
||||
1. **Log Retention**: Retention per system config
|
||||
2. **Unit Conversion**: Auto-converts to readable units
|
||||
3. **Multi-filter**: Supports multiple condition combinations
|
||||
4. **Jump with Params**: Jumps from stats logs auto-fill parameters
|
||||
5. **Real-time**: Traffic data may have delay
|
||||
6. **Detail Level**: Most detailed traffic records
|
||||
7. **Performance**: Consider filtering with large data volumes
|
||||
8. **Regular Cleanup**: Detail logs consume more storage
|
||||
9. **Export Limits**: Single export may have quantity limits
|
||||
10. **Privacy Protection**: Detailed records contain user behavior info
|
||||
|
||||
</div>
|
||||
Reference in New Issue
Block a user