You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: initialize metrics exporter http gem
* remove version_rb_path for metrics exporter in release
* lint
* chore: Update metrics exporter README
This removes content related to installing the gem before the metrics
API and SDK gems were released.
* chore: Update MetricsExporter class in example
Now, there's an extra Metrics:: namespace
* chore: Update class for MetricsExporter
* revision
* add force_flush
---------
Co-authored-by: Kayla Reopelle <kreopelle@newrelic.com>
Copy file name to clipboardExpand all lines: exporter/otlp-metrics/README.md
+6-40
Original file line number
Diff line number
Diff line change
@@ -18,55 +18,21 @@ Generally, *libraries* that produce telemetry data should avoid depending direct
18
18
19
19
This gem supports the [v0.20.0 release][otel-proto-release] of OTLP.
20
20
21
-
## Prerequisite
22
-
23
-
The exporter-oltp-metrics depends on two gems that have not been officially released: opentelemetry-metrics-sdk and opentelemetry-metrics-api.
24
-
25
-
Within the .gemspec file, these gems are not listed as dependencies. However, for users who need utilize this metrics exporter, they must first install and load these two gems before they can use the exporter.
26
-
27
-
To facilitate this, there are couple recommended approaches:
28
-
29
-
#### 1. Download the source code
30
-
31
-
1. Download the [opentelemetry-ruby](https://github.com/open-telemetry/opentelemetry-ruby).
32
-
2. Navigate to subfolder, then build the [metrics_sdk](https://github.com/open-telemetry/opentelemetry-ruby/tree/main/metrics_sdk) and [metrics_api](https://github.com/open-telemetry/opentelemetry-ruby/tree/main/metrics_api).
33
-
3. Execute `gem build *.gemspec`.
34
-
4. Lastly, install the built gem into the system.
35
-
36
-
#### 2. Using `path:` option in Gemfile with downloaded source code
37
-
38
-
git clone [opentelemetry-ruby](https://github.com/open-telemetry/opentelemetry-ruby) first, then use Gemfile
Or, if you use [bundler][bundler-home], include `opentelemetry-sdk` in your `Gemfile`.
33
+
Or, if you use [bundler][bundler-home], include `opentelemetry-sdk`, `opentelemetry-metrics-sdk`, and `opentelemetry-exporter-otlp-metrics` in your `Gemfile`.
68
34
69
-
Then, configure the SDK to use the OTLP metrics exporter
35
+
Then, configure the SDK to use the OTLP metrics exporter
70
36
71
37
```ruby
72
38
require'opentelemetry/sdk'
@@ -77,7 +43,7 @@ OpenTelemetry::SDK.configure
77
43
78
44
# To start a trace you need to get a Tracer from the TracerProvider
@@ -112,7 +78,7 @@ The collector exporter can be configured explicitly in code, or via environment
112
78
113
79
## How can I get involved?
114
80
115
-
The `opentelemetry-exporter-otlp-metrics` gem source is [on github][repo-github], along with related gems including `opentelemetry-sdk`.
81
+
The `opentelemetry-exporter-otlp-metrics` gem source is [on github][repo-github], along with related gems including `opentelemetry-metrics-sdk`.
116
82
117
83
The OpenTelemetry Ruby gems are maintained by the OpenTelemetry-Ruby special interest group (SIG). You can get involved by joining us in [GitHub Discussions][discussions-url] or attending our weekly meeting. See the [meeting calendar][community-meetings] for dates and times. For more information on this and other language SIGs, see the OpenTelemetry [community page][ruby-sig].
0 commit comments