Skip to content

Commit 391571b

Browse files
cijothomasutpilla
andauthored
chore: Fix some typos in readme for userevent metrics (#393)
Co-authored-by: Utkarsh Umesan Pillai <66651184+utpilla@users.noreply.github.com>
1 parent 780ad02 commit 391571b

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

opentelemetry-user-events-metrics/README.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -17,16 +17,18 @@ to create events and trace data that can be viewed via existing tools like
1717
ftrace and perf.
1818

1919
This kernel feature is supported started in Linux kernel 5.18 onwards. The feature enables
20-
- A faster path for tracing from user mode application utilizing kernel mode memory address space.
21-
- User processes can now export telemetry events only when it is useful i.e, when the registered set of tracepoint events are enabled.
20+
21+
- A faster path for tracing from user mode application utilizing kernel mode memory address space.
22+
- User processes can now export telemetry events only when it is useful i.e, when the registered set of tracepoint events are enabled.
2223

2324
This user_events exporter enables applications to use OpenTelemetry API to capture the telemetry events, and write to user_events subsystem. From user_events, the events can be
24-
- Captured by the agents running locally, and listening for specific events within user_events subsystem.
25-
- Or real-time monitoring using local Linux tool like [perf](https://perf.wiki.kernel.org/index.php/Main_Page) or ftrace.
2625

27-
[![Crates.io: opentelemetry-user-events-logs](https://img.shields.io/crates/v/opentelemetry-user-events-logs.svg)](https://crates.io/crates/opentelemetry-user-events-logs)
28-
[![Documentation](https://docs.rs/opentelemetry-user-events-logs/badge.svg)](https://docs.rs/opentelemetry-user-events-logs)
29-
[![LICENSE](https://img.shields.io/crates/l/opentelemetry-user-events-logs)](./LICENSE)
26+
- Captured by the agents running locally, and listening for specific events within user_events subsystem.
27+
- Or real-time monitoring using local Linux tool like [perf](https://perf.wiki.kernel.org/index.php/Main_Page) or ftrace.
28+
29+
[![Crates.io: opentelemetry-user-events-metrics](https://img.shields.io/crates/v/opentelemetry-user-events-metrics.svg)](https://crates.io/crates/opentelemetry-user-events-metrics)
30+
[![Documentation](https://docs.rs/opentelemetry-user-events-metrics/badge.svg)](https://docs.rs/opentelemetry-user-events-metrics)
31+
[![LICENSE](https://img.shields.io/crates/l/opentelemetry-user-events-metrics)](./LICENSE)
3032
[![GitHub Actions CI](https://github.com/open-telemetry/opentelemetry-rust-contrib/workflows/CI/badge.svg)](https://github.com/open-telemetry/opentelemetry-rust-contrib/actions?query=workflow%3ACI+branch%3Amain)
3133
[![Slack](https://img.shields.io/badge/slack-@cncf/otel/rust-brightgreen.svg?logo=slack)](https://cloud-native.slack.com/archives/C03GDP0H023)
3234

0 commit comments

Comments
 (0)