Open
Conversation
outchannel: eleminate type cast for compatibility reasons
Commit ffaf6dc added proper variable sync, but dropped the check if active count had actually changed. As such, the output was always generated, which could pollute the log heavily. also fixes some codestyle issues introduced by earlier commits. With the help of AI-Agent: Codex 2025-06
…et-change-messages-in-omfwd.c Fix misleading active target log in omfwd
Easier to maintain than the off-project C source. The checks are pretty trivial. This also fixes some nits that the old checker did not detect. closes rsyslog#5631
CI: new python-based codestyle checker
…g-warnings Revert "queue: emit better warning messages on queue param mismatch"
fix hashtable realloc memset range
While somewhat irrelevant for daily stable, we base the version on scheduled stable and must bump in order to be the "highest version number".
\nAI-Agent: Codex 2025-06
…rted-by-threadsanitizer Fix race in notifyReArm
Whilst this did not cause issues when building the project, it produced warnings.
Removed the redundant *_la_LDFLAGS
…g#5685) Avoid including openssl/engine.h when OPENSSL_NO_ENGINE is set. Adjust dependent modules and test accordingly.
- this is driven by Solaris: it does not provide UT_LINESIZE - prefer utmpx when available and map setutent()/getutent() - derive UT_LINESIZE from platform macros to compile on Solaris - if nothing else helps, set UT_LINESIZE to 32 Note that 32 is a somewhat save default, but not perfect. Fixes rsyslog#5678
…e-compatibility fix Solaris build of omusrmsg
…m-sphinx-generation Remove footer from singlehtml build
testbench: bootstrap build setup for direct test runs
This commit significantly improves the rsyslog documentation and its
associated tooling.
Key enhancements:
* **RainerScript Lexer**: Updated lexer to support hyphens in
identifiers, fixing highlighting issues.
* **Sphinx Extension**: Refactored lexer integration as a proper
Sphinx extension.
* **Deprecated Syntax Guidance**: Transformed docs for legacy action
statements to focus on conversion to modern `action()` syntax,
reducing duplication.
* **Legacy Stop Action**: Clarified that `~` for 'stop' is bad
practice.
* **MMAITAG Module Fixes**: Corrected formatting, highlighting, and
syntax in `mmaitag` documentation.
* **Minor Fixes**: Various small formatting and cross-reference
corrections.
These changes streamline documentation, provide clearer migration
paths for users, and enhance the overall accuracy and maintainability.
doc: PoC transformations of legacy stament doc
Add furo theme for sphinx
- Added "Getting Started" guide with modern examples and pipeline
integrations (e.g., Elasticsearch, Kafka).
- Rewrote community resources page:
* Added AI-based rsyslog assistant and GitHub Discussions as primary
support channels.
* Moved older resources to a new "Legacy Resources" section.
* Added note about Adiscon professional services.
- Reorganized configuration reference index with clearer structure,
modern examples, and compatibility note updates.
- Introduced a new "Documentation Style Guide" for consistent .rst
formatting and contributor guidance.
- Deleted outdated or unused content (old proposals, examples, and
legacy free_support page).
- Moved version compatibility notes to the historical section.
- Reworked main index page with a concise introduction, better
navigation, and updated community/sponsor references.
- Switched HTML theme to Furo and updated Sphinx requirements.
- Simplified and modernized footer with Apache License 2.0 reference.
doc: major restructure and content improvements
- Consolidate change detection into a single “Check for doc changes” step - Remove separate determine_changes_type and doc_only_success_check jobs - Ensure the CI job always returns an exit status (satisfies branch protection) - Update checkout action version and file‐pattern list for code changes - Bump copyright year to 2025
ci: simplify compile check workflow and guarantee exit status
doc: fix legacy conf where modern should be
Introduce a new `getting_started/` section with modern RainerScript-based examples and clear explanations for new users. The guide includes: - index page with quick overview and TOC - installation instructions for major distros - minimal example with modern omfile action - explanation of distro-provided default configs - forwarding logs with TCP/UDP and queue best practices - next steps pointing to tutorials and GitHub Discussions This provides a coherent entry point for sysadmins and DevOps engineers and avoids legacy syntax to reduce confusion for first-time users.
docs: add structured beginner guide under getting_started/
…e-in-doc Add LICENSE file for docs
…r-sphinx-json-targets Add JSON build targets
- Added sphinxcontrib.mermaid to requirements and enabled the extension. - Rewrote configuration/basic_structure.rst with a structured overview of message flow, including mermaid diagrams for pipeline visualization. - Modernized examples.rst: converted all examples to RainerScript, added inline comments, and removed outdated legacy syntax. - Updated configuration/index.rst to place basic_structure as the first topic.
doc: introduce mermaid diagrams and modernized configuration docs
This patch improves the GitHub Actions PR validation workflow: - Added comprehensive inline documentation for clarity. - Corrected branch reference from 'master' to 'main' in `tests/CI/PR_validation.sh`. These changes enhance CI/CD clarity and maintainability. With support from AI Agents: Gemini
CI: Enhance PR validation and update branch name
Version 8.2406.2-vlt ### Added - [OUTPUT MODULES] New omsentinel module
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.