Enhancing Asset Management in GLPI: Separation, Criticality, Colors, and Advanced OS Handling

Hello,

I would like to propose several improvements to asset management in GLPI to optimize classification and monitoring, especially for servers.

1. Separation of “Computers” and “Servers” Assets

Currently, “Computers” and “Servers” are grouped together, which can make management more complex. It would be beneficial to introduce a native distinction between these two categories to better structure information and filtering.

2. Addition of a “Criticality” Field for Servers

To facilitate the management of critical infrastructure, a “Criticality” field should be added to server assets. This field could be customizable (e.g., low, moderate, high, critical) and usable in filters and reports.

3. Customizable Colors for Better Visibility

• Ability to assign a color to the “Criticality” field values to visually identify the most critical servers.

• An option to customize the colors of the “Status” field, allowing better differentiation of states (e.g., green for “Operational,” red for “Down,” orange for “Maintenance”).

4. Improved Operating System Management

• Automatic OS-to-Version, Kernel, and Edition Linking: When selecting an OS, it should automatically suggest only relevant versions, editions, and service packs. This would prevent errors and avoid displaying irrelevant versions. For example, selecting Windows Servershould not show ESXi versions in the dropdown list. Similarly, selecting Linux should not display Windows-specific versions.

• Additional Fields for OS End-of-Life (EOL) Tracking: Automatically populate fields with OS end-of-support dates based on an integrated database or API. This would help anticipate updates and migrations.

These enhancements would greatly improve asset readability and management, especially in large infrastructures where handling numerous servers and OS versions can be challenging without automation.

Thank you for considering this suggestion!