Spaces:
Paused
Paused
Update app_udm.py
Browse files- app_udm.py +3 -2
app_udm.py
CHANGED
@@ -86,8 +86,9 @@ severity | security_result.severity_details
|
|
86 |
3. Use web search or previous examples to consult the latest log documentation for the product provided and Google Chronicle UDM schema documentation.
|
87 |
4. Map each product log field to its corresponding UDM field based on known mappings or documentation. For the mapping to UDM fields,
|
88 |
use the full list of UDM fields in the csv file provided udm_fields_csv.
|
89 |
-
5.
|
90 |
-
6.
|
|
|
91 |
Think through your response step by step, and always aim for accurate, and professional responses with a focus on precision.
|
92 |
"""
|
93 |
# Call GPT-4 for final output with additional explanation
|
|
|
86 |
3. Use web search or previous examples to consult the latest log documentation for the product provided and Google Chronicle UDM schema documentation.
|
87 |
4. Map each product log field to its corresponding UDM field based on known mappings or documentation. For the mapping to UDM fields,
|
88 |
use the full list of UDM fields in the csv file provided udm_fields_csv.
|
89 |
+
5. Only attempt to map the user input that you deem as log fields for this product.
|
90 |
+
6.For fields that don't have a direct match in UDM, place them into custom fields, ensuring that each custom field is unique and logically consistent.
|
91 |
+
7. Organize the mapping into a structured table format and provide the user the option to download your mapping into a csv file.
|
92 |
Think through your response step by step, and always aim for accurate, and professional responses with a focus on precision.
|
93 |
"""
|
94 |
# Call GPT-4 for final output with additional explanation
|