Skip to content

[b/525256545] Deleting logtype folders under community directory#960

Draft
shridharn-stack wants to merge 6 commits into
mainfrom
migration-delete-folder-full
Draft

[b/525256545] Deleting logtype folders under community directory#960
shridharn-stack wants to merge 6 commits into
mainfrom
migration-delete-folder-full

Conversation

@shridharn-stack

@shridharn-stack shridharn-stack commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Description:

Deleting below logtypes

  1. SPLUNK
  2. ACCELLION
  3. ARBOR_SIGHTLINE
  4. ARCHER_IRM
  5. ASSET_STATIC_IP
  6. AVATIER
  7. AWS_ECS_METRICS
  8. AWS_VPC_TRANSIT_GATEWAY
  9. AZURE_COSMOS_DB
  10. CA_ACCESS_CONTROL
  11. CIRCLECI
  12. CISCO_CALL_MANAGER
  13. CITRIX_MONITOR
  14. CLEARSWIFT
  15. CLOUDFLARE_PAGESHIELD
  16. CYBER_2_IDS
  17. CYNET_360_AUTOXDR
  18. DEEP_INSTINCT_EDR
  19. DELINEA_DISTRIBUTED_ENGINE
  20. DIGICERT
  21. DIGITAL_SHADOWS_IOC
  22. DIGITAL_SHADOWS_SEARCHLIGHT
  23. ENTRUST_HSM
  24. F5_SHAPE
  25. FILEZILLA_FTP
  26. FORCEPOINT_CASB
  27. GREYNOISE
  28. HADOOP
  29. HILLSTONE_NGFW
  30. IBM_SAFENET
  31. IBM_SECURITY_VERIFY
  32. IBM_SECURITY_VERIFY_SAAS
  33. IBM_SIM
  34. IBM_WEBSEAL
  35. IMPERVA_ABP
  36. IMPERVA_DRA
  37. IPSWITCH_SFTP
  38. IRONSTREAM_ZOS
  39. JUNIPER_IPS
  40. KERIOCONTROL
  41. KISI
  42. KOLIDE
  43. KUBERNETES_AUTH_PROXY
  44. LENEL_ONGUARD
  45. LINKSHADOW_NDR
  46. MACOS_ENDPOINT_SECURITY
  47. MALWAREBYTES_EDR
  48. MANAGE_ENGINE_AD360
  49. MICROFOCUS_IMANAGER
  50. MICROSOFT_IAS
  51. NAGIOS
  52. NOKIA_ROUTER
  53. OKTA_ACCESS_GATEWAY
  54. ONAPSIS
  55. OORT
  56. OPENAI_AUDITLOG
  57. OPENCANARY
  58. OPENDJ
  59. OPENPATH
  60. ORACLE_FUSION
  61. ORACLE_NETSUITE
  62. ORACLE_OUD
  63. PALANTIR
  64. PAN_EDR
  65. PASSWORDSTATE
  66. PEPLINK_FW
  67. PROOFPOINT_SER
  68. PROOFPOINT_TAP_THREATS
  69. PROWATCH
  70. QUALYS_CONTINUOUS_MONITORING
  71. QUALYS_VIRTUAL_SCANNER
  72. QUEST_CHANGE_AUDITOR_EMC
  73. QUMULO_FS
  74. REDHAT_DIRECTORY_SERVER
  75. RH_ISAC_IOC
  76. RIPPLING_ACTIVITYLOGS
  77. SALESFORCE_COMMERCE_CLOUD
  78. SAP_ASE
  79. SAP_NETWEAVER
  80. SAP_SUCCESSFACTORS
  81. SERVICENOW_SECURITY
  82. SHAREPOINT
  83. SIERRA_WIRELESS
  84. SKYBOX_FIREWALL_ASSURANCE
  85. SMBD
  86. SNORT_IDS
  87. SOTI_MOBICONTROL
  88. SPYCLOUD
  89. STEALTHBITS_AUDIT
  90. STEALTHBITS_DEFEND
  91. SYMANTEC_VIP_AUTHHUB
  92. TALON
  93. TANIUM_INSIGHT
  94. TANIUM_INTEGRITY_MONITOR
  95. TANIUM_PATCH
  96. TANIUM_REVEAL
  97. TCPWAVE_DDI
  98. THALES_MFA
  99. THREATX_WAF
  100. TINES
  101. TINTRI
  102. UBIKA_WAAP
  103. UKG
  104. UPGUARD
  105. UPTYCS_EDR
  106. VSFTPD
  107. VYOS
  108. WINDCHILL
  109. XITING_XAMS
  110. YAMAHA_ROUTER
  111. YUBICO_OTP
  112. ZEROFOX_PLATFORM
  113. ZYWALL
  114. AWS_LAMBDA_FUNCTION
  115. BRO_TSV
  116. CA_ACF2
  117. CA_SSO_WEB
  118. CENSYS
  119. CENTRIFY_SSO
  120. CEQUENCE_BOT_DEFENSE
  121. CIMCOR
  122. CISCO_UMBRELLA_SWG_DLP
  123. CIS_ALBERT_ALERT
  124. CITRIX_ANALYTICS
  125. CITRIX_STOREFRONT
  126. CLOUDIAN_HYPERSTORE
  127. COMFORTE_SECURDPS
  128. DATTO_FILE_PROTECTION
  129. IVANTI_ENDPOINT_MANAGER_MOBILE
  130. MICROSOFT_ATA
  131. MICROSTRATEGY
  132. NEO4J
  133. NETAPP_BLUEXP
  134. NETSCOUT_OCI
  135. NETSKOPE_CLIENT
  136. NETWRIX_STEALTHAUDIT
  137. NET_SUITE
  138. NTOPNG
  139. SOPHOS_DHCP
  140. SYMANTEC_SA
  141. TACACS_PLUS
  142. TERADATA_DB
  143. THREATLOCKER
  144. UBERAGENT
  145. UPSTREAM_VSOC_ALERTS
  146. UPX_ANTIDDOS
  147. VECTRA_ALERTS
  148. VENAFI_ZTPKI
  149. AGILOFT
  150. ALVEO_RDM
  151. ARMIS_VULNERABILITIES
  152. ARRAYNETWORKS_VPN
  153. ASSET_PANDA
  154. AVIGILON_ACCESS_LOGS
  155. AWARE_AUDIT
  156. AWARE_SIGNALS
  157. AWS_INSPECTOR
  158. AWS_KMS
  159. AWS_REDSHIFT
  160. AWS_VPC_FLOW_CSV
  161. BARRACUDA_CLOUDGEN_FIREWALL
  162. BMC_CLIENT_MANAGEMENT
  163. BMC_HELIX_DISCOVERY
  164. BROADCOM_CA_PAM
  165. BROADCOM_SUPPORT_PORTAL
  166. CAMBIUM_NETWORKS
  167. CASSANDRA
  168. CA_LDAP
  169. CIENA_ROUTER
  170. CISCO_ACE
  171. CISCO_PIX_FIREWALL
  172. DIGITALGUARDIAN_DLP
  173. FIREEYE_NX_AUDIT
  174. FORTINET_FORTIDDOS
  175. GITGUARDIAN_ENTERPRISE
  176. GITHUB_DEPENDABOT
  177. HACKERONE
  178. HCL_BIGFIX
  179. HCNET_ACCOUNT_ADAPTER
  180. HID_DIGITALPERSONA
  181. HITACHI_CLOUD_PLATFORM
  182. IBM_DS8000
  183. IBM_QRADAR
  184. INTEL471_WATCHER_ALERTS
  185. INTEL_EMA
  186. ION_SPECTRUM
  187. KEA_DHCP
  188. KYRIBA
  189. LOGONBOX
  190. LUCID
  191. MAILMARSHAL
  192. MANAGE_ENGINE_REPORTER_PLUS
  193. MICROSOFT_SCEP
  194. NETDOCUMENTS
  195. NUCLEUS_VULNERABILITY
  196. NXLOG_MANAGER
  197. NYANSA_EVENTS
  198. ONFIDO
  199. OPA
  200. PROFTPD
  201. PROOFPOINT_SENDMAIL_SENTRION
  202. QUALYS_ASSET_CONTEXT
  203. QUEST_FILE_AUDIT
  204. RECORDIA
  205. REDCANARY_EDR
  206. SAIWALL_VPN
  207. SANGFOR_PROXY
  208. SENTRY
  209. SEQRITE_ENDPOINT
  210. SHRUBBERY_TACACS
  211. SMARTSHEET
  212. SNIPE_IT
  213. STEALTHBITS_PAM
  214. CT_GAUS_SEGUROS
  215. CYBERGATEKEEPER_NAC
  216. DIGITALGUARDIAN_EDR
  217. DIGI_MODEMS
  218. DMP_ENTRE
  219. DOMAINTOOLS_THREATINTEL
  220. DOPE_SWG
  221. ELASTIC_DEFEND
  222. ERGON_INFORMATIK_AIRLOCK_IAM
  223. ESET_IOC
  224. EVISION_FIRCOSOFT
  225. FINGERPRINT_JS
  226. FIVETRAN
  227. FORCEPOINT_MAIL_RELAY
  228. FORGEROCK_IDENTITY_CLOUD
  229. IBM_MAAS360
  230. IBM_OPENPAGES
  231. IBM_SOAR
  232. IBM_SVA
  233. VERBA_REC
  234. VIRTRU_EMAIL_ENCRYPTION
  235. VITALQIP
  236. WEBMARSHAL
  237. WINSCP
  238. WPENGINE

