Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Berbagai komponen di GDC menghasilkan log auditnya menggunakan format syslog standar sesuai dengan spesifikasi RFC-5424. Untuk mengetahui informasi selengkapnya, lihat https://datatracker.ietf.org/doc/html/rfc5424.
ID proses aplikasi yang memulai pesan. Contoh, "1"
pri
string
Nilai prioritas. Contoh, "46"
hostname
string
Komponen yang awalnya mengirim pesan syslog. Contoh, "anthos-audit-logs-forwarder-2kbnd"
ident
string
Perangkat atau aplikasi yang memulai pesan. Contoh, "/logging-prober-sidecar"
msgid
string
Jenis pesan. Contoh, "audit-log"
extradata
string
Informasi kustom tambahan. Contoh, "[exampleSDID@20224 iut=\"3\" eventSource=\"Application\" eventID=\"11211\"]"
message
string
Pesan bentuk bebas yang memberikan informasi tentang acara. Misalnya,
"{\"time\":\"2024-01-24T17:24:55.076954537Z\",\"auditID\":\"7ab3bf57-67cb-4373-bbf6-b3ad0835cc65\",\"user\":{\"identity\":\"audit-log-writer\"},\"resource\":\"41075\",\"action\":\"-\",\"description\":\"This is a prober testing the functionality of the syslog endpoint\",\"userAgent\":\"audit-log-prober\",\"response\":\"-\",\"_gdch_org\":\"-\",\"_gdch_service\":\"audit-log-prober\"}"
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eGDC components generate audit logs in a standard syslog format, adhering to the RFC-5424 specification.\u003c/p\u003e\n"],["\u003cp\u003eThe audit logs are represented in JSON format, containing fields like \u003ccode\u003epid\u003c/code\u003e, \u003ccode\u003epri\u003c/code\u003e, \u003ccode\u003ehostname\u003c/code\u003e, \u003ccode\u003eident\u003c/code\u003e, \u003ccode\u003emsgid\u003c/code\u003e, \u003ccode\u003eextradata\u003c/code\u003e, and \u003ccode\u003emessage\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003emessage\u003c/code\u003e field contains a free-form text message that includes detailed information about the event, such as time, audit ID, user, and resource.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ehostname\u003c/code\u003e field indicates the component that originally sent the message, whereas \u003ccode\u003eident\u003c/code\u003e specifies the device or application source.\u003c/p\u003e\n"],["\u003cp\u003eThe field \u003ccode\u003emsgid\u003c/code\u003e specify the type of the message that is being logged, for example "audit-log".\u003c/p\u003e\n"]]],[],null,["# System logging protocol (syslog) audit logs\n\nVarious components in GDC produce their audit logs using a standard syslog format according to the RFC-5424 specification. For more information, see \u003chttps://datatracker.ietf.org/doc/html/rfc5424\u003e.\n\n**JSON representation** \n\n {\n \"pid\": string,\n \"pri\": string,\n \"hostname\": string,\n \"ident\": string,\n \"msgid\": string,\n \"extradata\": string,\n \"message\": string\n }"]]
