이 문서에서는 Cloud Logging에서 사용하는 데이터 모델을 설명합니다.
이 데이터 모델은 로그 데이터가 저장되는 형식을 지정합니다. 또한 로그 데이터를 쿼리할 수 있는 측정기준도 결정합니다.
데이터 모델
Cloud Logging에서 로그는 이름이 지정된 개별 항목의 모음입니다.
로그 이름으로 데이터를 쿼리할 수 있습니다. 로그는 LogEntry 구조를 따르는 항목으로 구성됩니다.
각 로그 항목은 상태를 기록하거나 가상 머신 인스턴스 만들기와 같은 특정 이벤트를 기술하며 최소한 다음 요소를 포함합니다.
이벤트가 발생한 시점 또는 Cloud Logging에서 수신된 시점을 나타내는 타임스탬프
로그 항목 소스에 관한 정보. 이 소스를 모니터링 리소스라고 합니다. 모니터링 리소스의 예시로는 개별 Compute Engine 인스턴스 및 Google Kubernetes Engine 컨테이너가 있습니다.
모니터링 리소스 유형의 전체 목록은 모니터링 리소스 및 서비스를 참조하세요.
다음 중 하나여야 하는 페이로드:
textPayload: 이러한 페이로드는 단일 문자열 형식입니다.
jsonPayload: 이러한 페이로드는 정형화되어 있으므로 키-값 쌍으로 쿼리할 수 있습니다.
애플리케이션이 항상 정형 로그 데이터를 작성하는 것이 좋습니다.
protoPayload: 이러한 페이로드는 proto 파일 형식을 따르며 필드는 JSON 형식입니다.
로그가 속한 로그의 이름. 로그 이름에는 로그 항목이 속한 리소스의 전체 경로와 식별자가 포함됩니다. 다음은 로그 이름의 예시입니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-05(UTC)"],[],[],null,["# Log entry data model\n\nThis document describes the data model used by Cloud Logging.\nThe data model specifies the format in which your log data is stored. It\nalso determines the dimensions over which you can query your log data.\n\nData model\n----------\n\nIn Cloud Logging, a *log* is a named collection of individual entries.\nYou can query your data by the name of the log. Logs are composed\nof entries that conform to the [`LogEntry`](/logging/docs/reference/v2/rest/v2/LogEntry) structure.\n\nEach log entry records status or describes a specific event, such as\nthe creation of a virtual machine instance, and minimally consists of the\nfollowing:\n\n- A timestamp that indicates either when the event took place or when it was received by Cloud Logging.\n- Information about the source of the log entry. This source is called the *monitored resource* . Examples of monitored resources include individual Compute Engine instances and Google Kubernetes Engine containers. For a complete listing of monitored resource types, see [Monitored resources and services](/logging/docs/api/v2/resource-list).\n- A payload which must be one of the following:\n\n - `textPayload`: These payloads are formatted as a single string.\n - `jsonPayload`: These payloads are [structured](/logging/docs/structured-logging), so you can query by key-value pairs. We recommend that applications always write structured log data.\n - `protoPayload`: These payloads follow the format of a proto file and the fields are formatted as JSON.\n- The name of the log to which it belongs. The name of a log includes the full\n path of the resource to which the log entries belong, followed by an\n identifier. The following are examples of log names:\n\n - `projects/my-project/logs/stdout`\n - `projects/my-project/compute.googleapis.com/activity`\n\nYou can write queries that retrieve only those log entries where the value of\na `LogEntry` field matches some criteria. For example, you can display only\nthose log entries whose `severity` field has the value of `ERROR`.\n\nLog entry types\n---------------\n\n[Audit logs](/logging/docs/audit) and [Access Transparency](/assured-workloads/access-transparency/docs/overview) provide\ninformation necessary to satisfy compliance regulations.\nAudit logs provide information about administrative activities\nand accesses within your Google Cloud resources.\nAccess Transparency logs record actions taken by Google Cloud\nstaff when accessing your Google Cloud content. For a list of supported\nservices, see [Google Cloud services with audit logs](/logging/docs/audit/services)\nand [Google Cloud services with Access Transparency logs](/assured-workloads/access-transparency/docs/supported-services).\n\nThe following type of log entries are stored in the\n[`_Required` log bucket](/logging/docs/store-log-entries#required-bucket) in the Google Cloud project,\nbilling account, folder, or organization in which they originate:\n\n- [Admin Activity audit logs](/logging/docs/audit#admin-activity)\n- [System Event audit logs](/logging/docs/audit#system-event)\n- Google Workspace Admin Audit logs\n- Enterprise Groups Audit logs\n- Login Audit logs\n\n\u003c!-- --\u003e\n\n- Access Transparency logs\n\nAll other log entries that originate in a Google Cloud project, billing account,\nfolder, or organization are stored in the\n[`_Default` log bucket](/logging/docs/store-log-entries#default-bucket). However, you can change which\nlog entries are stored in this log bucket.\n\nWhat's next\n-----------\n\n- [Store log data](/logging/docs/store-log-entries).\n- [Route log data](/logging/docs/routing/overview).\n- [Query and view logs overview](/logging/docs/log-analytics)."]]