Traffic Portal feature request: the ability to identify if a DS is used as a steering target

[guzzijason]

As a Traffic Portal user, the ability to identify (in the Delivery Service table list and/or in the DS config screen) whether or not this service is a steering target, and if so, also identify the steering config(s) that reference it. Currently, we can only trace the relationship in the opposite direction.

[mitchell852]

Not sure if a DS knows that it is a steering target. Sounds like maybe a couple of attributes would need to be added to a DS response along the lines of isSteeringTarget: true|false and steeringSources: [ sources ] or something like that...

[mitchell852]

tenancy could make this interesting as a source ds could be outside your tenancy which would give you the impression that a delivery services is not being used as a steering target. just something to think about...

[mitchell852]

@jhg03a - you added the "high impact" label. can you explain why? just curious. is this something that is requested frequently?

[jhg03a]

While moderately infrequent as an sre, the only workaround is querying todb (typically last resort discouraged if possible) or writing custom scripts to reconstruct the data. During outages that awareness can save outage minutes.

It is also an operations safety concern so that there is awareness when updating one steering target there's a decent chance you need to update others you weren't told about.

And as a self-service consumer, it's an aid to navigate the relationships of DS with one another.

[mitchell852]

agreed @jhg03a . this is info that operators need especially when troubleshooting issues and depending on the implementation chosen, it could be a semi-low effort imo.