Aporia Documentation
Get StartedBook a Demo🚀 Cool StuffBlog
V2
V2
  • 📖Aporia Docs
  • 🤗Introduction
    • Quickstart
    • Support
  • 💡Core Concepts
    • Why Monitor ML Models?
    • Understanding Data Drift
    • Analyzing Performance
    • Tracking Data Segments
    • Models & Versions
  • 🚀Deployment
    • AWS
    • Google Cloud
    • Azure
    • Databricks
    • Offline / On-Prem
    • Platform Architecture
  • 🏠Storing your Predictions
    • Overview
    • Real-time Models (Postgres)
    • Real-time Models (Kafka)
    • Batch Models
    • Kubeflow / KServe
  • 🧠Model Types
    • Regression
    • Binary Classification
    • Multiclass Classification
    • Multi-Label Classification
    • Ranking
  • 🌈Explainability
    • SHAP values
  • 📜NLP
    • Intro to NLP Monitoring
    • Example: Text Classification
    • Example: Token Classification
    • Example: Question Answering
  • 🍪Data Sources
    • Overview
    • Amazon S3
    • Athena
    • BigQuery
    • Databricks
    • Glue Data Catalog
    • Google Cloud Storage
    • PostgreSQL
    • Redshift
    • Snowflake
    • Microsoft SQL Server
    • Oracle
  • ⚡Monitors & Alerts
    • Overview
    • Data Drift
    • Metric Change
    • Missing Values
    • Model Activity
    • Model Staleness
    • Performance Degradation
    • Prediction Drift
    • Value Range
    • Custom Metric
    • New Values
    • Alerts Consolidation
  • 🎨Dashboards
    • Overview
  • 🤖ML Monitoring as Code
    • Getting started
    • Adding new models
    • Data Segments
    • Custom metrics
    • Querying metrics
    • Monitors
    • Dashboards
  • 📡Integrations
    • Slack
    • Webhook
    • Teams
    • Single Sign On (SAML)
    • Cisco
  • 🔐Administration
    • Role Based Access Control (RBAC)
  • 🔑API Reference
    • REST API
    • API Extended Reference
    • Custom Segment Syntax
    • Custom Metric Syntax
    • Code-Based Metrics
    • Metrics Glossary
  • ⏩Release Notes
    • Release Notes 2024
    • Release Notes 2023
Powered by GitBook
On this page
  1. Integrations

Cisco

PreviousSingle Sign On (SAML)NextRole Based Access Control (RBAC)

Last updated 1 year ago

You can integrate Aporia with Cisco's Full-Stack Observability Platform to receive alerts and notifications directly to the platform, and view your models health status in a centralized place.

Setting up the FSOP Integration

  1. Create a service principal in Cisco's platform

    1. Login to

    2. Click on Access Management and go to Service Principals

    3. Click on Add

    4. Define the new service principal. Note to pick Basic for Authentication Type and add the Agent default role access (Under Edit Role Access). Then click on Create.

    5. Save the output service principal details - They will be needed for the Aporia integration.

  2. Log into Aporia’s console. On the navbar on the left, click on Integrations, switch to the Applications tab, and choose Cisco.

  3. Enter your Tenant Details and Service Principal Details, as created in the previous step. The Tenant URL should include the schema with no added URIs (https://<tenant>.observe.appdynamics.com).

  4. Click Save. On success the save button will become disabled, and you'll be able to Test the integration.

Congratulations: You’ve now successfully integrated Aporia to Cisco's FSO Platform!

After Integrating Cisco FSOP, any monitors will be automatically configured to send alerts to the platform.

In addition, the workspace state will now be synced to the FSO platform periodically, including models and alerts.

Happy Monitoring!

📡
https://accounts.appdynamics.com/overview
Cisco FSOP Account Management
Cisco FSOP Service Principal Management
Service-Principal Configuration
Service Principal Details
Cisco Integration
Integration Configuration
Monitor Configuration