Hello,
Thank you again for maintaining lancache-manager — it’s a great tool and very well executed.
I’d like to propose an enhancement related to cacheable content visibility and categorization.
Problem / Motivation
Currently, the UI provides detailed insights primarily for Steam cached content, which is extremely useful.
However, there are several other officially supported and commonly used cacheable services that are either not visible or not categorized with the same level of detail.
Examples include:
Epic Games
Blizzard / Battle.net
Riot Games
Ubisoft
Microsoft / Xbox
PlayStation
Other CDN-based cached content
Additionally, cached content that does not fall under a known category is not easily observable or analyzed.
Proposed Enhancements
- Expand Official Cacheable Services
Add support for officially listed cacheable services such as:
Epic Games
Blizzard / Battle.net
(and others supported by Lancache)
Provide per-service visibility similar to Steam:
Cache hit ratio
Bandwidth saved
Total requests
Storage usage (if applicable)
- Introduce an “Other” Cached Content Category
Add a generic “Other” category to display uncategorized or non-standard cached content.
Suggested metrics for this category:
List of cached URLs / domains
Cache hit & miss ratios
Traffic volume per URL or domain
Time-based activity (recently cached content)
This would give administrators much better insight into:
What is actually being cached
Unexpected or unknown traffic
Optimization opportunities
Benefits
Improved transparency of cache behavior
Better bandwidth optimization decisions
Easier troubleshooting and auditing
Feature parity across different platforms, not only Steam
Notes
I understand that some of this depends on log parsing and upstream lancache capabilities, so even partial implementation (visibility-only, without deep metrics at first) would already be very valuable.
Thank you for your time and consideration.
Please let me know if clarification or additional examples would help.
Hello,
Thank you again for maintaining lancache-manager — it’s a great tool and very well executed.
I’d like to propose an enhancement related to cacheable content visibility and categorization.
Problem / Motivation
Currently, the UI provides detailed insights primarily for Steam cached content, which is extremely useful.
However, there are several other officially supported and commonly used cacheable services that are either not visible or not categorized with the same level of detail.
Examples include:
Epic Games
Blizzard / Battle.net
Riot Games
Ubisoft
Microsoft / Xbox
PlayStation
Other CDN-based cached content
Additionally, cached content that does not fall under a known category is not easily observable or analyzed.
Proposed Enhancements
Add support for officially listed cacheable services such as:
Epic Games
Blizzard / Battle.net
(and others supported by Lancache)
Provide per-service visibility similar to Steam:
Cache hit ratio
Bandwidth saved
Total requests
Storage usage (if applicable)
Add a generic “Other” category to display uncategorized or non-standard cached content.
Suggested metrics for this category:
List of cached URLs / domains
Cache hit & miss ratios
Traffic volume per URL or domain
Time-based activity (recently cached content)
This would give administrators much better insight into:
What is actually being cached
Unexpected or unknown traffic
Optimization opportunities
Benefits
Improved transparency of cache behavior
Better bandwidth optimization decisions
Easier troubleshooting and auditing
Feature parity across different platforms, not only Steam
Notes
I understand that some of this depends on log parsing and upstream lancache capabilities, so even partial implementation (visibility-only, without deep metrics at first) would already be very valuable.
Thank you for your time and consideration.
Please let me know if clarification or additional examples would help.