[jira] [Updated] (NIFI-7988) Prometheus Remote Write Processor
[ https://issues.apache.org/jira/browse/NIFI-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javi Roman updated NIFI-7988: - Labels: (was: pull-request-available) > Prometheus Remote Write Processor > -- > > Key: NIFI-7988 > URL: https://issues.apache.org/jira/browse/NIFI-7988 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > A new processor that allows NiFi to store Prometheus metrics as a Remote > Write Adapter. > Prometheus's local storage is limited by single nodes in its scalability and > durability. Instead of trying to solve clustered storage in Prometheus > itself, Prometheus has a set of interfaces that allow integrating with remote > storage systems. > The Remote Write feature in Prometheus allows sending samples to a third > party storage system. There is a list of specialized remote endpoints here > [1]. > With this NiFi Prometheus Remote Write Processor you can store the metrics in > whatever storage supported in NiFi, even to store in several storages at the > same time with the advantages of NiFi routing capabilities. > This processor has two user defined working modes: > # One FlowFile per Prometheus sample. > # One FlowFile every N samples defined by the user. This mode allows storing > the samples in bunches in an easy way without needing other NiFi processors > for aggregations. > The user decides the operation mode. > The content of the FlowFiles is JSON format. > [1] > [https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7988) Prometheus Remote Write Processor
[ https://issues.apache.org/jira/browse/NIFI-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javi Roman updated NIFI-7988: - Status: Open (was: Patch Available) Working in a new patch. > Prometheus Remote Write Processor > -- > > Key: NIFI-7988 > URL: https://issues.apache.org/jira/browse/NIFI-7988 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Minor > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > A new processor that allows NiFi to store Prometheus metrics as a Remote > Write Adapter. > Prometheus's local storage is limited by single nodes in its scalability and > durability. Instead of trying to solve clustered storage in Prometheus > itself, Prometheus has a set of interfaces that allow integrating with remote > storage systems. > The Remote Write feature in Prometheus allows sending samples to a third > party storage system. There is a list of specialized remote endpoints here > [1]. > With this NiFi Prometheus Remote Write Processor you can store the metrics in > whatever storage supported in NiFi, even to store in several storages at the > same time with the advantages of NiFi routing capabilities. > This processor has two user defined working modes: > # One FlowFile per Prometheus sample. > # One FlowFile every N samples defined by the user. This mode allows storing > the samples in bunches in an easy way without needing other NiFi processors > for aggregations. > The user decides the operation mode. > The content of the FlowFiles is JSON format. > [1] > [https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7988) Prometheus Remote Write Processor
[ https://issues.apache.org/jira/browse/NIFI-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javi Roman updated NIFI-7988: - Status: Patch Available (was: In Progress) > Prometheus Remote Write Processor > -- > > Key: NIFI-7988 > URL: https://issues.apache.org/jira/browse/NIFI-7988 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Minor > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > A new processor that allows NiFi to store Prometheus metrics as a Remote > Write Adapter. > Prometheus's local storage is limited by single nodes in its scalability and > durability. Instead of trying to solve clustered storage in Prometheus > itself, Prometheus has a set of interfaces that allow integrating with remote > storage systems. > The Remote Write feature in Prometheus allows sending samples to a third > party storage system. There is a list of specialized remote endpoints here > [1]. > With this NiFi Prometheus Remote Write Processor you can store the metrics in > whatever storage supported in NiFi, even to store in several storages at the > same time with the advantages of NiFi routing capabilities. > This processor has two user defined working modes: > # One FlowFile per Prometheus sample. > # One FlowFile every N samples defined by the user. This mode allows storing > the samples in bunches in an easy way without needing other NiFi processors > for aggregations. > The user decides the operation mode. > The content of the FlowFiles is JSON format. > [1] > [https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7988) Prometheus Remote Write Processor
[ https://issues.apache.org/jira/browse/NIFI-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javi Roman updated NIFI-7988: - Status: In Progress (was: Patch Available) > Prometheus Remote Write Processor > -- > > Key: NIFI-7988 > URL: https://issues.apache.org/jira/browse/NIFI-7988 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Minor > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > A new processor that allows NiFi to store Prometheus metrics as a Remote > Write Adapter. > Prometheus's local storage is limited by single nodes in its scalability and > durability. Instead of trying to solve clustered storage in Prometheus > itself, Prometheus has a set of interfaces that allow integrating with remote > storage systems. > The Remote Write feature in Prometheus allows sending samples to a third > party storage system. There is a list of specialized remote endpoints here > [1]. > With this NiFi Prometheus Remote Write Processor you can store the metrics in > whatever storage supported in NiFi, even to store in several storages at the > same time with the advantages of NiFi routing capabilities. > This processor has two user defined working modes: > # One FlowFile per Prometheus sample. > # One FlowFile every N samples defined by the user. This mode allows storing > the samples in bunches in an easy way without needing other NiFi processors > for aggregations. > The user decides the operation mode. > The content of the FlowFiles is JSON format. > [1] > [https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7988) Prometheus Remote Write Processor
[ https://issues.apache.org/jira/browse/NIFI-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javi Roman updated NIFI-7988: - Description: A new processor that allows NiFi to store Prometheus metrics as a Remote Write Adapter. Prometheus's local storage is limited by single nodes in its scalability and durability. Instead of trying to solve clustered storage in Prometheus itself, Prometheus has a set of interfaces that allow integrating with remote storage systems. The Remote Write feature in Prometheus allows sending samples to a third party storage system. There is a list of specialized remote endpoints here [1]. With this NiFi Prometheus Remote Write Processor you can store the metrics in whatever storage supported in NiFi, even to store in several storages at the same time with the advantages of NiFi routing capabilities. This processor has two user defined working modes: # One FlowFile per Prometheus sample. # One FlowFile every N samples defined by the user. This mode allows storing the samples in bunches in an easy way without needing other NiFi processors for aggregations. The user decides the operation mode. The content of the FlowFiles is JSON format. [1] [https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage] was: A new processor that allows NiFi to store Prometheus metrics as a Remote Write Adapter. Prometheus's local storage is limited by single nodes in its scalability and durability. Instead of trying to solve clustered storage in Prometheus itself, Prometheus has a set of interfaces that allow integrating with remote storage systems. The Remote Write feature in Prometheus allows sending samples to a third party storage system. There is a list of specialized remote endpoints here [1]. With this NiFi Prometheus Remote Write Processor you can store the metrics in whatever storage supported in NiFi, even store in several storages with the advantages of NiFi routing capabilities. This processor has two user defined working modes: # One FlowFile per Prometheus sample. # One FlowFile every N samples defined by the user. This mode allows storing the samples in bunches in an easy way without needing other NiFi processors for aggregations. The user decides the operation mode. The content of the FlowFiles is JSON format. [1] [https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage] > Prometheus Remote Write Processor > -- > > Key: NIFI-7988 > URL: https://issues.apache.org/jira/browse/NIFI-7988 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Minor > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > A new processor that allows NiFi to store Prometheus metrics as a Remote > Write Adapter. > Prometheus's local storage is limited by single nodes in its scalability and > durability. Instead of trying to solve clustered storage in Prometheus > itself, Prometheus has a set of interfaces that allow integrating with remote > storage systems. > The Remote Write feature in Prometheus allows sending samples to a third > party storage system. There is a list of specialized remote endpoints here > [1]. > With this NiFi Prometheus Remote Write Processor you can store the metrics in > whatever storage supported in NiFi, even to store in several storages at the > same time with the advantages of NiFi routing capabilities. > This processor has two user defined working modes: > # One FlowFile per Prometheus sample. > # One FlowFile every N samples defined by the user. This mode allows storing > the samples in bunches in an easy way without needing other NiFi processors > for aggregations. > The user decides the operation mode. > The content of the FlowFiles is JSON format. > [1] > [https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7988) Prometheus Remote Write Processor
[ https://issues.apache.org/jira/browse/NIFI-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-7988: --- Status: Patch Available (was: Open) > Prometheus Remote Write Processor > -- > > Key: NIFI-7988 > URL: https://issues.apache.org/jira/browse/NIFI-7988 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Minor > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > A new processor that allows NiFi to store Prometheus metrics as a Remote > Write Adapter. > Prometheus's local storage is limited by single nodes in its scalability and > durability. Instead of trying to solve clustered storage in Prometheus > itself, Prometheus has a set of interfaces that allow integrating with remote > storage systems. > The Remote Write feature in Prometheus allows sending samples to a third > party storage system. There is a list of specialized remote endpoints here > [1]. > With this NiFi Prometheus Remote Write Processor you can store the metrics in > whatever storage supported in NiFi, even store in several storages with the > advantages of NiFi routing capabilities. > This processor has two user defined working modes: > # One FlowFile per Prometheus sample. > # One FlowFile every N samples defined by the user. This mode allows storing > the samples in bunches in an easy way without needing other NiFi processors > for aggregations. > The user decides the operation mode. > The content of the FlowFiles is JSON format. > [1] > [https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7988) Prometheus Remote Write Processor
[ https://issues.apache.org/jira/browse/NIFI-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javi Roman updated NIFI-7988: - External issue URL: https://github.com/apache/nifi/pull/4651 Labels: pull-request-available (was: ) > Prometheus Remote Write Processor > -- > > Key: NIFI-7988 > URL: https://issues.apache.org/jira/browse/NIFI-7988 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Minor > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > A new processor that allows NiFi to store Prometheus metrics as a Remote > Write Adapter. > Prometheus's local storage is limited by single nodes in its scalability and > durability. Instead of trying to solve clustered storage in Prometheus > itself, Prometheus has a set of interfaces that allow integrating with remote > storage systems. > The Remote Write feature in Prometheus allows sending samples to a third > party storage system. There is a list of specialized remote endpoints here > [1]. > With this NiFi Prometheus Remote Write Processor you can store the metrics in > whatever storage supported in NiFi, even store in several storages with the > advantages of NiFi routing capabilities. > This processor has two user defined working modes: > # One FlowFile per Prometheus sample. > # One FlowFile every N samples defined by the user. This mode allows storing > the samples in bunches in an easy way without needing other NiFi processors > for aggregations. > The user decides the operation mode. > The content of the FlowFiles is JSON format. > [1] > [https://prometheus.io/docs/operating/integrations/#remote-endpoints-and-storage] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
