Bug 1676559
| Summary: | [RFE]: support omhttp for REST APIs | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Rich Megginson <rmeggins> | |
| Component: | rsyslog | Assignee: | Jiří Vymazal <jvymazal> | |
| Status: | CLOSED ERRATA | QA Contact: | Dalibor Pospíšil <dapospis> | |
| Severity: | unspecified | Docs Contact: | Mirek Jahoda <mjahoda> | |
| Priority: | medium | |||
| Version: | 8.0 | CC: | dapospis, jvymazal, rmeggins | |
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged | |
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1676560 (view as bug list) | Environment: | ||
| Last Closed: | 2020-04-28 16:01:03 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1682459, 1740683 | |||
| Bug Blocks: | 1676560, 1785679 | |||
|
Description
Rich Megginson
2019-02-12 14:58:11 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. https://access.redhat.com/errata/RHSA-2020:1702 |