[
https://issues.apache.org/jira/browse/NIFI-7855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203981#comment-17203981
]
Alan Jackoway commented on NIFI-7855:
-------------------------------------
What kind of limit are you thinking of? In one of my NiFis, at least 60% of
metrics come from the connection metrics like OutputCount. Would you want to
shut off all of the connection metrics? For my use cases, I was considering a
block/allow list setup for the connections since they seem to be the main
contributor to metric count.
[SiteToSiteProvenanceReportingtask|https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-site-to-site-reporting-nar/1.5.0/org.apache.nifi.reporting.SiteToSiteProvenanceReportingTask/]
has an existing pattern for filtering on component type or id that someone
could potentially follow.
> Limit or Tune metrics in DataDog Reporting Task
> -----------------------------------------------
>
> Key: NIFI-7855
> URL: https://issues.apache.org/jira/browse/NIFI-7855
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Crystal Harris
> Priority: Major
>
> I am using the DataDog reporting task with NiFi and we are sendings tens of
> thousands of custom metrics to DataDog. Is there a way or can there be a way
> to limit metrics, either by volume or metric type? i.e., Can we send
> nifi.Files and nifi.Active but not some of the others?
> If not, I think using the DataDog reporting task is a non-starter due to
> cost. We're at $4k/month in custom metrics right now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
