Bronto and Datadog: A Practical Guide to Scaling Log Management
YOUR-BRONTO-API-KEY
with your key and <REGION>
with us
or eu
.
payments-api
, nginx
)production
, web-tier
)service.name
→ Datasetservice.namespace
→ Collectionenvironment
, version
→ searchable contextservice.name
, env
, and version
. There’s no need to preselect a dataset or learn a new syntax. It just works.
One thing that might feel unfamiliar is that you don’t have to choose which logs to index. In Bronto, all logs are indexed and searchable by default.
For advanced use cases, Bronto supports SQL-like queries, but most users won’t need them to get started.See full search syntax and tips in our docs
service
, env
, or version
, they’re available in Bronto out of the box and ready to use in search.
You can also add or adjust tags via UI or API as needed.
us
, eu
, etc.):https://app.<REGION>.bronto.io/search?query=[...]
$service
to your service tag$env
to your environment tag$fromTs
and $toTs
to timestamps provided by the Datadog time windowIf you’re not sure where to start, begin by routing one high-volume log type — such as CDN access logs — into Bronto and see what it unlocks.
Concept | In Datadog | In Bronto |
---|---|---|
Log grouping | Index | Collection + Dataset |
Log source | service | service.name |
Environment | env | env |
Version | version | version |
Search/filter syntax | key:value | key:value |
Autocomplete | Tag-based | Attribute and tag-based |
Retention extension | Cold storage or rehydration | Native, hot, searchable |