From d569889ea8fcf6d0c8d4595666a5acd85564b713 Mon Sep 17 00:00:00 2001
From: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Date: Wed, 23 Nov 2022 09:14:45 -0700
Subject: [PATCH] [processor/filter] add ottl funcs to README (#16439)

Update README.md
---
 processor/filterprocessor/README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/processor/filterprocessor/README.md b/processor/filterprocessor/README.md
index a209b3cde7a5..6bfd8262e2d0 100644
--- a/processor/filterprocessor/README.md
+++ b/processor/filterprocessor/README.md
@@ -305,6 +305,8 @@ See the table below for details on each context and the fields it exposes.
 The OTTL allows the use of `and`, `or`, and `()` in conditions.
 See [OTTL Boolean Expressions](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/ottl/README.md#boolean-expressions) for more details.
 
+The filter processor has access to all the [factory functions of the OTTL](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/pkg/ottl/ottlfuncs#ottl-functions) 
+
 For conditions that apply to the same signal, such as spans and span events, if the "higher" level telemetry matches a condition and is dropped, the "lower" level condition will not be checked.
 This means that if a span is dropped but a span event condition was defined, the span event condition will not be checked.
 The same relationship applies to metrics and datapoints.