Checklist:

Please ensure you have completed the following items before submitting your PR.
This helps us review your contribution faster and more efficiently.

General Checks:

  • I have read and followed the project's contributing.md guide.
  • My code follows the project's coding style guidelines.
  • I have performed a self-review of my own code.
  • My changes do not introduce any new warnings.
  • My changes pass all existing tests.
  • I have added new tests where appropriate to cover my changes. (If applicable)
  • I have updated the documentation where necessary (e.g., README, API docs). (If applicable)

Open-Source Specific Checks:

  • My changes do not introduce any Personally Identifiable Information (PII) or sensitive customer data.
  • My changes do not expose any internal-only code examples, configurations, or URLs.
  • All code examples, comments, and messages are generic and suitable for a public repository.
  • I understand that any internal context or sensitive details related to this work are handled separately in internal systems (Buganizer for Google team members).

For Google Team Members and Reviewers Only:

  • I have included the Buganizer ID in the PR title or description (e.g., "Internal Buganizer ID: 123456789" or "Related Buganizer: go/buganizer/123456789").
  • I have ensured that all internal discussions and PII related to this work remain in Buganizer.
  • I have tagged the PR with one or more labels that reflect the pull request purpose.

Screenshots (If Applicable)

If your changes involve UI or visual elements, please include screenshots or GIFs here.
Ensure any sensitive data is redacted or generalized.


