In order to understand the impact of removing or changing a Connection or gateway we need to be able to see what uses it and is related to it.
Can we have a view at the connection and gateway level to see which artifacts in which workspaces use them.
Synapse Analytics and Data Factory have linked service 'relate' option, so something similar would be really helpful.
2 Comments
- HaldemanMANew Member
Currently...To get this information, I have to run multiple admin api's, including Get Datasources for each dataset. This takes 10 hours to run through all of our datasets in the tenant. Then I have to map it to the output of Get Datasources for the gateway. I am afraid to just let the 10 hour job run unattended, so I break it up in to workable time segments, which requires this to be a manual process. It is only something that can be done every quarter at best. We can see in the workspace lineage views on the tenant that the data is already linked and available, so please expose the same linkage view from the gateway connection perspective.
Additionally adding "last time used" attribute on the Get Datasource Status api or in the proposed new lineage view, would help us identify inactive connections that are still attached to datasets not being refreshed. I have tried to use the actual gateway logs from the servers, but this only exposes active connections. I have to manipulate the output to throw into Excel and perform vlookups for the connections that don't show up and assume they are inactive from a very limited point of time captured in a log file.
In summary, Administrators don't have time to come up with adhoc solutions such as this and would GREATLY benefit from this view. I know how voting works and this won't even be reviewed most likely. There aren't enough Admins to increase the votes. :(
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Add selective sync to OneLake File Explorer and allow Lakehouse sync to Files only
Idea Please add a selective sync feature to OneLake File Explorer so users can choose exactly which Fabric items are synchronised to their local machine. Today, OneLake File Explorer surfaces...JP89917 hours agoKudo CommanderNew573Views6likes1CommentPipeline: Activity-level Run Conditions (No IF Container Required)
We need the ability to add a "Run if" condition directly to every pipeline activity. Like, in each acticity's settings. One of the biggest readability issues in Fabric Pipelines is that conditional ...frithjof_v1 day agoCommunity ChampionNew31Views4likes1CommentPipeline: New Routing activity as an improvement to IF and Switch
The current If Condition and Switch activities create large nested containers that own all activities inside their branches. These containers make the canvas much harder to read. Instead, add a lig...frithjof_v1 day agoCommunity ChampionNew16Views2likes1Comment