--- title: "Integrations" description: "Explore Middleware integrations overview to connect with cloud, database, and third-party tools for complete monitoring." section: "Integrations" breadcrumb: "Integrations > Overview" canonical: "https://docs.middleware.io/integrations" --- # Integrations Connect the tools you already run to Middleware. Cloud accounts, databases, message queues and on-call tools each bring their own data and actions into the same place as your traces, logs and metrics — so an alert can page the right person, and an investigation can read the systems around it. **New to integrations? Start with these three.** 1. **Pick an integration** — Browse by category below, or search by what it collects 2. **Authenticate or point the agent** — Cloud, SSO and on-call tools connect by API. Databases use the agent. 3. **Confirm data is arriving** — Status turns Active once the first data point lands ## Browse integrations Every integration is listed once, under the category it mainly belongs to. Each card says whether it connects by API or runs through the Middleware agent. - [Amazon Web Services](/integrations/aws-integration) — CloudWatch metrics, resource inventory and tags across your accounts. (Cloud, API) - [Azure](/integrations/azure-integration) — Subscription-wide metrics and resource metadata via Azure Monitor. (Cloud, API) - [Google Cloud Platform](/integrations/gcp-integration) — Project metrics from Cloud Monitoring, with labels preserved. (Cloud, API) - [Vercel](/integrations/vercel-integration) — Build and runtime logs, plus deployment events as annotations. (Cloud, API) - [TrueFoundry](/integrations/truefoundry) — Model-serving metrics and inference logs from your TrueFoundry workspaces. (Cloud, API) - [Slack](/integrations/slack-integration) — Route alerts to channels, and acknowledge without leaving Slack. (Collaboration, API) - [Microsoft Teams](/integrations/microsoft-team-integration) — Alert delivery to Teams channels with incident context attached. (Collaboration, API) - [Jira](/integrations/jira-integration) — Raise an issue from an alert, with the trace and host prefilled. (Collaboration, API) - [PagerDuty](/integrations/pagerduty-integration) — Page the on-call rota and sync acknowledgement state both ways. (Collaboration, API) - [Opsgenie](/integrations/opsgenie-integration) — Escalation policies driven by Middleware alert severity. (Collaboration, API) - [Zenduty](/integrations/zenduty-integration) — On-call scheduling and incident routing from alert events. (Collaboration, API) - [GitHub](/integrations/github-integration) — Link deploys to releases, and let OpsAI open a fix as a pull request. (Collaboration, API) - [Bitbucket](/integrations/bitbucket-integration) — Repository access for OpsAI, and deploy markers from pipelines. (Collaboration, API) - [Grafana](/integrations/grafana-integration) — Let OpsAI read your existing Grafana dashboards during an investigation. (OpsAI Tools, API) - [Datadog](/integrations/datadog-integration) — Give OpsAI read access to Datadog while you are still migrating. (OpsAI Tools, API) - [PostgreSQL](/integrations/postgresql-integration) — Query performance, replication lag, locks and connection pool state. (Database, Agent) - [MySQL](/integrations/mysql-integration) — Slow query digests, InnoDB buffer health and replica status. (Database, Agent) - [MongoDB](/integrations/mongodb-integration) — Operation counters, replica set health and index hit ratios. (Database, Agent) - [MongoDB Atlas](/integrations/mongodb-atlas-integration) — Cluster metrics pulled from the Atlas Admin API, no agent required. (Database, API) - [Redis](/integrations/redis-integration) — Command latency, keyspace hit rate, evictions and memory fragmentation. (Database, Agent) - [Elasticsearch](/integrations/elasticsearch-integration) — Cluster and index health, search and indexing latency, JVM pressure. (Database, Agent) - [ClickHouse](/integrations/clickhouse-integration) — Query throughput, merge activity and part counts per table. (Database, Agent) - [Cassandra](/integrations/cassandra-integration) — Read and write latency per keyspace, compaction and hint backlog. (Database, Agent) - [Oracle](/integrations/oracledb-integration) — Wait events, tablespace usage and session-level activity. (Database, Agent) - [SQL Server](/integrations/sql-server-integration) — Wait statistics, deadlocks, buffer cache and plan cache behaviour. (Database, Agent) - [SAP HANA](/integrations/saphana-integration) — Memory and CPU per service, plus expensive statement tracking. (Database, Agent) - [AWS RDS PostgreSQL](/integrations/aws-rds-integration) — Enhanced Monitoring metrics correlated with query-level detail. (Database, API) - [Azure Database for PostgreSQL](/integrations/azure-managed-postgresql) — Flexible Server metrics without installing anything on the host. (Database, API) - [GCP Cloud SQL for PostgreSQL](/integrations/gcp-cloudsql-postgresql) — Cloud SQL instance metrics joined to the traces that query them. (Database, API) - [Kafka](/integrations/kafka-integration) — Broker, partition and consumer group health, read from Kafka's JMX metrics. (Streaming, Agent) - [RabbitMQ](/integrations/rabbitmq-integration) — Queues, exchanges, channels and node health from the management plugin. (Streaming, Agent) - [Redpanda](/integrations/redpanda-integration) — Broker throughput and latency metrics to find bottlenecks in the stream. (Streaming, Agent) - [Apache](/integrations/apache-server-integration) — Request and response activity from Apache HTTP Server, with its logs. (Networking, Agent) - [Nginx](/integrations/nginx-integration) — Connection states, request rates, response codes and upstream timing. (Networking, Agent) - [Prometheus](/integrations/prometheus-integration) — Scrape any Prometheus endpoint and keep its metrics beside your traces. (Telemetry, Agent) - [Prometheus & Kubernetes](/integrations/prometheus-integration-k8s) — Every service exposing Prometheus metrics in the cluster, scraped for you. (Telemetry, Agent) - [Journald](/integrations/journald-integration) — Systemd journal logs, filtered to the units you actually care about. (Logs, Agent) - [Custom Logs](/get-started/ingestion-api/custom-logs) — Post logs over OTLP/HTTP from anything that can make a request. (Custom Data Ingestion, API) - [Custom Metrics](/get-started/ingestion-api/custom-metrics) — Your own business or infrastructure metrics, charted with the rest. (Custom Data Ingestion, API) - [Okta](/features/accounts/sso/okta) — Single sign-on for your team over SAML or OIDC. (SSO, API) - [Microsoft Entra ID](/features/accounts/sso/microsoft-entra-id) — Single sign-on backed by your Microsoft Entra ID directory. (SSO, API) - [Windows Event Logs](/integrations/windows-event-logs) — System, security, application and custom event channels, as logs. (Windows, Agent) > Not listed here? Tell us what you are running. [Contact Us](https://middleware.io/contact-us/) ## Frequently asked questions Asked before every integration install, regardless of which one. #### What are the prerequisites for installing integrations? Prerequisites vary by integration type, but every integration needs Admin level permissions to install. Consult the specific integration's documentation for the permissions its third-party side requires. #### How do I configure my Middleware account for integrations? Check the status of your account permissions in the [Profile](/features/accounts) section of your account. If you do not have Admin level permissions, contact your system administrator to change them. #### Does an integration need an agent as well? It depends which kind — that is what the [API and Agent badge](#browse-integrations) on each card tells you. Cloud, SSO and collaboration integrations authenticate directly against the provider's API and need nothing installed. Database, streaming and networking integrations are collected by the Middleware agent, so one has to be running with reach to the instance. #### Do integrations count towards my ingestion volume? The data an integration sends is billed like any other data of the same kind — log events as log events, and monitored hosts as hosts. See [Usage Based Charges](/features/accounts) for the rates, track it on the [Usage](/features/accounts/usage) page, and use [Ingestion control](/features/pipeline/ingestion-control) to drop what you don't need. Need assistance or want to learn more about Middleware? Get in touch with us via our Contact Us page or join our Slack channel.