Este documento descreve as opções que ajudam a processar dados de registo que não são processados pelos analisadores existentes do Google Security Operations. Nesses casos, o Google SecOps suporta a criação de tipos de registos para permitir a análise e o carregamento.
Pode escolher entre os seguintes tipos:
Tipos de registos pré-criados: pode pedir ao Google SecOps para criar e gerir tipos de registos pré-criados. Estes funcionam em conjunto com analisadores pré-criados e
pré-configurados. 2 a 3 semanas após o seu pedido, estes tipos de registos pré-criados são disponibilizados a todos os clientes do Google SecOps.
Tipos de registos personalizados: criados e geridos pela sua organização. Tem de configurar os analisadores personalizados correspondentes internamente, onde os tipos de registos personalizados e os analisadores ficam disponíveis internamente (apenas para a sua organização) 10 minutos após a criação.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-20 UTC."],[],[],null,["# Request prebuilt and create custom log types\n============================================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nThis document describes options to help you process log data that isn't\nprocessed by existing Google Security Operations parsers. In such cases,\nGoogle SecOps supports the creation of log types to enable\nparsing and ingestion.\n\nYou can choose between the following types:\n\n- *Prebuilt log types*: You can request Google SecOps to create\n and manage prebuilt log types. These work in conjunction with prebuilt and\n preconfigured parsers. 2--3 weeks after your request, these prebuilt log\n types are made available to all Google SecOps customers.\n\n- *Custom log types*: Created and managed by your organization. You need to\n configure corresponding custom parsers in-house, where the custom log types\n and parsers become internally (only to your organization) available 10\n minutes after creation.\n\nFor information about corresponding **prebuilt parsers** and\n**custom parsers** , see\n[Manage prebuilt and custom parsers](/chronicle/docs/event-processing/manage-parser-updates).\n\nCreate a custom log type\n------------------------\n\nTo create a custom log type, do the following:\n\n1. Go to **SIEM settings \\\u003e Available Log Types** . You can view\n available log types using the **Search** feature.\n\n2. Click **Request a Log Type**.\n\n3. Under the **Create a custom log type on your own**, enter details for your log type.\n\n For example, to create a custom log type for *Azure Key Vault logging*,\n complete the following:\n - In the **Vendor/Product** field, enter\n `Azure Key Vault logging`.\n\n - In the **Log Type** field, enter `AZURE_KEYVAULT_LOGGING`.\n\n4. Click **Create Log Type**.\n\n5. Wait 10 minutes to ensure that the new log type is available in all\n components before creating feeds with it.\n\nThe custom log type limitations are:\n\n- Total: 400\n\n- Daily: 25\n\n- Hourly: 8\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
