[#97086] [Ruby master Bug#16612] Enumerator::ArithmeticSequence#last with float range produces incorrect value — muraken@...
Issue #16612 has been updated by mrkn (Kenta Murata).
4 messages
2020/02/07
[#97307] [Ruby master Feature#16663] Add block or filtered forms of Kernel#caller to allow early bail-out — headius@...
Issue #16663 has been reported by headius (Charles Nutter).
29 messages
2020/02/28
[ruby-core:97182] [Ruby master Feature#16638] Structured Data for Syslog
From:
rlafranchi@...
Date:
2020-02-17 19:06:28 UTC
List:
ruby-core #97182
Issue #16638 has been reported by rlafranchi (Richard LaFranchi).
----------------------------------------
Feature #16638: Structured Data for Syslog
https://bugs.ruby-lang.org/issues/16638
* Author: rlafranchi (Richard LaFranchi)
* Status: Open
* Priority: Normal
----------------------------------------
`Syslog::Logger` appears to conform to RFC5424, however doesn't support structured data unless I'm missing something. This feature would implement the ability to add some meta data along with the message.
A format of a RFC5424 message is the following:
```
<PRIVAL> VERSION TIMESTAMP HOSTNAME APP-NAME PROCID MSGID STRUCTUREDDATA MSG
```
where STRUCTUREDDATA is zero or multiple elements in the format of `[ID1 KEY1="VALUE1" KEY2="VALUE2" ...][ID2 ....]`
Per [https://tools.ietf.org/html/rfc5424#section-7.3](https://tools.ietf.org/html/rfc5424#section-7.3) meta appears to be the appropriate id to use for arbitrary meta-information about a message, ex.
```
[meta foo="bar" cat="dog"]
```
Possible implementation:
```
logger = Syslog::Logger.new
logger.info "msg", meta: {foo: "bar", cat: "dog"}
```
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>