Readme - update telemetry docs

Author: SiskaPavel

README.md

@@ -128,9 +128,41 @@ To install ipfixprobe with NEMEA dependency from binary RPM packages, it is poss
 
 ## Telemetry
 
-`ipfixprobe` can expose telemetry data using the appFs library, which leverages the fuse3 library (filesystem in userspace) to allow telemetry data to be accessed and manipulated 
+`ipfixprobe` exports statistics and other diagnostic information through a telemetry interface based on appFs library, which leverages the fuse3 library (filesystem in userspace) to allow telemetry data to be accessed and manipulated 
 through standard filesystem operations.
 
+```
+/var/run/ipfixprobe/
+├── output
+│   └── ipxRing
+│       └── stats
+└── pipeline
+    └── queues
+        ├── 0
+        │   ├── cache-stats
+        │   ├── fragmentation-cache-stats
+        │   ├── input-stats
+        │   └── parser-stats
+        ├── 1
+        ...
+```
+
+From telemetry stats you can read:
+
+**Output Directory:**
+
+In the output directory, you can monitor the capacity and current usage of the ipxRing. This helps determine whether the output plugin can export flows quickly enough or if there are bottlenecks caused by insufficient ring capacity.
+
+
+**Pipeline Directory:**
+
+The pipeline directory provides statistics for all worker queues. Each queue is identified by its ID (e.g., 0, 1) and includes the following files:
+- cache-stats: Provides detailed metrics about flow cache usage and exported flow statistics.
+- fragmentation-cache-stats: Provides metrics related to packet fragmentation.
+- input-stats: Provides metrics on the data received by by the queue.
+- parser-stats: Provides detailed information about the types of packets processed by the parser,
+
+
 ## Input / Output of the flow exporter
 
 The availability of the input and output interfaces depends on the ipfixprobe build settings. By default, we provide RPM package with pcap and raw inputs. The default provided outpus are ipfix and text.