[
https://issues.apache.org/jira/browse/IGNITE-21529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr updated IGNITE-21529:
-------------------------------
Fix Version/s: 3.0
> Implement Log Sink for EventLog
> -------------------------------
>
> Key: IGNITE-21529
> URL: https://issues.apache.org/jira/browse/IGNITE-21529
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr
> Assignee: Aleksandr
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> This is a user-configurable entity that is configured via cluster
> configuration. A Sink defines where events from Channel(s) should be sent to.
> Examples: logger sink, kafka sink, webhook sink, table sink. Sink has one
> method that can be called by channel: write(Event). Write does not guarantee
> that the Event is really written and won’t be lost. But a user can configure
> a sink that does flush on every write (log4j with synchronous appender and
> immediateFlush = true).
> The eventlog.sinks.<name>.type = “log” defines the Log Sink where <name> is
> the name of the unique cluster-wide name. NamedList should be used to define
> sinks and their names. Here are properties that are Log Sink specific:
> category (what appender should be used, default: system)
> level (what logging level should be used, default: INFO).
> As a result of this ticket there should be a cluster configuration for the
> File Sink and a base set of EventTypes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
