Use cases
Use cases
Illustrative examples of everyday lookups. They describe how the features combine, not any real customer.
Who owns this service?
An alert names a service. Search finds it; the Service page shows the owning Team, contacts and links.
Typical lookups
- GET /api/search?q=checkout
- GET /api/service/{name}
- Owning Team and contacts
What breaks if this changes?
Before a change, walk the dependency and ownership edges around a Service in the operational graph.
Typical lookups
- DEPENDS_ON edges
- GET /api/graph/traverse
- Dependents of a Service
Which accounts does a team run in?
Follow a Team to its Services and their AWS and Azure accounts, with provisioning state.
Typical lookups
- Team → Services
- Service → AWS accounts
- Requester map on each account
Keep a downstream system in step
A deployment tool subscribes to catalog events and re-reads the changed row when a notice arrives.
Typical lookups
- service.updated webhook
- Verify X-YP-Signature
- GET the row by id
Look up who owns it in seconds
Sign in with your Fleetworks account, or start with the public rows through the API.