See every request, end to end.
Hosted OpenTelemetry observability. Send traces, logs and metrics to one OTLP endpoint, then search them, chart them and alert on them in one console.
Prepaid credits from $10 USD. No subscription, and credits never expire.
- Investigate: summary tiles above the waterfall of one failing checkout request across checkout-api, inventory and payments-svc.
- Logs: a volume histogram stacked by severity, a log table and the detail panel of one error record with its JSON.
- Metrics: average request duration by service as a line chart, with a legend table of minimum, maximum, average and current values.
- Alerts: alert rules with their state (firing, pending, OK or disabled), condition, last evaluation and channels.
Sample data. Pick a page above, or in the window’s side menu.
All capabilities
The pages in the console’s side menu, grouped the way the console groups them. Overview, Events and Jobs are on the product page too.
Explore
From your code to the console
Four steps between an exporter and a chart. How it works, in detail.
- 1
Send
An OpenTelemetry SDK or Collector posts OTLP over HTTPS to one endpoint, with a project key in the
Authorizationheader. - 2
Clean
Attributes with sensitive names are dropped, secret-looking values are redacted and sizes are bounded, before anything is stored.
- 3
Store
Every record is stamped with the project of the key that sent it. Dashboards, alert rules and keys live in a separate application database.
- 4
Read and alert
The console queries the project you are working in. An evaluator checks every enabled alert rule every 30 seconds.
One endpoint, standard OTLP
Create a project and an ingest key in the app. Point your exporter at the endpoint and add one header: for a service that already speaks OpenTelemetry, that is the whole change. A 204 means the data was accepted.
# Send one span. Create the key in the app under Settings › API Keys.
$ NOW=$(( $(date +%s) * 1000000000 )); END=$(( NOW + 120000000 ))
$ curl -sS -o /dev/null -w "%{http_code}\n" -X POST "https://ingest.boltsight.app/v1/traces" \
-H "Authorization: Bearer $BOLT_SIGHT_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<EOF
{"resourceSpans":[{
"resource":{"attributes":[{"key":"service.name","value":{"stringValue":"quickstart"}}]},
"scopeSpans":[{"spans":[{
"traceId":"5b8efff798038103d269b633813fc60c","spanId":"eee19b7ec3c1b174",
"name":"GET /hello","kind":2,
"startTimeUnixNano":"$NOW","endTimeUnixNano":"$END",
"status":{"code":1}
}]}]
}]}
EOF
204# Any OpenTelemetry SDK, in any language
OTEL_SERVICE_NAME=billing-worker
OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.boltsight.app
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer%20bsk_your_project_key// Node.js SDK: call init() before any other import. Install steps are on the Developers page in the app.
init({
endpoint: "https://ingest.boltsight.app",
apiKey: process.env.BOLT_SIGHT_API_KEY!, // bsk_…, one key per producer
serviceName: "checkout-api",
environment: "production",
});How your telemetry is handled
The controls the service applies, as the code enforces them. Security and data handling.
- Write-only ingest keys
- A key can send telemetry to one project and nothing else. It cannot read data or sign in, and only its hash is stored.
- Cleaned on arrival
- Attributes named like a password or token are dropped, secret-looking values are redacted and sizes are bounded, before storage, Live Tail and alerts see them.
- Scoped to a project
- Every record carries the project of the key that sent it, and every console query runs in a project you belong to.
Metered usage, paid from prepaid credits
There is no subscription. You buy a pack from your project’s Billing page and usage draws it down.
- Packs
- $10 to $210 USD, each a one-time payment
- Rate
- $1 buys 1,000 credits, in every pack
- Usage
- 1 credit pays for 1,000 ingested records (spans, log records or metric data points) or 10 query attempts
- Expiry
- Credits never expire
- Out of credits
- Ingestion and queries pause until you buy another pack
- More than $210
- Contact sales
Questions
Anything else: contact us.
What can I send to Bolt Sight?
Traces, metrics and logs as OpenTelemetry (OTLP) over HTTP, in protobuf or JSON, from any language with an OpenTelemetry SDK. Thin Node.js and browser SDKs are available too, and the browser SDK also collects Web Vitals. See Integrations.
Do I have to run it myself?
No. This is the hosted service, made and operated by Techsstuff LLC. Sign in at console.boltsight.app, create a project and an ingest key, and start sending. About Bolt Sight and Techsstuff LLC.
How is usage counted?
1 credit = 1,000 ingested records (spans, log records or metric data points) or 10 query attempts. Credits never expire; when they run out, ingestion and queries pause until you buy another pack.
Is there a limit on request size?
Each OTLP request can carry up to 4 MB and 10,000 records. Gzip is accepted, and the limit applies after decompression. Attributes are capped at 64 per record and log bodies at 8 KB. Every limit is on the developer page.
How long is telemetry kept?
Traces, logs and error events are kept for 8 days and metrics for 90 days; the daily totals behind the Events page are kept for 400 days. See what is stored where.
Where do I get help or a refund?
Email or call us from the support page or the contact page. Purchases fall under the refund and cancellation policy.