You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it currently possible to query path trace results via GraphQL given a termination ID as an argument (similar to the vanilla REST API)?
In the REST API we have the endpoint circuits/circuit-termination/{id}/paths/ which does this.
In my use case I query for a list of circuits, and I need to determine to which switch/interface they connect, possibly several cables/terminations away from the returned circuit termination.
Today I loop through the large list of circuit terminations pulling individual trace results via many individual REST calls. This is very slow, so I was hoping to see if there was a way to craft a GraphQL query to minimize the number or API calls.
However, I don't see path trace functionality in the GraphQL schema. Does it exist? Or does anyone have any other ideas on how to make a task like this more efficient?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
Is it currently possible to query path trace results via GraphQL given a termination ID as an argument (similar to the vanilla REST API)?
In the REST API we have the endpoint
circuits/circuit-termination/{id}/paths/
which does this.In my use case I query for a list of circuits, and I need to determine to which switch/interface they connect, possibly several cables/terminations away from the returned circuit termination.
Today I loop through the large list of circuit terminations pulling individual trace results via many individual REST calls. This is very slow, so I was hoping to see if there was a way to craft a GraphQL query to minimize the number or API calls.
However, I don't see path trace functionality in the GraphQL schema. Does it exist? Or does anyone have any other ideas on how to make a task like this more efficient?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions