/* Bronto Welcome Page Custom Styling */
[data-page="welcome"] {
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: center;
    text-align: center;
    padding: 4rem 2rem;
}

[data-page="welcome"] h1 {
    font-size: 3rem;
    font-weight: bold;
    color: #F4C430; /* Bronto Gold */
    margin-bottom: 1.5rem;
}

[data-page="welcome"] .content-container {
    max-width: 800px;
    margin: 0 auto;
}

[data-page="welcome"] .side-nav {
    display: none; /* Hide sidebar */
}

[data-page="welcome"] img {
    max-width: 100%;
    height: auto;
    margin-bottom: 2rem;
}

[data-page="welcome"] .CardGroup {
    display: grid;
    grid-template-columns: 1fr;
    gap: 1.5rem;
    margin-top: 2rem;
}

[data-page="welcome"] .Card {
    background: #1e1e1e;
    color: white;
    padding: 1.5rem;
    border-radius: 8px;
    transition: transform 0.2s ease-in-out;
}

[data-page="welcome"] .Card:hover {
    transform: scale(1.05);
}

[data-page="welcome"] .Card h2 {
    font-size: 1.5rem;
    color: #F4C430; /* Bronto Gold */
    margin-bottom: 0.5rem;
}

Cancel a currently in-progress query & stop related processing. A cancelled query will not count towards
search usage.


Cancel an in-progress query

ApiKeyAuth

BearerAuth

Bad Request - The body in the request is invalid.

Not Found - The status with given ID does not exist.

Too Many Request - Fair usage limits exceeded

Internal Server Error - An error occurred on the server side.

Bronto

Welcome to Bronto

In Bronto Docs, you will find comprehensive guides to assist you in seamlessly integrating and using Bronto. 

Introduction

The [Agent setup](/getting-started/agent-setup) guide provides the necessary information to set up either Fluent Bit or Vector for forwarding your log data to Bronto.

Quick Ingest

Stream CDN logs from Akamai Datastream2 to Bronto

Akamai

Cloudflare provides a feature named Logpush that enables logs to be forwarded to 3rd party logging solutions. Logs are delivered near realtime in small batches.

Cloudflare

Fastly provides a feature to stream service logs to 3rd party solutions.

Fastly

This guide explains how to forward Azure logs to Bronto using Azure Event Hub and the Bronto log forwarder.

Azure Forwarder

The Search page in Bronto provides you with a powerful log explorer that allows you to quickly scan through millions of events to find the ones you need, and allows you to gain valuable insights through numerical queries.

Log Search

Bronto provides a simple point-and-click query builder for you to search, analyse and visualise your log data. We have several views which include Timeseries, Table, Top List, Pie Chart and Tree Map. These are explained in more detail here.

Query Syntax

You can leverage our query language to write search queries that allow you to visualiuze your log data in multiple ways.

Log Visualization

Bronto dashboards are a powerful way to visualize your log data and gain insights into your application's performance. Dashboards are driven by log-based metrics, which are calculated based on the log data you have ingested.

Dashboards

Saved Views make it easier for you and your organisation to switch between different troubleshooting contexts. You can access your account's saved views in the upper left corner of the UI.

Saved Views

Monitoring all of your infrastructure in one place would not be complete without the ability to know when critical changes are occurring.

Overview

Monitors

Your Bronto Usage

Bronto offers a flexible access management system that allows you to customize the level at which you control access to your Bronto resources.

Access Control

API keys are unique to your organization. An API key is used by our logging integration methods as a unique identifier to route log data to your account. Using an API key alongside a Service name and Service namespace in your logging configurations, alows us to route log data to the correct service.

API Keys

To invite, modify or remove users, navigate to Settings page from the application sidebar, then select Users.

User Management

User Mangement

At Bronto, we prioritize the security and privacy of your data. We adhere to the highest standards of compliance and employ advanced security measures to protect your information.

Security

Bronto and Datadog: A Practical Guide to Scaling Log Management

Datadog

Bronto and Coralogix: A Practical Guide to Scaling Log Management

Coralogix

A powerful API for seamless log ingestion, data retrieval, and system management at scale.

Bronto API (1.0.0)

An Application Programming Interface (API) key is a unique identifier. The API Key must be provided as X-BRONTO-API-KEY in headers for the request to be authenticated and authorized by the API server according to the API Key's role. For further information about roles visit [our API Key docs] [/manage/manage-api-keys](/manage/manage-api-keys)

api-keys

Retrieve a list of API keys

Create a new API key

Delete an API key

Update an API key

Users are given specific roles, where each role determines the user's permissions within the application. Those roles are as follows:

Users

Retrieve a list of users

Create a new user

Get a single user by ID

Delete a user by ID

Updates a user

Context is a REST API resource that allows the retrieval of a specified number of log events (default of 100) around a log event of interest, e.g. when a number of log events were returned by a previous query and you then decide you want to see the 50 log events before one of those returned log events. Log events can be retrieved either before, after, or both before and after the specified log event.

context

Retrieve contextual information for a given sequence and log

exports

Retrieve an export by ID

Delete an export by ID

Create a new export

Retrieve a list of exports

Logs are a sequence of timestamped log events. Logs can be searched to view events matching a filter or to perform statistical functions on matching events.

logs

Create a new log

Retrieve a list of logs

Usage is a REST API resource that allows you to easily track your Bronto usage by retrieving usage data relating to data ingestion and amount of data searched, and allowing you to drill down for a specific dataset over a defined timeframe.

Get the usage over a period of time for a log id.

Get the usage over a period of time for a user per log id.

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.brontobytes.io/core-features/log-search/query-syntax/. 

Bronto supports both the GET and POST methods for executing a query, however the POST method is
preferred as it avoids problems related to maximum URL length when the query parameters are very long.

In the context of the REST API, there are three distinct types queries which determine which parts of the 
response object are populated:
+ Event search queries return a list of events matching the specified filter.
The response will be paginated if more than `limit` (default 50) matching events are returned.
+ Aggregate queries apply aggregate functions such as count(), sum(), max(), avg()
to your log data, and return a number or a timeseries of numbers.
+ Group by aggregate queries return numerical results grouped according to the values for the
attributes specified in the group by clause.

The query type is determined by the combination of the `select` and `groups` parameters.


Execute a query

Bronto provides an async API for long-running queries, which allows users to poll an in-progress query to monitor
its progress and to receive partial results. It also allows an API client to handle multiple requests concurrently
without blocking, and is more tolerant of network failures since a query will continue to execute if a connection
is broken. Additionally it allows clients to cancel requests they are no longer interested in. For extremely long 
running queries it helps avoid issues due to timeouts.

When the client makes an async query request, the server will initially respond with either a `201` or a `202` response code.
The `201` response code is returned if the query was very short and the results are immediately available. 
Otherwise, if the query has started and is in-progress, the server will return a `202` response code and the 
response body will contain a status endpoint link (`/search/status/<status id>`) which should be polled periodically.
When polled, the server will continue to respond with a `202` response code if the query is still in-progress, or it
will respond with a `201` response code if the query has completed.
The link must be polled at least once every 1 minute, otherwise the query will be cancelled. 
Once a query is completed the results can be retrieved using the status endpoint for at least 5 minutes,
and up to 7 days (if the query results have expired the server will respond with a `410` response code).


Poll a Query In Progress

Create a forward config, to forward log events outside the Bronto system (e.g. archive logs in an S3 bucket)

Create a new forward config to archive your logs in another system

Delete a forward config

Retrieves the list of all forward configs set up for the account

Retrieve forward configs

Check access to the destination. A test file will be created and deleted to make sure Bronto can access your destination

Test access to the destination

Update a forward config, to forward log events outside the Bronto system (e.g. archive logs in an S3 bucket)

Api Keys endpoints

User endpoints

Context endpoints

Export endpoints

Logs endpoints

Usage endpoints

Search endpoints

Forward endpoints

Cancel an in-progress query

Authorizations

Path Parameters

Response