Feature Enhancement ask: Reporting Interface for Experience Fragment Export status and destination / serve (more visibility)

[#1]

Request for Feature Enhancement (RFE) Summary:	Would like an interface to the Adobe Experience Fragment Export via IMS (enhancement to the export/serve/status of Fragment Export)
Use-case:	Many orgs have limited bandwidth to troubleshoot the destination of Experience Fragments as they are exported to Target (i.e. workspace destination). Development development team updates the experience fragment incorrectly or a bad config gets installed via the build or is misconfigured via IMS in some way, it would be useful to see the ultimate destination (and potentially where the XF is embedded by Target if possible) within some kind of reporting interface.
Current/Experienced Behavior:	No visibility into Experience Fragment destination our serving after export
Improved/Expected Behavior:	Some level of visibility into Experience Fragment "Journey"
Environment Details (AEM version/service pack, any other specifics if applicable):	6.5
Customer-name/Organization name:	Large Medical Organization Based in Northern California
Screenshot (if applicable):
Code package (if applicable):

[#2]

@jkkp12 

Please note that the information that you are looking for is all visible in the Target side. The Target's console offers tab provides the info about the content name, content type, source specific to each workspace.

[#3]

@jkkp12 Do you agree with Hamid or you have more informaiton/request to be shared? 

[#4]

@jkkp12, We are closing this ticket as we do not hear a response from you. Please reply with information asked on this thread to reopen it again.