Skip to content

Send Test Logs

Overview

You can send test logs to check whether data is collected as intended. You can test in both the sandbox environment and the production environment, and in either environment the test follows the steps below.

Step Description Menu
1. Send Test Logs Send test logs in the environment you want to test. Data > Event > [Source Creation] tab or [ETL Simulation] tab
2. Check Reception Check whether the sent data has been collected. Data > Event > [Data Preview] tab or BigQuery
3. Check Metric Configuration Check whether you can build the metrics you want with the collected data. Create (Chart, Funnel, Retention, Ranking, etc.)

Test Environment

Environment Send To Storage Dataset Reflected in Metrics
Sandbox Sandbox receiving address analytics_N_sandbox Not included in production metrics
Production Production receiving address analytics_N_live Included in production metrics

Testing in Production

Test logs sent to the production environment are included in actual metrics. To avoid affecting actual metrics, prepare as follows before testing.

  1. Get a test-only appId.

    Register a test app in Hive console > App Center to get a test-only appId. For details, see App ID Management.

  2. Exclude the test data from metrics with one of the following menus.

    Menu How to Exclude
    Metric Excluded User Management Register the users used for testing as metric excluded users
    Metric Filter Management Register the test appId or QA server as an exclusion condition
    Time Settings Set the official launch date as the metric start date to exclude pre-launch test data

1. Send Test Logs

Send test logs in the environment you want to test. Developers can apply source code and send actual events, and non-developers can send sample data with ETL simulation.

Method For Description
Source Creation Developers Apply the generated source code to the app client or server, then trigger test events to send logs.
ETL Simulation Non-developers Enter field values in the console to send sample data without writing code.

Send with Source Creation (Developers)

  1. In Data > Event, select the event to test, then go to the [Source Creation] tab.
  2. On the Client Developer or Server Developer tab, check the source code and apply it to the app client or server.
  3. Trigger test events in the environment you want to test to send logs.
Note

If you send from a server via Fluentd or HTTP, you must send to the receiving address of the environment you want to test. You can find the production and sandbox receiving addresses in Event Log Transmission.

Send with ETL Simulation (Non-developers)

  1. In the Analytics console of the environment you want to test, go to Data > Event and select the event to test.
  2. On the [ETL Simulation] tab, enter the values to test in each field of the event collection table.
  3. Click the Send button.

For details on the [Source Creation] tab and the [ETL Simulation] tab, see Event.

2. Check Reception

Check whether the test logs you sent have been collected in one of the following two ways.

Check in Data Preview

In Data > Event, select the event you tested, then on the [Data Preview] tab, set the query period to the date you sent the test logs and run the query.

  • Check that the test logs appear in the list.
  • Check that the attribute values you sent were collected as intended.

Check Directly in BigQuery

If you request BigQuery access in the Analytics console, you can query the stored data directly in BigQuery. Event logs are stored in the t_raw_event_log table.

SELECT userId, deviceId, appIdGroup, appId,
    DATETIME(TIMESTAMP_ADD(dateTime, INTERVAL 32400 SECOND)) AS dateTime_kst,  -- Convert dateTime stored in UTC to KST
    SAFE_CAST(
            JSON_VALUE(attributes, '$.eventAttributes.level') AS INT64
        ) AS level -- When level was sent as an event attribute
FROM `habq-storage.analytics_N_sandbox.t_raw_event_log`  -- analytics_N_live if you tested in production
WHERE identifierProvider = 'hive'  -- User identifier issuing system (always hive)
  AND eventName = '{tested event name}'
  AND appId = 'com.sample.test.aos'  -- appId used for testing
  AND JSON_VALUE(attributes, '$.hiveAttributes._dataSource') IN ('custom_server', 'custom_sdk')  -- Only events you sent directly (server, SDK)
  -- When querying in KST
  AND dateTime >= TIMESTAMP_SUB(TIMESTAMP('2026-09-30 00:00:00'), INTERVAL 32400 SECOND)
  AND dateTime <  TIMESTAMP_SUB(TIMESTAMP('2026-10-07 00:00:00'), INTERVAL 32400 SECOND)
  -- When removing duplicates by checksum
  QUALIFY ROW_NUMBER() OVER (PARTITION BY checksum ORDER BY bigqueryRegistTimestamp DESC) = 1
LIMIT 100
  • t_raw_event_log is a table partitioned daily by dateTime, so specify a date condition when you query it.
  • Logs that violate the transmission rules are stored in the rescue table (t_raw_event_log_rescue), not in t_raw_event_log. If you cannot see your data, check errorReason in the rescue table.

For the table structure and isolation reasons, see Event Storage Structure.

3. Check Metric Configuration

Once data reception is confirmed, create a chart, funnel, retention, ranking, or similar from the Create menu to check whether you can build the metrics you want with the collected data.

  • Check that the attributes to use as measures and dimensions appear in the selection list.
  • Check that the aggregated results match the test data you sent.

For how to use each feature, see Chart, Funnel, Retention, and Ranking.

Precautions & Tips

Events Without Sandbox Support

Refund and MMP (Airbridge, etc.) data is not processed by Hive directly. Instead, third parties such as markets (Google Play, etc.) or MMPs send it to Hive.

Third parties do not provide a sandbox environment and send data to Hive only from the production environment, so Hive cannot tell whether data collected through a third party is from production or sandbox. As a result, data processed in the sandbox may appear included in production data.

  • Test logs sent to the production environment are included in actual metrics. When you test in production, see Testing in Production to exclude the test data from metrics.
  • In the appId field, you must enter an appId registered in Hive console > App Center. If you enter an incorrect value, the data may not be collected.