DevNet Associate (DEVASC) v1.0Cisco Platforms and DevelopmentMedium
A security operations team wants to integrate Cisco FSO (Full-Stack Observability) with their custom security orchestration platform. They need to retrieve detailed application performance metrics, security events, and infrastructure health data programmatically. Which type of API would they primarily use for this data extraction from Cisco FSO?
- AQuery APIs
- BData Ingestion APIs
- CEvent-driven APIs
- DConfiguration APIs
Show answer & explanationAnswer & explanation
Correct answer: A. Query APIs
Cisco FSO exposes Query APIs that allow external systems to retrieve collected observability data, including application performance metrics, security events, and infrastructure health, based on specified criteria. This is crucial for integrating with orchestration platforms that need to pull data.
Why the other options are wrong
- B. Data Ingestion APIs are for sending data *into* FSO, not retrieving it.
- C. Event-driven APIs (webhooks) push data, which is not the primary mechanism for a custom platform to 'retrieve' detailed data on demand.
- D. Configuration APIs are for managing FSO itself, not for extracting observed data.
Cisco FSO Query APIs
Cisco FSO Query APIs enable programmatic access for external applications to retrieve collected observability data, such as application performance, security events, and infrastructure metrics, based on specific query parameters.
- Used for extracting data from FSO.
- Supports various query parameters for filtering and selection.
- Essential for integration with external analysis or orchestration tools.
Memory trick: FSO's APIs are like a library: some for adding books, some for borrowing them.