![\"\"](\"https:\/\/dtasiagroup.com\/wp-content\/uploads\/2025\/12\/DSCF9705g.jpg-1350x400x2.jpg\")
<\/p>\n<\/p>\n
Recently, several people have asked about the syslog-ng project\u2019s position on AI. In short, the answer is one of cautious optimism. We are open to using AI, but we do not allow it to take over any critical responsibilities from human developers. What does this approach look like in practice?<\/p>\n
First and foremost, all syslog-ng code continues to be written by humans. While we do not reject AI tools outright, we deliberately avoid using them to directly generate production code. There are two main reasons for this.<\/p>\n
The first is licensing. Syslog-ng\u2019s source code is distributed under a combination of GPLv2 and LGPLv2.1 licenses. At present, there is no reliable way to guarantee that code produced by AI tools would be compliant with these licensing requirements.<\/p>\n
The second reason is code quality. Syslog-ng is built using high-performance C code and is often deployed in highly secure environments. Even if AI-generated code were to run correctly, there would be no guarantee that it would meet our efficiency and security standards. Retrofitting performance optimizations and security measures after the fact is significantly more difficult than building them in from the very beginning.<\/p>\n
Portability is another major concern. While x86_64 Linux is one of the supported platforms, it is far from the only one. Syslog-ng also runs on ARM, RISC-V, POWER, s390, and other architectures, including big-endian systems. In addition, it is not limited to Linux \u2014 it also supports operating systems such as macOS and FreeBSD. Writing code that behaves correctly and efficiently across all these environments is a complex task and one that current AI tools are not equipped to manage reliably.<\/p>\n
So where does AI fit into the syslog-ng ecosystem?<\/p>\n
Although it is not used to write core code, AI is part of our broader quality and support processes. We maintain a large suite of automated test cases, and each pull request is reviewed by humans before being merged. In parallel, various automated tools continuously analyze our code, both on GitHub and internally. These tools provide suggestions on how to improve code quality and security.<\/p>\n
Of course, such tools are known to generate a significant number of false positives. Still, they remain useful, as they sometimes identify legitimate issues that require attention. Importantly, every final decision \u2014 whether to accept or reject a recommendation \u2014 is made by a human, since AI-based tools often lack full contextual understanding of the codebase.<\/p>\n
Another critical pillar of the syslog-ng project is its documentation. Many of our most active users have chosen syslog-ng specifically because of the high quality of its documentation, which is written by humans. That said, we are exploring the use of AI as a way to improve how users access that information. We have already run a proof of concept on a local machine, where users could ask questions through an AI-powered interface and find relevant information much faster than by manually browsing the documentation.<\/p>\n
While this is not directly tied to syslog-ng development itself, I recently realized that sequence-rtg \u2014 the tool I use to generate syslog-ng PatternDB rules from large volumes of log messages \u2014 would also be classified as an AI tool under many modern definitions. Interestingly, its documentation never mentions AI at all, likely because it was created before \u201cAI\u201d became a mainstream buzzword. If you\u2019d like to learn more about sequence and how it helps streamline PatternDB creation for syslog-ng, you can read more here: In summary: yes, we do use AI. Probably less than what AI enthusiasts would hope for, but certainly more than what AI skeptics would be comfortable with. We have chosen a balanced, pragmatic position \u2014 one where AI enhances our work but does not replace the critical thinking, responsibility, and expertise of human developers.<\/p>\n \n Gi\u1edbi thi\u1ec7u v\u1ec1 DT Asia<\/strong><\/p>\n DT Asia \u0111\u01b0\u1ee3c th\u00e0nh l\u1eadp v\u00e0o n\u0103m 2007 v\u1edbi s\u1ee9 m\u1ec7nh r\u00f5 r\u00e0ng l\u00e0 x\u00e2y d\u1ef1ng b\u01b0\u1edbc th\u00e2m nh\u1eadp th\u1ecb tr\u01b0\u1eddng cho c\u00e1c gi\u1ea3i ph\u00e1p b\u1ea3o m\u1eadt CNTT ti\u00ean phong kh\u00e1c nhau t\u1eeb M\u1ef9, Ch\u00e2u \u00c2u v\u00e0 Israel.<\/p>\n Ng\u00e0y nay, DT Asia l\u00e0 nh\u00e0 ph\u00e2n ph\u1ed1i gi\u00e1 tr\u1ecb gia t\u0103ng khu v\u1ef1c v\u1ec1 c\u00e1c gi\u1ea3i ph\u00e1p an ninh m\u1ea1ng, cung c\u1ea5p c\u00e1c c\u00f4ng ngh\u1ec7 ti\u00ean ti\u1ebfn cho c\u00e1c c\u01a1 quan ch\u00ednh ph\u1ee7 tr\u1ecdng \u0111i\u1ec3m v\u00e0 c\u00e1c kh\u00e1ch h\u00e0ng h\u00e0ng \u0111\u1ea7u thu\u1ed9c khu v\u1ef1c t\u01b0 nh\u00e2n, bao g\u1ed3m c\u00e1c ng\u00e2n h\u00e0ng to\u00e0n c\u1ea7u v\u00e0 c\u00e1c c\u00f4ng ty thu\u1ed9c danh s\u00e1ch Fortune 500. Ch\u00fang t\u00f4i c\u00f3 c\u00e1c v\u0103n ph\u00f2ng v\u00e0 \u0111\u1ed1i t\u00e1c kh\u1eafp khu v\u1ef1c Ch\u00e2u \u00c1 - Th\u00e1i B\u00ecnh D\u01b0\u01a1ng nh\u1eb1m th\u1ea5u hi\u1ec3u r\u00f5 h\u01a1n c\u00e1c th\u1ecb tr\u01b0\u1eddng v\u00e0 cung c\u1ea5p c\u00e1c gi\u1ea3i ph\u00e1p mang t\u00ednh b\u1ea3n \u0111\u1ecba h\u00f3a.<\/p>\n \u00a0<\/strong><\/p>\n Ch\u00fang t\u00f4i h\u1ed7 tr\u1ee3 nh\u01b0 th\u1ebf n\u00e0o<\/strong><\/p>\n If you need to know more about dynamic data movement, you\u2019re in the right place, we\u2019re here to help! DTA is One Identity\u2019s distributor, especially in Singapore and Asia, our technicians have deep experience on the product and relevant technologies you can always trust, we provide this product\u2019s turnkey solutions, including consultation, deployment, and maintenance service.<\/p>\n
https:\/\/www.syslog-ng.com\/community\/b\/blog\/posts\/sequence-making-patterndb-creation-for-syslog-ng-easier<\/a><\/p>\n