Add application FQDN to Subscription inventory #7732
Description
Description:
Currently, the standard inventory does not include detailed information about installed applications and their configurations. This makes it difficult to identify which customer a specific application instance belongs to, especially since in NS8 the application–customer association is no longer available on my.
Problem:
Without this association, it’s not possible to verify which customer owns a given application (e.g., cti or voice), making certain partner verifications unreliable.
Proposed solution:
Add additional information to the standard inventory, such as:
- The FQDN of each installed application (e.g.,
cti.example.org,webtop.example.org) - The associated LDAP domain
These data could be included only in the inventory sent by registered clusters (those with a Subscription) and not in the general phonehome data, to avoid privacy concerns.
Discussion summary:
- Domain names and FQDNs are not anonymous data.
- It may be acceptable to include them only in the my inventory (for Subscription clusters).
- The new my already plans a dedicated Applications section where customer associations can be added manually.
- For the current my transition phase, exporting application–FQDN mappings (e.g., from Traefik configuration) would already provide useful insights.
Example data formats:
Option 1 (app → FQDN):
{
"nethvoice4": "nethvoice.nethesis.it",
"webtop6": "webtop.nethesis.it"
}Option 2 (app → list of FQDNs):
{
"nethvoice4": ["nethvoice.nethesis.it", "cti.nethesis.it"],
"webtop6": ["webtop.nethesis.it"]
}Option 3 (FQDN → app):
{
"nethvoice.nethesis.it": "nethvoice4",
"cti.nethesis.it": "nethvoice4",
"webtop.nethesis.it": "webtop6"
}Requested outcome:
Extend the standard inventory to include application FQDNs (or other relevant identifiers) for improved partner and deployment verification, while ensuring data privacy compliance.
See also