# Bronto Docs

## Docs

- [Welcome to Bronto](https://docs.bronto.io/welcome.md): Bronto is the Intelligent Observability Data Platform for the AI era: store, search, and monitor telemetry at scale with no trade-offs on cost or coverage.
- [Introduction](https://docs.bronto.io/introduction.md): Bronto docs cover everything from sending your first events to building dashboards, writing queries, and connecting Bronto to AI tools like MCP.
- [Quick Ingest](https://docs.bronto.io/getting-started/quick-ingestion.md): Send data directly to Bronto in seconds using an API key with no agent or forwarder configuration required, ideal for testing or one-off ingestion.
- [Bronto Ingestion Endpoints](https://docs.bronto.io/getting-started/bronto-endpoints.md): Reference for Bronto's ingestion endpoints, including supported formats, OTLP and HTTP routes, regional URLs, authentication, and when to use each.
- [Try Bronto with the OpenTelemetry Demo](https://docs.bronto.io/getting-started/otel-demo.md): Run the OpenTelemetry Demo (Astronomy Shop) locally and route its logs, metrics, and traces to Bronto to explore real, correlated telemetry.
- [Changelog](https://docs.bronto.io/changelog.md): Read the latest Bronto product updates, new features, integrations, and announcements, with release notes for log management, tracing, and AI features.
- [Send Traces to Bronto](https://docs.bronto.io/tracing/send-traces.md): Send OpenTelemetry traces to Bronto using OTLP over HTTP or gRPC, exported directly from the OTel SDK or routed through an OpenTelemetry Collector.
- [Explore Traces](https://docs.bronto.io/tracing/explore-traces.md): Explore distributed traces in Bronto to investigate services, operations, latency, errors, and trace volume, then drill into spans and correlated logs.
- [Send Metrics to Bronto](https://docs.bronto.io/metrics/send-metrics.md): Send OpenTelemetry metrics to Bronto using OTLP over HTTP, exported directly from an OTel SDK or routed through an OpenTelemetry Collector.
- [Explore Metrics](https://docs.bronto.io/metrics/explore-metrics.md): Query Bronto metrics with formulas, inspect histograms, normalize series, configure units, export raw data, and create metric monitors.
- [Log Search](https://docs.bronto.io/Search-and-Visualize/Log-Search.md): Explore millions of log events in Bronto with the Search page, using a single search syntax with autocomplete and SQL-style filtering to analyze your data.
- [Search Syntax](https://docs.bronto.io/query-syntax/search-syntax.md): Query Bronto telemetry with a unified search syntax combining SQL-style expressions, autocomplete, and automatic conversion of free-text searches.
- [Patterns](https://docs.bronto.io/core-features/patterns.md): Use Bronto Patterns to automatically group structurally similar log messages, search with precision, and analyze log frequency and volume.
- [Visualization](https://docs.bronto.io/Search-and-Visualize/Log-Visualization.md): Visualize your data in Bronto with charts, time series, and aggregations driven by SQL queries to expose trends, errors, and performance issues.
- [Dashboards](https://docs.bronto.io/Search-and-Visualize/Dashboards.md): Build Bronto dashboards from metrics and other telemetry to visualize application performance, track trends, and share live views with your team.
- [Saved Searches](https://docs.bronto.io/Search-and-Visualize/Saved-Searches.md): Save search queries, filters and column layouts as Saved Searches in Bronto so your team can quickly switch between troubleshooting contexts and shared workflows.
- [Data Organization](https://docs.bronto.io/Search-and-Visualize/Partitions.md): Organize log data in Bronto using datasets, collections, tags, and partition tags to scope queries, control access, and manage retention efficiently.
- [Monitoring Overview & Threshold Monitors](https://docs.bronto.io/core-features/monitors.md): Create threshold monitors in Bronto to evaluate logs or metrics on a schedule and alert teams via email, webhooks, Slack, or PagerDuty.
- [Change Detection Monitors](https://docs.bronto.io/core-features/change-detection.md): Detect spikes, drops, and shifts in metrics or telemetry with Bronto change detection monitors that compare current values against historical baselines.
- [Slack](https://docs.bronto.io/integrations/slack.md): Receive Bronto monitor alerts directly in your Slack workspace using incoming webhooks so your team can triage incidents without leaving their chat.
- [Webhooks](https://docs.bronto.io/integrations/webhooks.md): Send Bronto monitor alerts to any HTTP endpoint with custom payloads to trigger downstream automation, ticketing, or chat tools when an alert fires.
- [My Data](https://docs.bronto.io/My-Data/My-Data.md): Manage your Bronto data, review collections and datasets, monitor data quality, and explore ingestion and search usage from the My Data page.
- [Log Forwarding](https://docs.bronto.io/core-features/log-forwarding.md): Forward Bronto log events to an external Amazon S3 bucket for archiving, long-term storage, compliance workflows, or downstream processing.
- [Access Control](https://docs.bronto.io/Account-Management/Access-Control.md): Bronto offers a flexible access management system that allows you to customize the level at which you control access to your Bronto resources.
- [API Keys](https://docs.bronto.io/Account-Management/API-Keys.md): Create, manage, and rotate Bronto API keys to authenticate integrations and route telemetry to the correct service in your organization.
- [Bring Your Own Key (BYOK)](https://docs.bronto.io/Account-Management/BYOK.md): Encrypt Bronto data at rest using your own AWS KMS customer-managed key (BYOK) for tighter compliance, key rotation, and access control.
- [Multi-Organisation](https://docs.bronto.io/Account-Management/Multi-Org.md): Operate multiple independent organisations within a single Bronto account, with centralised governance, role-based access, and isolated data.
- [User Management](https://docs.bronto.io/Account-Management/User-Management.md): Invite, edit, and remove users in your Bronto organisation, assign roles, and review access permissions from the Users settings page.
- [Security](https://docs.bronto.io/Account-Management/Security.md): Learn how Bronto protects your data with SOC 2 Type II compliance, encryption at rest and in transit, role-based access controls, and audit logging.
- [Data Retention](https://docs.bronto.io/Account-Management/Retention.md): Configure how long Bronto retains your data at the organisation and dataset level to control storage costs and meet compliance requirements.
- [SSO Overview](https://docs.bronto.io/Account-Management/SSO/SSO-Overview.md): Configure single sign-on (SSO) so users log in to Bronto through your identity provider using SAML or OIDC, instead of a password.
- [SSO Role Mapping](https://docs.bronto.io/Account-Management/SSO/SSO-Role-Mapping.md): Map SAML attributes from your identity provider to Bronto user roles so user permissions are provisioned automatically from your IdP.
- [Google SAML IdP](https://docs.bronto.io/Account-Management/SSO/google-saml.md): Configure Google Workspace as a SAML identity provider for Bronto so users can sign in with their existing Google accounts via single sign-on.
- [Okta OIDC](https://docs.bronto.io/Account-Management/SSO/okta-oidc.md): Configure Okta as an OIDC single sign-on provider for Bronto so users authenticate through your existing identity provider with centralised access.
- [Microsoft Entra ID](https://docs.bronto.io/Account-Management/SSO/entra-id.md): Configure Microsoft Entra ID (formerly Azure AD) as a SAML or OIDC single sign-on provider for Bronto, and map Entra ID groups to Bronto roles.
- [Glossary](https://docs.bronto.io/getting-started/glossary.md): Definitions for Bronto-specific terms used across the documentation, including datasets, collections, partitions, monitors, and ingestion concepts.
- [Ingest Data into Bronto](https://docs.bronto.io/ingest-data/overview.md): Choose how to get your logs, metrics, and traces into Bronto — agents, cloud providers, CDNs, applications, infrastructure, databases, and OpenTelemetry.
- [Agent Setup](https://docs.bronto.io/agent-setup/agent-intro.md): Configure a telemetry agent to collect and forward log data to Bronto. Supports OpenTelemetry, Fluent Bit, Fluentd, Logstash, Datadog Agent, and Vector.
- [Connect OpenTelemetry Collector to Bronto](https://docs.bronto.io/agent-setup/open-telemetry.md): Deploy the OpenTelemetry Collector with OTLP exporters to receive, process, and forward logs, metrics, and traces to Bronto, including on Kubernetes.
- [Connect Odigos to Bronto](https://docs.bronto.io/agent-setup/odigos.md): Configure Odigos to auto-instrument Kubernetes workloads with eBPF and forward their traces, metrics, and logs to Bronto over OTLP.
- [Connect Fluent Bit to Bronto](https://docs.bronto.io/agent-setup/fluent-bit.md): Configure the Fluent Bit log processor to collect application and system logs, batch them, and forward to Bronto over HTTP for search and analysis.
- [Connect Fluentd to Bronto](https://docs.bronto.io/agent-setup/fluentd.md): Configure the Fluentd open-source data collector to tail application log files and forward structured events to Bronto over HTTP with batching and retries.
- [Connect Logstash to Bronto](https://docs.bronto.io/agent-setup/logstash.md): Configure the Logstash data processing pipeline with an HTTP output to enrich, transform, and forward log events from your applications to Bronto.
- [Configure Datadog Agent](https://docs.bronto.io/agent-setup/datadog-agent.md): Forward logs to Bronto using the Datadog Agent, ideal for migrating existing Datadog-based pipelines without changing your application instrumentation.
- [Connect Vector to Bronto](https://docs.bronto.io/agent-setup/vector.md): Configure the Vector observability data pipeline to collect, transform, and forward host, container, and application logs to Bronto over HTTP.
- [Ingesting AWS Data into Bronto](https://docs.bronto.io/integrations/aws-overview.md): An overview of the available methods for sending AWS log, trace, and metric data to Bronto, with guidance on choosing the right approach.
- [Amazon Bedrock AgentCore Logs, Metrics and Traces](https://docs.bronto.io/integrations/aws-agentcore.md): Route the OpenTelemetry logs, metrics and traces an agent emits on Amazon Bedrock AgentCore Runtime to Bronto — via an OTel Collector or directly over OTLP.
- [ALB and NLB Access Logs](https://docs.bronto.io/integrations/aws-alb.md): Ingest Application and Network Load Balancer access logs into Bronto — client IP, request details, target, latency, and response code — from an S3 bucket.
- [Amazon API Gateway Logs](https://docs.bronto.io/integrations/aws-api-gateway.md): Send execution and access logs from Amazon API Gateway REST and HTTP APIs to Bronto via CloudWatch, capturing request paths, latencies, and integration errors.
- [Amazon Bedrock Logs, Metrics and Traces](https://docs.bronto.io/integrations/aws-bedrock.md): Collect OpenTelemetry logs, metrics, and traces from applications that call the Amazon Bedrock Converse and InvokeModel APIs via an OTel Collector.
- [Amazon CloudFront Real-Time Logs](https://docs.bronto.io/integrations/aws-cloudfront.md): Stream Amazon CloudFront real-time logs to Bronto with per-viewer-request edge details such as cache status, edge location, viewer IP, and response bytes.
- [Amazon CloudWatch Metrics](https://docs.bronto.io/integrations/aws-cloudwatch-metrics.md): Ingest Amazon CloudWatch service metrics for EC2, RDS, Lambda, and load balancers into Bronto through CloudWatch Metric Streams and Amazon Data Firehose.
- [AWS CloudTrail Events](https://docs.bronto.io/integrations/aws-cloudtrail.md): Ingest AWS API activity and management events from CloudTrail into Bronto — who did what, when, and from where — via EventBridge API Destinations.
- [Amazon Cognito Activity](https://docs.bronto.io/integrations/aws-cognito.md): Ingest Amazon Cognito user pool activity — authentication events, user management operations, and token issuance — via CloudTrail.
- [Amazon DynamoDB Events](https://docs.bronto.io/integrations/aws-dynamodb.md): Ingest Amazon DynamoDB management and data events — API calls, table operations, and item-level activity — into Bronto through CloudTrail and EventBridge.
- [Amazon ECS and AWS Fargate Telemetry](https://docs.bronto.io/integrations/aws-ecs.md): Choose the right ingestion path for container logs, metrics, and traces from Amazon ECS tasks and AWS Fargate workloads — an ADOT sidecar or FireLens.
- [Amazon EKS Telemetry](https://docs.bronto.io/integrations/aws-eks.md): Choose the right ingestion path for pod logs, kubelet metrics, control plane logs, and traces from Amazon EKS — an ADOT DaemonSet or Fargate sidecar.
- [Amazon ElastiCache Logs](https://docs.bronto.io/integrations/aws-elasticache.md): Ship Amazon ElastiCache slow logs and engine logs for Redis and Valkey clusters to Bronto to troubleshoot latency, evictions, and command usage.
- [AWS GuardDuty Findings](https://docs.bronto.io/integrations/aws-guardduty.md): Ingest AWS GuardDuty threat findings into Bronto — compromised credentials, unusual API calls, malware, and suspicious network activity — via EventBridge.
- [AWS Lambda Telemetry](https://docs.bronto.io/integrations/aws-lambda.md): Compare AWS Lambda ingestion options for function logs, platform logs, metrics, and traces to choose between CloudWatch, extensions, or the ADOT layer.
- [Amazon RDS and Aurora (MySQL) Logs](https://docs.bronto.io/integrations/aws-rds-mysql.md): Ship MySQL slow query, general, and error logs from Amazon RDS and Aurora MySQL to Bronto to diagnose slow queries, connection failures, and replication issues.
- [Amazon RDS and Aurora (PostgreSQL) Logs](https://docs.bronto.io/integrations/aws-rds-postgresql.md): Ship PostgreSQL slow query, connection, and error logs from Amazon RDS and Aurora to Bronto to troubleshoot query latency, locking, and auth failures.
- [Amazon Route 53 DNS Query Logs](https://docs.bronto.io/integrations/aws-route53.md): Ingest Amazon Route 53 public DNS query logs and Resolver query logs into Bronto to investigate DNS traffic patterns, resolver failures, and suspicious lookups.
- [Amazon SES Sending Events](https://docs.bronto.io/integrations/aws-ses.md): Send Amazon SES delivery, bounce, complaint, reject, open, and click events to Bronto to monitor email deliverability and investigate send failures.
- [AWS Step Functions Execution Logs](https://docs.bronto.io/integrations/aws-step-functions.md): Ingest AWS Step Functions execution history — state transitions, input/output payloads, errors, and durations — into Bronto to debug workflow failures at scale.
- [VPC Flow Logs](https://docs.bronto.io/integrations/aws-vpc-flow-logs.md): Ingest VPC Flow Logs — IP traffic records for network interfaces in your VPC, useful for security analysis, network diagnostics, and compliance.
- [AWS WAF Logs](https://docs.bronto.io/integrations/aws-waf.md): Ingest AWS WAF web ACL traffic logs — allowed, blocked, and counted requests with rule match details — into Bronto for security monitoring and threat hunting.
- [Forwarding AWS Logs from S3](https://docs.bronto.io/integrations/aws-client-s3.md): Forward logs delivered to Amazon S3 buckets into Bronto using a Lambda-based forwarder for VPC flow, ALB, CloudFront, and other AWS service logs.
- [Forwarding AWS Logs from CloudWatch](https://docs.bronto.io/integrations/aws-client-cloudwatch.md): Forward Amazon CloudWatch Logs to Bronto with Lambda subscription filters to centralize AWS service, application, and Lambda function logs for search.
- [ECS Container Logs with AWS FireLens](https://docs.bronto.io/integrations/aws-firelens.md): Route Amazon ECS container logs directly to Bronto using AWS FireLens with Fluent Bit, skipping CloudWatch and reducing AWS log ingestion costs.
- [Kubernetes Logs with Fluent Bit on EKS](https://docs.bronto.io/integrations/aws-fluent-bit-eks.md): Deploy Fluent Bit as a DaemonSet on Amazon EKS to collect Kubernetes container logs and forward them to Bronto, a lightweight alternative to the OTel Collector.
- [AWS Distribution for OpenTelemetry (ADOT)](https://docs.bronto.io/integrations/aws-adot.md): Send application logs, metrics, and traces from Amazon ECS, EKS, or EC2 to Bronto with AWS Distro for OpenTelemetry (ADOT), avoiding CloudWatch fees.
- [Serverless Telemetry with ADOT Lambda Layer](https://docs.bronto.io/integrations/aws-adot-lambda.md): Instrument AWS Lambda functions with the AWS Distro for OpenTelemetry (ADOT) Lambda Layer to send serverless logs, metrics, and traces to Bronto.
- [Self-Managed OpenTelemetry Collector on AWS](https://docs.bronto.io/integrations/aws-custom-otel.md): Deploy and configure an OpenTelemetry Collector on AWS to send logs, metrics, and traces to Bronto with full control over routing and processing.
- [AWS EventBridge API Destinations](https://docs.bronto.io/integrations/aws-eventbridge.md): Route AWS service events directly to Bronto using Amazon EventBridge API Destinations, with no Lambda function required for forwarding or transformation.
- [AWS Kinesis Firehose for Logs](https://docs.bronto.io/integrations/aws-firehose-logs.md): Stream high-volume AWS logs into Bronto with an Amazon Data Firehose delivery stream that batches and retries HTTP delivery automatically.
- [AWS Kinesis Firehose for CloudWatch Metrics](https://docs.bronto.io/integrations/aws-firehose-cloudwatch-metrics.md): Send Amazon CloudWatch metrics to Bronto through CloudWatch Metric Streams and an Amazon Data Firehose HTTP destination — no Lambda function required.
- [Ingesting Azure Data into Bronto](https://docs.bronto.io/integrations/azure-overview.md): An overview of the available methods for sending Azure log and trace data to Bronto, with guidance on choosing the right approach.
- [Azure Kubernetes Service Telemetry](https://docs.bronto.io/integrations/azure-aks.md): Choose the right ingestion path for pod logs, kubelet metrics, control plane logs, and traces from Azure Kubernetes Service with a Collector DaemonSet.
- [Azure Container Apps Telemetry](https://docs.bronto.io/integrations/azure-container-apps.md): Choose the right ingestion path for console logs, system logs, metrics, and traces from Azure Container Apps — a Collector container app or the OTel SDK.
- [Azure Container Instances Telemetry](https://docs.bronto.io/integrations/azure-aci.md): Choose the right ingestion path for container stdout logs, metrics, and traces from Azure Container Instances, using an OpenTelemetry Collector sidecar.
- [Azure App Service Telemetry](https://docs.bronto.io/integrations/azure-app-service.md): Choose the right ingestion path for application logs, web server logs, platform diagnostics, and traces from Azure App Service with OpenTelemetry.
- [Azure Functions Telemetry](https://docs.bronto.io/integrations/azure-functions.md): Choose the right ingestion path for function execution logs, host logs, metrics, and distributed traces from Azure Functions — the OTel SDK or a Collector.
- [Azure Virtual Machines Telemetry](https://docs.bronto.io/integrations/azure-vms.md): Choose the right ingestion path for system logs, application logs, and distributed traces from Azure Virtual Machines and VM Scale Sets.
- [Azure Event Hub Forwarder](https://docs.bronto.io/integrations/azure-client.md): Forward Azure logs to Bronto using Azure Event Hub and the Bronto log forwarder to centralize platform, diagnostic, and application telemetry.
- [OpenTelemetry on Azure](https://docs.bronto.io/integrations/azure-otel.md): Send application logs, metrics, and traces from Azure to Bronto using a self-managed OpenTelemetry Collector or the OpenTelemetry SDK.
- [Azure Monitor OpenTelemetry Distro](https://docs.bronto.io/integrations/azure-monitor-otel-distro.md): Forward logs, metrics, and traces to Bronto with Microsoft's Azure Monitor OpenTelemetry Distro when you already use Application Insights.
- [Collecting Windows OS Logs](https://docs.bronto.io/integrations/azure-windows-logs.md): Collect Windows Event Log channels and file-based logs (IIS, SQL Server) from Windows hosts and ship them to Bronto with the OpenTelemetry Collector.
- [Akamai](https://docs.bronto.io/integrations/akamai.md): Stream Akamai CDN logs to Bronto with DataStream 2 for real-time visibility into edge traffic, errors, cache performance, and security events.
- [Cloudflare](https://docs.bronto.io/integrations/cloudflare.md): Forward Cloudflare HTTP request, firewall, and Workers logs to Bronto in near real time using Logpush for analysis of edge traffic and security events.
- [Fastly](https://docs.bronto.io/integrations/fastly.md): Stream Fastly CDN service logs to Bronto in real time using a real-time log streaming endpoint to monitor edge traffic, errors, and cache performance.
- [Send Auth0 events to Bronto](https://docs.bronto.io/integrations/auth0.md): Stream Auth0 authentication and user lifecycle events — logins, MFA challenges, and password resets — to Bronto with Auth0 Event Streams.
- [Send Okta events to Bronto](https://docs.bronto.io/integrations/okta.md): Stream all Okta System Log events to Bronto through AWS EventBridge Log Streaming — no Lambda, no middleware, and no verification handshake required.
- [Send Google Cloud Run telemetry to Bronto](https://docs.bronto.io/integrations/gcp-cloud-run.md): Send Cloud Run application logs, metrics, and traces through an OpenTelemetry Collector sidecar, and platform request logs through Cloud Logging Pub/Sub.
- [Send Google Kubernetes Engine logs and metrics to Bronto](https://docs.bronto.io/integrations/gcp-gke.md): Collect GKE pod logs and kubelet metrics with an OpenTelemetry Collector DaemonSet, or bridge Cloud Logging through Pub/Sub, and forward both to Bronto.
- [Send Heroku Fir telemetry to Bronto](https://docs.bronto.io/integrations/heroku-fir.md): Forward logs, metrics, and traces from Heroku Fir apps to Bronto with a native OpenTelemetry telemetry drain — no Logplex, proxy, or Collector needed.
- [PagerDuty](https://docs.bronto.io/integrations/pagerduty.md): Forward PagerDuty incident events into Bronto with PagerDuty's Generic Webhooks integration to search and analyze them alongside your other telemetry.
- [Supabase logs, metrics, and traces](https://docs.bronto.io/integrations/supabase.md): Send Supabase Postgres, Auth, Storage, Realtime, and Edge Function logs with a log drain, scrape the Metrics API with the OpenTelemetry Collector, and correlate both with your application's traces.
- [Vercel](https://docs.bronto.io/integrations/vercel.md): Stream runtime logs, OpenTelemetry traces, Speed Insights, Web Analytics, and audit logs from Vercel into Bronto using Vercel drains.
- [Ingesting Infrastructure Telemetry into Bronto](https://docs.bronto.io/integrations/infrastructure-overview.md): An overview of self-hosted infrastructure and database integrations that send logs, metrics, and traces to Bronto with the OpenTelemetry Collector.
- [Docker container logs and metrics with OpenTelemetry](https://docs.bronto.io/integrations/docker.md): Collect container logs and runtime metrics from Docker and Docker Compose with the OpenTelemetry Collector and forward them to Bronto.
- [Docker build traces with BuildKit and OpenTelemetry](https://docs.bronto.io/integrations/docker-build.md): Send Docker BuildKit build traces to Bronto over OTLP to see per-step durations, cache hits and misses, and where build time is spent.
- [Envoy logs, metrics, and traces with OpenTelemetry](https://docs.bronto.io/integrations/envoy.md): Collect Envoy access logs, Prometheus metrics, and request traces — downstream connections, response codes, and timing — with the OpenTelemetry Collector.
- [HAProxy logs and metrics with OpenTelemetry](https://docs.bronto.io/integrations/haproxy.md): Collect HAProxy access logs and proxy metrics — request latency, status codes, and backend health — with the OpenTelemetry Collector and Prometheus.
- [Host metrics with OpenTelemetry](https://docs.bronto.io/integrations/host-metrics.md): Collect CPU, memory, disk, filesystem, network, paging, process, and system-load metrics with the OpenTelemetry Collector and send them to Bronto.
- [Istio logs, metrics, and traces with OpenTelemetry](https://docs.bronto.io/integrations/istio.md): Collect Istio access logs, Envoy sidecar metrics, and mesh traces with the OpenTelemetry Collector, enabling access logging through the Telemetry API.
- [Apache Kafka logs and metrics with OpenTelemetry](https://docs.bronto.io/integrations/kafka.md): Collect Apache Kafka broker logs and cluster metrics — controller and request logs, partitions, and consumer lag — with the OpenTelemetry Collector.
- [Kubernetes logs and metrics with OpenTelemetry](https://docs.bronto.io/integrations/kubernetes.md): Deploy the OpenTelemetry Collector as a DaemonSet to collect Kubernetes pod logs, kubelet metrics, node events, and workload metadata.
- [MongoDB logs and metrics with OpenTelemetry](https://docs.bronto.io/integrations/mongodb.md): Collect self-hosted MongoDB server logs and database metrics — slow queries, connections, and replication — with the OpenTelemetry Collector.
- [MySQL logs and metrics with OpenTelemetry](https://docs.bronto.io/integrations/mysql.md): Collect self-hosted MySQL error and slow query logs plus database metrics with the OpenTelemetry Collector to debug slow queries and locking in Bronto.
- [Nginx logs, metrics, and traces with OpenTelemetry](https://docs.bronto.io/integrations/nginx.md): Collect Nginx access logs, error logs, stub_status metrics, and request traces with the OpenTelemetry Collector and forward all three signals to Bronto.
- [PostgreSQL logs and metrics with OpenTelemetry](https://docs.bronto.io/integrations/postgresql.md): Collect self-hosted PostgreSQL logs and database metrics — errors, slow queries, and connection activity — with the OpenTelemetry Collector.
- [RabbitMQ logs and metrics with OpenTelemetry](https://docs.bronto.io/integrations/rabbitmq.md): Collect self-hosted RabbitMQ broker logs and queue metrics — connections, channel activity, and node events — with the OpenTelemetry Collector.
- [Redis logs and metrics with OpenTelemetry](https://docs.bronto.io/integrations/redis.md): Collect self-hosted Redis server logs and cache metrics — slow log entries, replication events, and memory use — with the OpenTelemetry Collector.
- [Traefik logs and metrics with OpenTelemetry](https://docs.bronto.io/integrations/traefik.md): Collect Traefik access logs and Prometheus metrics — routing decisions, backend responses, and latency — with the OpenTelemetry Collector.
- [Ingest OpenTelemetry data into Bronto](https://docs.bronto.io/opentelemetry/overview.md): Instrument applications to send logs, metrics, and distributed traces to Bronto using the OpenTelemetry SDK and Collector over OTLP.
- [Zero-code instrumentation with eBPF](https://docs.bronto.io/opentelemetry/ebpf.md): Instrument applications with OpenTelemetry eBPF Instrumentation (OBI) to send traces and RED metrics to Bronto with no code changes and no redeploy.
- [Send Python logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/python.md): Instrument a Python application with the OpenTelemetry Python SDK to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send Python structlog and loguru logs to Bronto](https://docs.bronto.io/opentelemetry/python-structlog-loguru.md): Route Python structlog and loguru output through the OpenTelemetry Python SDK to send structured application logs to Bronto without rewriting log calls.
- [Send .NET logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/dotnet.md): Instrument .NET and ASP.NET Core applications with the OpenTelemetry .NET SDK to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send Java logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/java.md): Instrument Java applications with the OpenTelemetry Java agent to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send Node.js logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/nodejs.md): Instrument Node.js and JavaScript applications with the OpenTelemetry JS SDK to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send Go logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/go.md): Instrument Go applications with the OpenTelemetry Go SDK to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send Kotlin logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/kotlin.md): Instrument Kotlin and JVM applications with the OpenTelemetry Java agent to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send Ruby logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/ruby.md): Instrument Ruby and Rails applications with the OpenTelemetry Ruby SDK to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send PHP logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/php.md): Instrument PHP applications with the OpenTelemetry PHP SDK and auto-instrumentation to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send Erlang and Elixir logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/erlang-elixir.md): Instrument Erlang or Elixir BEAM applications with the OpenTelemetry SDK to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send Rust logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/rust.md): Instrument Rust applications with the OpenTelemetry Rust SDK to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send C++ logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/cpp.md): Instrument C++ applications with the OpenTelemetry C++ SDK to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [Send Swift logs, metrics, and traces to Bronto](https://docs.bronto.io/opentelemetry/swift.md): Instrument iOS, macOS, and server-side Swift apps with the OpenTelemetry Swift SDK to send logs, metrics, and traces to Bronto over OTLP/HTTP, via an OTel Collector or directly.
- [AI Overview](https://docs.bronto.io/ai-features/ai-welcome.md): Connect AI agents and MCP clients to Bronto, run AI-driven investigations, and turn raw telemetry into structured, queryable observability data.
- [Bronto Agent Skills](https://docs.bronto.io/ai-features/bronto-agent-skills.md): Install Bronto's agent skills and plugins for Cursor or Claude Code so coding agents can investigate telemetry and improve logging workflows.
- [Hosted MCP Server](https://docs.bronto.io/ai-features/hosted-mcp.md): Connect Claude and other MCP clients to Bronto's hosted MCP endpoint to query log data, no local server required, using your existing Bronto login.
- [Local MCP Server](https://docs.bronto.io/ai-features/local-mcp.md): Run the open-source Bronto MCP server locally with Python and connect Claude Code or any MCP agent to your datasets, API keys, and search tools.
- [BrontoScope](https://docs.bronto.io/ai-features/brontoscope.md): Investigate error events automatically with BrontoScope, an AI-powered tool that identifies scope, root causes, and next steps without writing queries.
- [AI Investigation Reports](https://docs.bronto.io/ai-features/ai-investigation-reports.md): Run automated AI investigations when a Bronto monitor fires, with prompt-guided analysis and reports covering likely causes, impact, and next steps.
- [LLM Observability](https://docs.bronto.io/ai-features/llm-observability.md): Capture, send, and search OpenTelemetry GenAI telemetry in Bronto — prompts, responses, token usage, model metadata, and tool calls from LLM apps.
- [Amazon Bedrock LLM observability with OpenTelemetry](https://docs.bronto.io/ai-features/aws-bedrock.md): Capture token usage, model metadata, and prompt/response content from Amazon Bedrock calls with OpenTelemetry GenAI auto-instrumentation in Bronto.
- [Amazon Bedrock AgentCore observability with OpenTelemetry](https://docs.bronto.io/ai-features/aws-agentcore.md): Route the OpenTelemetry logs, metrics, and traces an agent emits on Amazon Bedrock AgentCore Runtime — agent-loop spans, token usage, tool calls — to Bronto.
- [Send OpenLLMetry traces to Bronto](https://docs.bronto.io/integrations/openllmetry.md): Instrument LLM providers, agent frameworks, and vector databases with Traceloop OpenLLMetry and send the resulting OpenTelemetry traces to Bronto.
- [Send LangChain traces to Bronto via OpenTelemetry](https://docs.bronto.io/integrations/langchain.md): Instrument LangChain applications with OpenTelemetry and send their traces to Bronto, with an optional path for existing LangSmith users.
- [Custom Parser](https://docs.bronto.io/core-features/custom-parser.md): Generate custom log parsers automatically with LLMs to extract structured fields from Apache, IIS, HAProxy, Syslog, and custom log formats in Bronto.
- [AWS DevOps Agent Integration](https://docs.bronto.io/ai-features/aws-devops-agent.md): Register Bronto's hosted MCP server with the AWS DevOps Agent so it can search your Bronto logs and traces while investigating and operating workloads in AWS.
- [n8n Integration](https://docs.bronto.io/ai-features/n8n.md): Connect Bronto to n8n workflows to query logs, trigger automations on observability data, and build AI-assisted incident response pipelines.
- [OpenClaw Integration](https://docs.bronto.io/ai-features/openclaw.md): Instrument OpenClaw agents with OpenTelemetry to send AI agent logs, metrics, and traces to Bronto for observability, debugging, and cost tracking.
- [Vibe Building with Bronto](https://docs.bronto.io/ai-features/vibe-building.md): Build custom observability interfaces with Lovable, v0, and Bronto APIs for workflows such as usage dashboards, service maps, and focused operational views.
- [Bronto API](https://docs.bronto.io/api-reference/introduction.md): Manage logs, run searches, control users and access, and automate workflows in Bronto using a RESTful API authenticated with API keys or bearer tokens.
- [Retrieve a list of API keys](https://docs.bronto.io/api-reference/api-keys/retrieve-a-list-of-api-keys.md)
- [Create a new API key](https://docs.bronto.io/api-reference/api-keys/create-a-new-api-key.md)
- [Delete an API key](https://docs.bronto.io/api-reference/api-keys/delete-an-api-key.md)
- [Update an API key](https://docs.bronto.io/api-reference/api-keys/update-an-api-key.md)
- [Retrieve a list of users](https://docs.bronto.io/api-reference/users/retrieve-a-list-of-users.md)
- [Create a new user](https://docs.bronto.io/api-reference/users/create-a-new-user.md)
- [Retrieve a list of users](https://docs.bronto.io/api-reference/users/retrieve-a-list-of-users-1.md)
- [Retrieve a user by ID](https://docs.bronto.io/api-reference/users/retrieve-a-user-by-id.md): Retrieves detailed information for a specific user using their unique identifier. Returns all user attributes including profile information, roles, and status.
- [Delete a user by ID](https://docs.bronto.io/api-reference/users/delete-a-user-by-id.md): Permanently removes a user from the system. This action cannot be undone. All associated data and permissions for this user will be removed. Only administrators can delete users.
- [Update a user](https://docs.bronto.io/api-reference/users/update-a-user.md): Updates the specified user's information. Only the fields provided in the request body will be modified; other fields will remain unchanged. Users can typically update their own profiles, while administrators may update any user.
- [Deactivate a user](https://docs.bronto.io/api-reference/users/deactivate-a-user.md)
- [Reactivate a user](https://docs.bronto.io/api-reference/users/reactivate-a-user.md)
- [Resend a user's invitation email](https://docs.bronto.io/api-reference/users/resend-a-users-invitation-email.md)
- [Get user preferences](https://docs.bronto.io/api-reference/users/get-user-preferences.md): Returns the stored user preferences for the specified organization and user.
- [Patch user preferences](https://docs.bronto.io/api-reference/users/patch-user-preferences.md): Sets or updates specific user preferences without overwriting others.
- [List all organizations this user has access to](https://docs.bronto.io/api-reference/users/list-all-organizations-this-user-has-access-to.md)
- [List all user groups in the organization](https://docs.bronto.io/api-reference/groups/list-all-user-groups-in-the-organization.md)
- [Create a new group](https://docs.bronto.io/api-reference/groups/create-a-new-group.md)
- [Get a specific group](https://docs.bronto.io/api-reference/groups/get-a-specific-group.md)
- [Delete a group](https://docs.bronto.io/api-reference/groups/delete-a-group.md)
- [Update a group](https://docs.bronto.io/api-reference/groups/update-a-group.md)
- [List members of a group](https://docs.bronto.io/api-reference/groups/list-members-of-a-group.md)
- [Add members to a group](https://docs.bronto.io/api-reference/groups/add-members-to-a-group.md)
- [Remove members from a group](https://docs.bronto.io/api-reference/groups/remove-members-from-a-group.md)
- [List groups a member belongs to](https://docs.bronto.io/api-reference/groups/list-groups-a-member-belongs-to.md)
- [Execute a query](https://docs.bronto.io/api-reference/search/execute-a-query.md): You can execute queries on your log data by using Bronto's syntax based on a subset of SQL as described in the documentation https://docs.bronto.io/query-syntax/overview.
- [Execute a query](https://docs.bronto.io/api-reference/search/execute-a-query-1.md): You can execute queries on your log data by using Bronto's syntax based on a subset of SQL as described in the documentation https://docs.bronto.io/query-syntax/overview
- [Retrieve contextual information for a given sequence and log](https://docs.bronto.io/api-reference/context/retrieve-contextual-information-for-a-given-sequence-and-log.md)
- [Poll a live tail job](https://docs.bronto.io/api-reference/live-tail/poll-a-live-tail-job.md)
- [Initiate a live tail job](https://docs.bronto.io/api-reference/live-tail/initiate-a-live-tail-job.md)
- [Retrieve a list of logs](https://docs.bronto.io/api-reference/logs/retrieve-a-list-of-logs.md)
- [Create a new log](https://docs.bronto.io/api-reference/logs/create-a-new-log.md)
- [Retrieve a list of log views](https://docs.bronto.io/api-reference/logs/retrieve-a-list-of-log-views.md)
- [Retrieve a list of datasets](https://docs.bronto.io/api-reference/datasets/retrieve-a-list-of-datasets.md)
- [Create a new dataset](https://docs.bronto.io/api-reference/datasets/create-a-new-dataset.md)
- [Get the parser assigned to a dataset](https://docs.bronto.io/api-reference/datasets/get-the-parser-assigned-to-a-dataset.md)
- [Assign a parser to a dataset](https://docs.bronto.io/api-reference/datasets/assign-a-parser-to-a-dataset.md)
- [Unassign the parser from a dataset](https://docs.bronto.io/api-reference/datasets/unassign-the-parser-from-a-dataset.md)
- [List monitors associated with a log](https://docs.bronto.io/api-reference/monitors/list-monitors-associated-with-a-log.md)
- [Retrieve monitors](https://docs.bronto.io/api-reference/monitors/retrieve-monitors.md): Retrieves the list of currently configured monitors
- [Create a new monitor](https://docs.bronto.io/api-reference/monitors/create-a-new-monitor.md): Create a monitor to be notified when a log-based or metric-based condition is met
- [Retrieve monitor templates](https://docs.bronto.io/api-reference/monitors/retrieve-monitor-templates.md): Retrieves the list of monitor templates
- [Create a new monitor template](https://docs.bronto.io/api-reference/monitors/create-a-new-monitor-template.md): Create a monitor template to be notified when a log-based or metric-based condition is met
- [Get a monitor](https://docs.bronto.io/api-reference/monitors/get-a-monitor.md)
- [Update a monitor](https://docs.bronto.io/api-reference/monitors/update-a-monitor.md): Update an existing monitor
- [Delete a monitor](https://docs.bronto.io/api-reference/monitors/delete-a-monitor.md)
- [Get a monitor template](https://docs.bronto.io/api-reference/monitors/get-a-monitor-template.md)
- [Update a monitor template](https://docs.bronto.io/api-reference/monitors/update-a-monitor-template.md): Update an existing monitor template
- [Delete a monitor template](https://docs.bronto.io/api-reference/monitors/delete-a-monitor-template.md)
- [return the list of monitor notifications](https://docs.bronto.io/api-reference/monitors/return-the-list-of-monitor-notifications.md)
- [Update monitor status](https://docs.bronto.io/api-reference/monitors/update-monitor-status.md): Update the status of a monitor - only supports muting/unmuting
- [List dashboards associated with a log](https://docs.bronto.io/api-reference/dashboards/list-dashboards-associated-with-a-log.md)
- [Get all dashboards for an organisation](https://docs.bronto.io/api-reference/dashboards/get-all-dashboards-for-an-organisation.md)
- [Create a dashboard](https://docs.bronto.io/api-reference/dashboards/create-a-dashboard.md)
- [Get a single Dashboard by ID](https://docs.bronto.io/api-reference/dashboards/get-a-single-dashboard-by-id.md)
- [Delete a dashboard by ID](https://docs.bronto.io/api-reference/dashboards/delete-a-dashboard-by-id.md)
- [Partially update a dashboard by ID, allowing either a name change or modification of widget IDs (append or remove)](https://docs.bronto.io/api-reference/dashboards/partially-update-a-dashboard-by-id-allowing-either-a-name-change-or-modification-of-widget-ids-append-or-remove.md)
- [Detach a dashboard from a template](https://docs.bronto.io/api-reference/dashboards/detach-a-dashboard-from-a-template.md)
- [Append widgets to a dashboard](https://docs.bronto.io/api-reference/dashboards/append-widgets-to-a-dashboard.md)
- [Remove a widget from a dashboard](https://docs.bronto.io/api-reference/dashboards/remove-a-widget-from-a-dashboard.md)
- [Retrieve a list of collections](https://docs.bronto.io/api-reference/collections/retrieve-a-list-of-collections.md)
- [Grant access to a user or group](https://docs.bronto.io/api-reference/access/grant-access-to-a-user-or-group.md)
- [Revoke access from a user or group](https://docs.bronto.io/api-reference/access/revoke-access-from-a-user-or-group.md)
- [List all members who have access to this organization](https://docs.bronto.io/api-reference/access/list-all-members-who-have-access-to-this-organization.md)
- [Check if user or group has access to org](https://docs.bronto.io/api-reference/access/check-if-user-or-group-has-access-to-org.md)
- [Switch active organization for a user](https://docs.bronto.io/api-reference/access/switch-active-organization-for-a-user.md): Sets the specified organization as the active organization for the user. The user must already have access to this organization.
- [Retrieve all monitor downtimes](https://docs.bronto.io/api-reference/downtimes/retrieve-all-monitor-downtimes.md): Retrieves the list of currently configured downtimes
- [Create a new monitor downtime](https://docs.bronto.io/api-reference/downtimes/create-a-new-monitor-downtime.md): Create a downtime to silence monitors periodically
- [Update a monitor downtime](https://docs.bronto.io/api-reference/downtimes/update-a-monitor-downtime.md): update an existing downtime
- [Delete a monitor downtime](https://docs.bronto.io/api-reference/downtimes/delete-a-monitor-downtime.md)
- [return the list of monitor events](https://docs.bronto.io/api-reference/events/return-the-list-of-monitor-events.md)
- [Retrieve forward configs](https://docs.bronto.io/api-reference/forward/retrieve-forward-configs.md): Retrieves the list of all forward configs set up for the account
- [Create a new forward config to archive your logs in another system](https://docs.bronto.io/api-reference/forward/create-a-new-forward-config-to-archive-your-logs-in-another-system.md): Create a forward config, to forward log events outside the Bronto system (e.g. archive logs in an S3 bucket)
- [Test access to the destination](https://docs.bronto.io/api-reference/forward/test-access-to-the-destination.md): Check access to the destination. A test file will be created and deleted to make sure Bronto can access your destination
- [Update an existing forward config](https://docs.bronto.io/api-reference/forward/update-an-existing-forward-config.md): Update a forward config, to forward log events outside the Bronto system (e.g. archive logs in an S3 bucket)
- [Delete a forward config](https://docs.bronto.io/api-reference/forward/delete-a-forward-config.md)
- [Retrieve top keys for logs](https://docs.bronto.io/api-reference/top-keys/retrieve-top-keys-for-logs.md): Retrieves the most frequently occurring keys (field names) from log events within a specified time range. This is useful for understanding the structure and common fields present in your log data. If no log ID is specified, top keys are returned for all accessible logs.
- [Retrieve all the widgets](https://docs.bronto.io/api-reference/widgets/retrieve-all-the-widgets.md)
- [Create a widget](https://docs.bronto.io/api-reference/widgets/create-a-widget.md)
- [Retrieve a widget](https://docs.bronto.io/api-reference/widgets/retrieve-a-widget.md)
- [Update a widget](https://docs.bronto.io/api-reference/widgets/update-a-widget.md)
- [Delete a widget](https://docs.bronto.io/api-reference/widgets/delete-a-widget.md)
- [Partially update a widget by ID](https://docs.bronto.io/api-reference/widgets/partially-update-a-widget-by-id.md)
- [Append widgets to a widget](https://docs.bronto.io/api-reference/widgets/append-widgets-to-a-widget.md)
- [Remove a widget from a widget](https://docs.bronto.io/api-reference/widgets/remove-a-widget-from-a-widget.md)
- [Retrieve usage metrics over time](https://docs.bronto.io/api-reference/usage/retrieve-usage-metrics-over-time.md): Retrieves usage statistics for your organization over a specified time period. Usage metrics include data ingestion volumes, search query counts, and export activities. The results can be broken down into time slices and optionally compared against previous periods for trend analysis.
- [Get the usage over a period of time for a log id.](https://docs.bronto.io/api-reference/usage/get-the-usage-over-a-period-of-time-for-a-log-id.md)
- [Get the usage over a period of time for a user per log id.](https://docs.bronto.io/api-reference/usage/get-the-usage-over-a-period-of-time-for-a-user-per-log-id.md)
- [Get all Slack Integration Resources for an organisation](https://docs.bronto.io/api-reference/integrations/get-all-slack-integration-resources-for-an-organisation.md)
- [Create a Slack Integration Resource](https://docs.bronto.io/api-reference/integrations/create-a-slack-integration-resource.md)
- [Update a Slack Integration Resource](https://docs.bronto.io/api-reference/integrations/update-a-slack-integration-resource.md)
- [Delete a Slack Integration Resource](https://docs.bronto.io/api-reference/integrations/delete-a-slack-integration-resource.md)
- [Get all Slack workspace resources for an organisation](https://docs.bronto.io/api-reference/integrations/get-all-slack-workspace-resources-for-an-organisation.md)
- [Delete a Slack workspace resource; note this does not uninstall the bronto.io app from Slack](https://docs.bronto.io/api-reference/integrations/delete-a-slack-workspace-resource;-note-this-does-not-uninstall-the-brontoio-app-from-slack.md)
- [Get all Webhook Integration Resources for an organisation](https://docs.bronto.io/api-reference/integrations/get-all-webhook-integration-resources-for-an-organisation.md)
- [Create a Webhook Integration Resource](https://docs.bronto.io/api-reference/integrations/create-a-webhook-integration-resource.md)
- [Update a webhook Integration Resource](https://docs.bronto.io/api-reference/integrations/update-a-webhook-integration-resource.md)
- [Delete a webhook Integration Resource](https://docs.bronto.io/api-reference/integrations/delete-a-webhook-integration-resource.md)
- [Retrieve a list of exports](https://docs.bronto.io/api-reference/exports/retrieve-a-list-of-exports.md)
- [Create a new export](https://docs.bronto.io/api-reference/exports/create-a-new-export.md): Creates an export from either explicit log ids in `from` or a dataset selector in `from_expr`. When `from_expr` is supplied, it is resolved at creation time and the resulting log ids are persisted in `search_details.from` for export processing.
- [Retrieve an export by ID](https://docs.bronto.io/api-reference/exports/retrieve-an-export-by-id.md)
- [Delete an export by ID](https://docs.bronto.io/api-reference/exports/delete-an-export-by-id.md)
- [Get the customer record for the current organization](https://docs.bronto.io/api-reference/customers/get-the-customer-record-for-the-current-organization.md)
- [Update the customer record for the current organization](https://docs.bronto.io/api-reference/customers/update-the-customer-record-for-the-current-organization.md)
- [Update a tag](https://docs.bronto.io/api-reference/tags/update-a-tag.md): Update the value of a tag.
- [Create a tag](https://docs.bronto.io/api-reference/tags/create-a-tag.md): Create a tag and associate it with an entity.
- [Delete a tag](https://docs.bronto.io/api-reference/tags/delete-a-tag.md)
- [List tags](https://docs.bronto.io/api-reference/tags/list-tags.md): Retrieve a list of tags, optionally filtered by name, value, or entity type.
- [Retrieve limits](https://docs.bronto.io/api-reference/limits/retrieve-limits.md): Retrieves the list of limits configured for the organisation. Limits define thresholds and constraints applied to resources within your account.
- [Create a new limit](https://docs.bronto.io/api-reference/limits/create-a-new-limit.md): Create a limit
- [Get a Limit](https://docs.bronto.io/api-reference/limits/get-a-limit.md)
- [Delete a limit by ID](https://docs.bronto.io/api-reference/limits/delete-a-limit-by-id.md)
- [Update a limit](https://docs.bronto.io/api-reference/limits/update-a-limit.md): update an existing limit
- [Retrieve permissions](https://docs.bronto.io/api-reference/permissions/retrieve-permissions.md): Retrieves a list of all available permissions grouped by resource. Permissions define the individual actions that can be performed within the system, such as reading API keys or managing monitors. Permissions are assigned to roles, which in turn are assigned to users and API keys. Use the `/roles` e…
- [Get the parsers usage metrics over a period of time for a log id.](https://docs.bronto.io/api-reference/parsers/get-the-parsers-usage-metrics-over-a-period-of-time-for-a-log-id.md)
- [Get the parsers usage metrics over a period of time for a log id.](https://docs.bronto.io/api-reference/parsers/get-the-parsers-usage-metrics-over-a-period-of-time-for-a-log-id-1.md)
- [Ask AI to give hints regarding a particular error](https://docs.bronto.io/api-reference/ai/ask-ai-to-give-hints-regarding-a-particular-error.md)
- [Ask AI to provide a widget based on a prompt request](https://docs.bronto.io/api-reference/ai/ask-ai-to-provide-a-widget-based-on-a-prompt-request.md)
- [List policies by resource](https://docs.bronto.io/api-reference/policies/list-policies-by-resource.md)
- [Retrieve a list of encryption keys](https://docs.bronto.io/api-reference/encryption-keys/retrieve-a-list-of-encryption-keys.md)
- [Create a new encryption key](https://docs.bronto.io/api-reference/encryption-keys/create-a-new-encryption-key.md)
- [Retrieve a specific encryption key](https://docs.bronto.io/api-reference/encryption-keys/retrieve-a-specific-encryption-key.md)
- [Delete an encryption key](https://docs.bronto.io/api-reference/encryption-keys/delete-an-encryption-key.md): Delete an encryption key. Keys can only be deleted when their status is CREATED.
- [Update an existing encryption key](https://docs.bronto.io/api-reference/encryption-keys/update-an-existing-encryption-key.md): Update an encryption key's display name and/or status. Only name and status can be updated. Status can only transition from CREATED to ACTIVE.
- [Retrieve the timeseries for a metric definition.](https://docs.bronto.io/api-reference/timeseries/retrieve-the-timeseries-for-a-metric-definition.md)
- [Run an ad-hoc timeseries query](https://docs.bronto.io/api-reference/timeseries/run-an-ad-hoc-timeseries-query.md): Execute a one-off timeseries query or formula directly. This is not saved.   Use for interactive mode or metrics explorer.
- [Get Pattern templates for logs matching search criteria](https://docs.bronto.io/api-reference/patterns/get-pattern-templates-for-logs-matching-search-criteria.md): Returns the Pattern IDs, templates, and source log ID for all logs matching the given search criteria.
- [API Key Authentication](https://docs.bronto.io/api-reference/api-keys/overview.md): Authenticate Bronto API requests with API keys passed in the X-BRONTO-API-KEY header. Roles assigned to each key control which endpoints are available.
- [Retrieve contextual information for a given sequence and log](https://docs.bronto.io/api-reference/context/get-context.md): Retrieve the log events immediately before, after, or surrounding a specific event of interest to investigate incidents and reconstruct request timelines.
- [Context API](https://docs.bronto.io/api-reference/context/overview.md): Use the Bronto Context REST API to retrieve log events surrounding a specific event of interest, before, after, or both, for faster troubleshooting.
- [Delete an export by ID](https://docs.bronto.io/api-reference/exports/delete-an-export.md): Delete a Bronto export job by ID to cancel an in-progress export or remove the download URL for a completed export from your organization.
- [Retrieve an export by ID](https://docs.bronto.io/api-reference/exports/get-export-by-id.md): Poll the status and progress percentage of an asynchronous Bronto export job by ID, and retrieve the signed download URL once the export completes.
- [Exports API](https://docs.bronto.io/api-reference/exports/overview.md): Use the Bronto Exports REST API to download large volumes of log data asynchronously, filtered by query, with status polling and direct download URLs.
- [Create a new forward config to archive your logs in another system](https://docs.bronto.io/api-reference/forward/create-new-config.md): Create a forward config, to forward log events outside the Bronto system (e.g. archive logs in an S3 bucket)
- [Delete a forward config](https://docs.bronto.io/api-reference/forward/delete-a-config.md): Delete a Bronto log forwarding configuration by ID to stop archiving matching log events to the configured S3, GCS, or HTTP destination.
- [Test access to the destination](https://docs.bronto.io/api-reference/forward/test-access-to-destination.md): Check access to the destination. A test file will be created and deleted to make sure Bronto can access your destination
- [Update an existing forward config](https://docs.bronto.io/api-reference/forward/update-existing-config.md): Update a forward config, to forward log events outside the Bronto system (e.g. archive logs in an S3 bucket)
- [Create a new log](https://docs.bronto.io/api-reference/logs/create-log.md): Create a new Bronto log dataset to receive timestamped events, with a configurable name, parser, retention, and metadata for routing ingested data.
- [Retrieve a list of logs](https://docs.bronto.io/api-reference/logs/get-logs.md): Retrieve the list of log datasets in your Bronto organization with metadata such as IDs, names, and retention settings to inspect or build search queries.
- [Logs API](https://docs.bronto.io/api-reference/logs/overview.md): Use the Bronto Logs REST API to create new log datasets and retrieve metadata for logs that can be searched, filtered, and aggregated across your organization.
- [Cancel an asynchronous search](https://docs.bronto.io/api-reference/search/delete-search.md): Cancel a long-running asynchronous Bronto search by its status identifier to stop the query and free up search capacity for other workloads.
- [Get asynchronous search status](https://docs.bronto.io/api-reference/search/get-search-status.md): Poll the status, progress, and partial results of an asynchronous Bronto search query by its status identifier to track long-running search jobs.
- [Execute a query](https://docs.bronto.io/api-reference/search/post-search.md): You can execute queries on your log data by using Bronto's syntax based on a subset of SQL as described in the documentation https://docs.bronto.io/query-syntax/overview
- [Execute a query](https://docs.bronto.io/api-reference/search/search.md): You can execute queries on your log data by using Bronto's syntax based on a subset of SQL as described in the documentation https://docs.bronto.io/query-syntax/overview.
- [Retrieve top keys for logs](https://docs.bronto.io/api-reference/top-keys/get-top-keys.md): Retrieves the most frequently occurring keys (field names) from log events within a specified time range. This is useful for understanding the structure and common fields present in your log data. If no log ID is specified, top keys are returned for all accessible logs.
- [Top Keys API](https://docs.bronto.io/api-reference/top-keys/overview.md): Use the Bronto Top Keys REST API to retrieve the most frequent keys and values for a dataset to understand cardinality and inform query design.
- [Get the usage over a period of time for a log id.](https://docs.bronto.io/api-reference/usage/get-usage-for-log-id.md): Retrieve Bronto ingestion and search usage for a specific log dataset over a chosen timeframe to monitor costs, capacity, and billing trends per log ID.
- [Get the usage over a period of time for a user per log id.](https://docs.bronto.io/api-reference/usage/get-usage-for-user-per-log-id.md): Retrieve Bronto ingestion and search volume broken down by user and log dataset over a chosen timeframe to attribute usage and identify heavy consumers.
- [Usage API](https://docs.bronto.io/api-reference/usage/overview.md): Use the Bronto Usage REST API to track ingestion and search volume per dataset over a chosen timeframe and drill into per-user or per-log breakdowns.
- [Retrieve a user by ID](https://docs.bronto.io/api-reference/users/get-a-single-user-by-id.md): Retrieves detailed information for a specific user using their unique identifier. Returns all user attributes including profile information, roles, and status.
- [Users API](https://docs.bronto.io/api-reference/users/overview.md): Use the Bronto Users REST API to create, list, update, and delete users and assign Admin, Standard, or ReadOnly roles that control their permissions.
- [Update a user](https://docs.bronto.io/api-reference/users/updates-a-user.md): Updates the specified user's information. Only the fields provided in the request body will be modified; other fields will remain unchanged. Users can typically update their own profiles, while administrators may update any user.
- [FAQ](https://docs.bronto.io/FAQ.md): Answers to common questions about the Bronto observability platform, including ingestion, retention, querying, integrations, and account configuration.
- [Custom Log Ingestion](https://docs.bronto.io/getting-started/custom-ingestion.md): Send log events directly to Bronto via HTTP using the Ingestion API — with full control over compression, batching, metadata, and authentication.
- [AWS S3 Access Log](https://docs.bronto.io/integrations/aws.md): Set up the AWS S3 access log integration in Bronto to ingest server access logs from S3 buckets and analyze object access, requests, and errors.

## OpenAPI Specs

- [brontobytes](https://docs.bronto.io/api-reference/brontobytes.yaml)

## Optional

- [Trust](https://trust.bronto.io/)
- [Book a Demo](https://www.bronto.io/book-a-demo)
- [Status](https://status.bronto.io)