Further Comments / Questions

SKIP_GOOGLE_PARSER_CHECK="Not Applicable for now"

Any additional comments, questions, or areas where you'd like specific feedback.

@shridharn-stack shridharn-stack requested a review from a team as a code owner June 18, 2026 07:13
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a comprehensive cleanup of the repository by removing numerous obsolete or deprecated log parser configurations and their corresponding metadata files. This effort helps reduce technical debt and maintain a cleaner codebase by pruning unused community-contributed parsers.

Highlights

  • Parser Cleanup: Removed a large set of legacy log parser configurations and their associated metadata files from the community directory.
New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request removes logstash parser configurations and metadata JSON files for multiple integrations, including Accellion, Agiloft, ALVEO_RDM, ARBOR_SIGHTLINE, Archer, ARMIS, ARRAYNETWORKS_VPN, ASSET_PANDA, Aqua Security, AVATIER, AVIGILON_ACCESS_LOGS, AWARE_AUDIT, AWARE_SIGNALS, AWS_ECS_METRICS, AWS_INSPECTOR, AWS_KMS, AWS_LAMBDA_FUNCTION, AWS_REDSHIFT, AWS_VPC_FLOW_CSV, and AWS_VPC_TRANSIT_GATEWAY. I have no feedback to provide as there are no review comments.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@shridharn-stack shridharn-stack changed the title Deleted all logtype folders [b/525256545] Deleting logtype folders under community directory Jun 18, 2026
@shridharn-stack shridharn-stack added Parser Parser Validations parser-migration To be used for all piper logtype migrations to github labels Jun 18, 2026
@shridharn-stack shridharn-stack marked this pull request as draft June 19, 2026 08:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Parser Validations Parser parser-migration To be used for all piper logtype migrations to github

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant