Load Cisco Nexus Dashboard Insights data in Python using dltHub
Build a Cisco Nexus Dashboard Insights-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Cisco Nexus Dashboard Insights is a platform providing centralized management, monitoring, and analytics for data center infrastructure that exposes its functionality through a REST API gateway. The REST API base URL is https://<node-management-ip> and all requests require an authentication token passed in a cookie header.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Cisco Nexus Dashboard Insights data in under 10 minutes.
What data can I load from Cisco Nexus Dashboard Insights?
Here are some of the endpoints you can load from Cisco Nexus Dashboard Insights:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| sites | /sites | GET | Get list of all sites | |
| anomalies | /sedgeapi/v1/cisco-nir/api/api/v1/anomalies/summary | GET | Get anomaly summary | |
| endpoint_stats | /sedgeapi/v1/cisco-nir/api/api/v1/endpoints/statistics | GET | Get endpoint statistics | |
| congestion_counters | /sedgeapi/v1/cisco-nir/api/api/v1/congestion/counters | GET | Get congestion counters | |
| defect_details | /sedgeapi/v1/cisco-nir/api/api/telemetry/defectDetails | GET | Get defect details |
How do I authenticate with the Cisco Nexus Dashboard Insights API?
Authentication is performed via a POST login request to obtain a JWT. The resulting token must be passed in subsequent API calls using the 'Cookie' header with the format 'AuthCookie='.
1. Get your credentials
To obtain credentials for the Nexus Dashboard API, you can use either a session-based authentication token or an API key for automation. \n\n1. For a session token: Send a POST request to https:///api/v1/infra/login with a JSON payload containing userName, userPasswd, and domain. The response includes an authentication token, which must be passed in the Cookie: AuthCookie= header for subsequent requests. \n\n2. For an API Key: API keys are recommended for automation. You can create them via the Nexus Dashboard GUI or API. To create one via API, first authenticate as described above, then POST an empty JSON payload {} to https:///api/config/addapikey. Note that the API key is displayed only once upon creation.
2. Add them to .dlt/secrets.toml
[sources.cisco_nexus_dashboard_insights_source] api_key = "REPLACE_ME"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Cisco Nexus Dashboard Insights API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python cisco_nexus_dashboard_insights_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline cisco_nexus_dashboard_insights_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset cisco_nexus_dashboard_insights_data The duckdb destination used duckdb:/cisco_nexus_dashboard_insights.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads /api/v1/infra/login and /api/v1/manage/fabrics from the Cisco Nexus Dashboard Insights API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def cisco_nexus_dashboard_insights_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<node-management-ip>", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key}, }, "resources": [ {"name": "sites", "endpoint": {"path": "sites"}}, {"name": "anomalies", "endpoint": {"path": "sedgeapi/v1/cisco-nir/api/api/v1/anomalies/summary"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="cisco_nexus_dashboard_insights_pipeline", destination="duckdb", dataset_name="cisco_nexus_dashboard_insights_data", ) load_info = pipeline.run(cisco_nexus_dashboard_insights_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("cisco_nexus_dashboard_insights_pipeline").dataset() sessions_df = data.sites.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM cisco_nexus_dashboard_insights_data.sites LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("cisco_nexus_dashboard_insights_pipeline").dataset() data.sites.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Cisco Nexus Dashboard Insights data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Cisco Nexus Dashboard Insights?
Request dlt skills, commands, AGENT.md files, and AI-native context.