})
+
+## Rules and limitations
+
+When writing regular expression rules, you must follow these rules:
+
+* Your rule must be [RE2 compliant](https://github.com/google/re2/wiki/Syntax).
+* If your rule matches *only a section* of the log line, the full log line will be matched.
+* For *single line messages*, it is not mandatory to prefix and suffix the regex expression with `.\*`.
+* Exclude rules take priority over include rules. Include rules are processed first. However, if an exclude rule matches data that matched the include rule filter, the data is excluded.
+* If two or more rules are listed, the assumed Boolean operator is `OR`.
diff --git a/docs/send-data/opentelemetry-collector/remote-management/processing-rules/index.md b/docs/send-data/opentelemetry-collector/remote-management/processing-rules/index.md
new file mode 100644
index 0000000000..22daede564
--- /dev/null
+++ b/docs/send-data/opentelemetry-collector/remote-management/processing-rules/index.md
@@ -0,0 +1,56 @@
+---
+slug: /send-data/opentelemetry-collector/remote-management/processing-rules
+title: Processing Rules for OpenTelemetry (Beta)
+description: Use Sumo Logic processing rules for an OpenTelemetry agent with an OpenTelemetry remote management (OTRM) source template.
+---
+
+
+
+
+
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+Processing rules can be used with OpenTelemetry Collector for different source templates in OTRM (OpenTelemetry remote management). These processing rules can filter and can mask the data sent to Sumo Logic from OpenTelemetry Collector which is remotely managed by Sumo Logic. The rules affect only the data sent to Sumo Logic; logs and metrics on your end remain intact and unchanged. Data filtered by OpenTelemetry Collector using processing rules does not count towards your daily data volume quota.
+
+Processing rules for logs collection support the following rule types:
+
+* [Exclude messages that match](include-and-exclude-rules.md). Remove messages that you do not want to send to Sumo Logic at all ("denylist" filter). These messages are skipped by OpenTelemetry Collector and are not uploaded to Sumo Logic.
+* [Include messages that match](include-and-exclude-rules.md). Send only the data you'd like in your Sumo Logic account (an "allowlist" filter). This type of rule can be useful, for example, if you only want to include messages coming from a firewall.
+
+Processing Rules for metrics collection support the following rule types:
+
+* [Exclude metrics that match](metrics-include-and-exclude-rules.md). Remove metrics that you do not want to send to Sumo Logic at all ("denylist" filter).
+* [Include metrics that match](metrics-include-and-exclude-rules.md). Send only selected metrics to your Sumo Logic account (an "allowlist" filter).
+
+## Limitations
+
+* Regular expressions must be [RE2 compliant](https://github.com/google/re2/wiki/Syntax).
+* Processing Rules are tested with maximum of 20 rules.
+
+## How do processing rules work together?
+
+You can create one or more processing rules for a Source Template, combining the different types of filters to generate the exact data set you want sent to Sumo Logic.
+
+When a Source has multiple rules they are processed in the following order: includes, excludes, masks.
+
+Exclude rules take priority over include rules. Include rules are processed first, however, if an exclude rule matches data that matched the include rule filter, the data is excluded.
+
+## Guide contents
+
+In this section, we'll introduce the following concepts:
+
+}){kind=icon}
Use include and exclude processing rules to specify what kind of data is sent to Sumo Logic using OpenTelemetry Collector.
+Use metrics processing rules to specify what metrics are sent to Sumo Logic using OpenTelemetry Collector.
+})
+
+### Filter by dimension
+
+If you need to filter by dimension of the metrics, then you can select this option and provide the list of keys and values in the dimension table. Key needs to be the exact dimension name and value can be a regex which matches against the value for the key given. All of these key value pairs will have the `AND` condition between them.
+
+For example, when collecting host metrics you can filter CPU metrics data for a specific CPU (say `cpu0`), and you can mention the respective key value pair in the dimension table.
+
+})
+
+### Filter by metrics name and dimension
+
+If you need to filter by metrics name and dimension, then you can select this option and provide the metric name regex and dimension key and value. Key needs to be the exact dimension name and value can be a regex which matches against the value for the key given. All inputs here (that is, metric name) and all key value pairs will have the `AND` condition between them.
+
+For example, when collecting host metrics, you can filter network metrics for a specific device and direction by giving metric name regex as `network`, and in the dimension table key value pair you can specify `device=lo` and `direction=transmit`.
+
+})
+
+## Rules and Limitations
+
+* Your rule must be [RE2 compliant](https://github.com/google/re2/wiki/Syntax).
+* Exclude rules take priority over include rules. Include rules are processed first, however, if an exclude rule matches data that matched the include rule filter, the data is excluded.
+* If two or more rules are listed, the assumed Boolean operator is OR.
+* If data needs to get filtered for single dimension key which can have multiple possible values then we can use a `|` operator. For example if we need to monitor cpu metrics for only cpu0 and cpu1 then we can form the dimension value expression as `cpu0|cpu1`.
diff --git a/static/img/send-data/opentelemetry-collector/processingrule-include-logs.png b/static/img/send-data/opentelemetry-collector/processingrule-include-logs.png
new file mode 100644
index 0000000000..837041108c
Binary files /dev/null and b/static/img/send-data/opentelemetry-collector/processingrule-include-logs.png differ
diff --git a/static/img/send-data/opentelemetry-collector/processingrule-include-metricdimension.png b/static/img/send-data/opentelemetry-collector/processingrule-include-metricdimension.png
new file mode 100644
index 0000000000..122f63829e
Binary files /dev/null and b/static/img/send-data/opentelemetry-collector/processingrule-include-metricdimension.png differ
diff --git a/static/img/send-data/opentelemetry-collector/processingrule-include-metricname.png b/static/img/send-data/opentelemetry-collector/processingrule-include-metricname.png
new file mode 100644
index 0000000000..819a2af171
Binary files /dev/null and b/static/img/send-data/opentelemetry-collector/processingrule-include-metricname.png differ
diff --git a/static/img/send-data/opentelemetry-collector/processingrule-include-metricnameanddimension.png b/static/img/send-data/opentelemetry-collector/processingrule-include-metricnameanddimension.png
new file mode 100644
index 0000000000..2d5f6b648b
Binary files /dev/null and b/static/img/send-data/opentelemetry-collector/processingrule-include-metricnameanddimension.png differ