- Home
- Game Crash Reporting Software
- NHN Cloud Log & Crash Search
NHN Cloud Log & Crash Search
Seongnam-si, Gyeonggi-do, South Korea
What it is
NHN Cloud Log & Crash Search collects client and server application logs for viewing and searching. Logs reach its collector over HTTP as JSON, including bulk JSON-array delivery. The Log Search API accepts Lucene queries and requires a project secret key in each request header. Searches can cover only the previous 90 days, and one time range may span no more than 31 days. Results are paged in batches of up to 100 logs, with documentation describing paging through as many as 100,000 logs. HTTP ingestion requests are limited to 52 MB, while an individual JSON log may be up to 8 MB. Search usage consumes tokens according to duration, result size, and query complexity; tokens replenish over time. Source maps are supported. Listed platforms are Android, iOS, web, Windows, and API. NHN Cloud was founded in 2014 and is headquartered in Seongnam-si, South Korea. Pricing is by custom estimate based on selected features, with no product price shown.
For and against
For
- Accepts individual and bulk JSON logs
- Lucene queries through a documented API
- Supports source maps
- Paging handles large result sets
- Available across mobile, web, Windows, and API
Against
- Searches only cover the past 90 days
- Search ranges cannot exceed 31 days
- Requests and logs have size limits
- Pricing requires a custom estimate
The verdict
NHN Cloud Log & Crash Search provides structured ingestion and Lucene-based retrieval with explicit limits. Teams should account for retention windows, token usage, and API credentials in their design.
Who it suits
It suits teams that need API-based collection and querying of application logs across client and server software. It is also relevant for organizations working within defined retention, request-size, and token limits.
Plans and prices
Custom quote
Select needed features for a custom estimate
Read 4 Oct 2026 · nhncloud.com
On the record
- API access
- Log search API requests must include the project secret key in the request header.docs.nhncloud.com · read 4 Oct 2026
- Bulk ingestion
- The collector accepts bulk log delivery in JSON array format.docs.nhncloud.com · read 4 Oct 2026
- Headquarters address
- The NHN Cloud Japan page lists its address as NHN Atelier, 3-1-8 Nishi-Shimbashi, Minato-ku, Tokyo.nhncloud.com · read 4 Oct 2026
- Ingestion limits
- The API guide limits an HTTP request to 52 MB and an individual JSON log to 8 MB.docs.nhncloud.com · read 4 Oct 2026
- Log ingestion
- Logs can be sent to the collector over HTTP as JSON.docs.nhncloud.com · read 4 Oct 2026
- Pricing
- The pricing page offers a custom estimate based on selected features and does not state a product price in the opened page.nhncloud.com · read 4 Oct 2026
- Purpose
- Collects and stores client and server application logs so users can view or search them.nhncloud.com · read 4 Oct 2026
- Query allowance
- Search API usage is limited by tokens that are deducted according to search duration, size, and query complexity, and replenished over time.docs.nhncloud.com · read 4 Oct 2026
- Search
- Saved logs can be searched using Lucene queries through the Log Search API.docs.nhncloud.com · read 4 Oct 2026
- Search pagination
- The search API supports pages of up to 100 logs and documents searching up to 100,000 logs through paging.docs.nhncloud.com · read 4 Oct 2026
- Search window
- The API guide says only logs from the past 90 days can be searched, and a search time range cannot exceed 31 days.docs.nhncloud.com · read 4 Oct 2026
- Support contact
- The NHN Cloud Japan page lists [email protected] as its contact email.nhncloud.com · read 4 Oct 2026
