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
This repository also contains libraries to aid with interoperablity with vendor specific tracing solutions:
65
+
This repository also contains libraries to aid with interoperability with vendor specific tracing solutions:
66
66
67
67
-[Context Propagation](propagator/): OTTrace and Amazon X-Ray
68
68
-[Resource Detectors](resources/):
@@ -74,18 +74,18 @@ This repository also contains libraries to aid with interoperablity with vendor
74
74
75
75
OpenTelemetry Ruby follows the [versioning and stability document][otel-versioning] in the OpenTelemetry specification. Notably, we adhere to the outlined version numbering exception, which states that experimental signals may have a `0.x` version number.
76
76
77
-
### Library Compatability
77
+
### Library Compatibility
78
78
79
-
This project is managed on a volunteer basis and therefore we have limited capacity to support compatability with unmaintained or EOL libraries.
79
+
This project is managed on a volunteer basis and therefore we have limited capacity to support compatibility with unmaintained or EOL libraries.
80
80
81
-
We will regularly review the instrumentations to drop compatability for any versions of Ruby or gems that reach EOL or no longer receive regular maintenance.
81
+
We will regularly review the instrumentations to drop compatibility for any versions of Ruby or gems that reach EOL or no longer receive regular maintenance.
82
82
83
83
Should you need instrumentation for _older_ versions of a library then you must pin to a specific version of the instrumentation that supports it,
84
84
however, you will no longer receive any updates for the instrumentation from this repository.
85
85
86
86
> When a release series is no longer supported, it's your own responsibility to deal with bugs and security issues. We may provide backports of the fixes and publish them to git, however there will be no new versions released. If you are not comfortable maintaining your own versions, you should upgrade to a supported version. <https://guides.rubyonrails.org/maintenance_policy.html#security-issues>
87
87
88
-
Consult instrumentation gem's README file and gemspec for details about library compatability.
88
+
Consult instrumentation gem's README file and gemspec for details about library compatibility.
Copy file name to clipboardexpand all lines: instrumentation/CONTRIBUTING.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -173,7 +173,7 @@ For example, the `Werewolf` module generated in the example above is available v
173
173
174
174
Whenever possible, use first-party extension points (hooks) to instrument libraries. This ensures that the instrumentation is compatible with the latest versions of the library and that the instrumentation is maintained by the library authors. [`ActiveSupport::Notifications`](https://guides.rubyonrails.org/active_support_instrumentation.html) and `Middleware` are good examples of first-party extension points used by our instrumentation libraries.
175
175
176
-
Monkey patching is discouraged in OpenTelemetry Ruby because it is the most common source of bugs and incompatability with the libraries we instrument. If you must monkey patch, please ensure that the monkey patch is as isolated as possible and that it is clearly documented.
176
+
Monkey patching is discouraged in OpenTelemetry Ruby because it is the most common source of bugs and incompatibility with the libraries we instrument. If you must monkey patch, please ensure that the monkey patch is as isolated as possible and that it is clearly documented.
177
177
178
178
### Use Semantic Conventions
179
179
@@ -337,7 +337,7 @@ Add the service container to `jobs/instrumentation_with_services/services` and a
337
337
338
338
> :information_source: Please refer to the official [GitHub Actions Documentation](https://docs.github.com/en/actions/using-containerized-services/about-service-containers) for more information on how to add a service container.
339
339
340
-
If we determine the service container slows down the test suite significantly, it may make sense to copy the marix and steps stanzas from an existing instrumentation and update it to use the new service container as a dependency:
340
+
If we determine the service container slows down the test suite significantly, it may make sense to copy the matrix and steps stanzas from an existing instrumentation and update it to use the new service container as a dependency:
341
341
342
342
```yaml
343
343
@@ -407,7 +407,7 @@ In addition to that, there should also be redundant `yardoc` comments in the ent
407
407
408
408
### Examples
409
409
410
-
Executuable examples should be included in the `examples` directory that demonstrate how to use the instrumentation in a real-world scenario.
410
+
Executable examples should be included in the `examples` directory that demonstrate how to use the instrumentation in a real-world scenario.
411
411
412
412
We recommend using [Bundler's inline gemfile](https://bundler.io/guides/bundler_in_a_single_file_ruby_script.html) to run the examples. Here is an example from the `grape` instrumentation:
Copy file name to clipboardexpand all lines: instrumentation/README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -40,14 +40,14 @@ Instrumentation-specific documentation can be found in each subdirectory's `READ
40
40
41
41
You also have the option of installing all of the instrumentation libraries by installing `opentelemetry-instrumentation-all`. See that gem's [README](https://github.com/open-telemetry/opentelemetry-ruby-contrib/tree/main/instrumentation/all) for more.
42
42
43
-
### Maintenance and Version Compatability
43
+
### Maintenance and Version Compatibility
44
44
45
45
We are a community of volunteers who do our best to provide our users with up to date support for instrumentations,
46
-
however we have limited capacity and are unable to support compatability with EOL or unmaintained libraries.
46
+
however we have limited capacity and are unable to support compatibility with EOL or unmaintained libraries.
47
47
48
48
Should you need to instrument an _older_ version of a library you will have to ensure to pin to an instrumentation version that is compatible with that library.
49
49
50
-
Please review the individual instrumentation READMEs for more information about version compatability.
50
+
Please review the individual instrumentation READMEs for more information about version compatibility.
0 commit comments