RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1676559 - [RFE]: support omhttp for REST APIs
Summary: [RFE]: support omhttp for REST APIs
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rsyslog
Version: 8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Jiří Vymazal
QA Contact: Dalibor Pospíšil
Mirek Jahoda
Depends On: 1682459 1740683
Blocks: 1676560 1785679
TreeView+ depends on / blocked
Reported: 2019-02-12 14:58 UTC by Rich Megginson
Modified: 2023-02-12 22:46 UTC (History)
3 users (show)

Fixed In Version: rsyslog-8.1911.0-1.el8
Doc Type: Enhancement
Doc Text:
.`rsyslog` now provides the `omhttp` plugin for communication through an HTTP REST interface With this update of the `rsyslog` packages, you can use the new `omhttp` plugin for producing an output compatible with services using a Representational State Transfer (REST) API, such as the Ceph storage platform, Amazon Simple Storage Service (Amazon S3), and Grafana Loki. This new HTTP output module provides a configurable REST path and message format, support for several batching formats, compression, and TLS encryption. For more details, see the `/usr/share/doc/rsyslog/html/configuration/modules/omhttp.html` file installed on your system with the `rsyslog-doc` package.
Clone Of:
: 1676560 (view as bug list)
Last Closed: 2020-04-28 16:01:03 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github rsyslog rsyslog pull 3423 0 'None' closed omhttp: updates and improvements 2021-01-14 01:48:11 UTC
Red Hat Issue Tracker RHELPLAN-30300 0 None None None 2023-02-12 22:46:02 UTC
Red Hat Product Errata RHSA-2020:1702 0 None None None 2020-04-28 16:01:30 UTC

Description Rich Megginson 2019-02-12 14:58:11 UTC
Description of problem:
rsyslog needs a general purpose REST API for communication with a new generation of logging services - AWS S3, CEPH object store api, Loki, and many more.  In addition, the existing http apis (elasticsearch, mmkubernetes) could use more generalized support for http options such as headers, and better tls option support for passing in cipher suites, tls versions, and other tls parameters (especially the flag to turn off strict root CA checking so that we can use intermediate CA certs).

There is an upstream PR - https://github.com/rsyslog/rsyslog/pull/3423 - but I don't yet know if it supports all of the features we require.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 17 errata-xmlrpc 2020-04-28 16:01:03 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.