V2.39.0 Update Log

Network Analysis helps quickly locate network issues during deployment, scaling, and troubleshooting, and provides a downloadable evidence package.

Target Users

1. Implementation and delivery engineers who need to confirm whether ports are open and links are reachable after deployment or scaling.

2. O&M admins who need to perform daily inspections and periodically monitor changes in network connectivity.

3. Technical support engineers who need to perform preliminary diagnosis of on-site issues and collect standardized troubleshooting evidence.

Application Scenarios

1. The platform cannot be accessed after deployment, or the project fails to start.

2. Access requests return 502 or 504 errors, and you need to check whether inter-node connectivity is unavailable or the container port is blocked.

3. External dependencies are unreachable, such as cloud domains, the template market, the plugin market, and OAuth domains.

4. You need to troubleshoot cross-layer issues, such as DNS resolution, port occupation, firewall and iptables rules, and container network exceptions.

5. Evidence collection is required for complex issues, such as conflicts between physical server network segments and container network segments, and incorrect container network modes.

For details, see Network Analysis.

When FineReport, FineBI, FineDataLink, and FineBI Engine components experience startup exceptions, repeated restarts, or health check failures, you usually need to collect application logs, container logs, Docker events, and thread stacks separately. This requires logging in to nodes, switching between multiple entry points, and manual time alignment, making troubleshooting slow and increasing the risk of missing key materials. Diagnostic Collection combines collection, time alignment, and packaging of these materials into one operation.

Application Scenarios

1. A container fails to start or exits immediately after startup, and you need to locate startup errors.

2. A container repeatedly restarts, and you need to align Docker events and application logs on the timeline.

3. A health check remains in the failed (unhealthy) status, and you need to use thread stacks to determine whether the application is stuck.

4. When you submit an issue to technical support or the FanRuan R&D team, you need to provide complete on-site diagnostic materials at once.