[chore] Spelling it isn't... ...pratyush (#6019)
This commit is contained in:
Josh Soref
GitHub
parent
f458704463
commit
14daaf1b1d
|
|
@ -35,6 +35,6 @@ jobs:
|
|||
- name: Add comment to PR if author is not a member
|
||||
if: env.MEMBER_FOUND == 'false'
|
||||
run: |
|
||||
gh pr comment ${PR_NUM} --body "Thank you for your contribution! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out out this survey: ${SURVEY_URL}"
|
||||
gh pr comment ${PR_NUM} --body "Thank you for your contribution! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey: ${SURVEY_URL}"
|
||||
env:
|
||||
GH_TOKEN: ${{ secrets.OPENTELEMETRYBOT_GITHUB_TOKEN }}
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ markdown formatter (see below).
|
|||
|
||||
## Images
|
||||
|
||||
If you use images, make sure that your blog post is located in it's own
|
||||
If you use images, make sure that your blog post is located in its own
|
||||
directory. Put the images into the same directory.
|
||||
|
||||
If you have an image stored at `content/en/{{ .File.Dir }}imagename.png`, you
|
||||
|
|
|
|||
|
|
@ -4,9 +4,9 @@ linkTitle: Instrument Nginx
|
|||
date: 2022-08-22
|
||||
author: >-
|
||||
[Debajit Das](https://github.com/debajitdas), [Kumar
|
||||
Pratyus](https://github.com/kpratyus), [Severin
|
||||
Pratyush](https://github.com/kpratyus), [Severin
|
||||
Neumann](https://github.com/svrnm) (Cisco)
|
||||
cSpell:ignore: Debajit Kumar Pratyus webserver
|
||||
cSpell:ignore: Debajit Kumar Pratyush webserver
|
||||
---
|
||||
|
||||
Apache HTTP Server and NGINX are the most popular web servers. It's most likely
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: OpenTelemetry Erlang/Elixir, Javascript, and Ruby v1.0 (Medium)
|
||||
title: OpenTelemetry Erlang/Elixir, JavaScript, and Ruby v1.0 (Medium)
|
||||
linkTitle: Erlang/Elixir, JS, and Ruby 1.0
|
||||
date: 2022-02-01
|
||||
canonical_url: https://medium.com/opentelemetry/opentelemetry-erlang-elixir-javascript-and-ruby-v1-0-3a0c32e0add4
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ author: >-
|
|||
issue: 4542
|
||||
sig: SIG Go
|
||||
# prettier-ignore
|
||||
cSpell:ignore: aws Benedetti Fabrizio Ferri gopkg labstack macaron moduled otelaws otelecho otellambda otelmacaron otelmongo otelmux
|
||||
cSpell:ignore: aws Benedetti Fabrizio Ferri gopkg labstack macaron otelaws otelecho otellambda otelmacaron otelmongo otelmux
|
||||
---
|
||||
|
||||
The Go SIG will remove the code of contrib modules that lack code owners
|
||||
|
|
@ -30,7 +30,7 @@ Currently unowned modules include the following:
|
|||
- [`go.opentelemetry.io/contrib/samplers/aws/xray`](https://pkg.go.dev/go.opentelemetry.io/contrib/samplers/aws/xray)
|
||||
|
||||
For a full list of modules at risk for removal, see the
|
||||
[Remove unowned moduled](https://github.com/orgs/open-telemetry/projects/92/views/1)
|
||||
[Remove unowned modules](https://github.com/orgs/open-telemetry/projects/92/views/1)
|
||||
project board.
|
||||
|
||||
## Why are those modules going to be removed?
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ https://github.com/open-telemetry/opentelemetry-collector-releases/releases/down
|
|||
chmod +x ocb
|
||||
```
|
||||
|
||||
{{% /tab %}} {{% tab "MacOS (AMD 64)" %}}
|
||||
{{% /tab %}} {{% tab "macOS (AMD 64)" %}}
|
||||
|
||||
```sh
|
||||
curl --proto '=https' --tlsv1.2 -fL -o ocb \
|
||||
|
|
@ -65,7 +65,7 @@ https://github.com/open-telemetry/opentelemetry-collector-releases/releases/down
|
|||
chmod +x ocb
|
||||
```
|
||||
|
||||
{{% /tab %}} {{% tab "MacOS (ARM 64)" %}}
|
||||
{{% /tab %}} {{% tab "macOS (ARM 64)" %}}
|
||||
|
||||
```sh
|
||||
curl --proto '=https' --tlsv1.2 -fL -o ocb \
|
||||
|
|
|
|||
|
|
@ -670,21 +670,21 @@ started.
|
|||
|
||||
The available scrapers are:
|
||||
|
||||
| Scraper | Supported OSs | Description |
|
||||
| ---------- | ------------------- | ------------------------------------------------------ |
|
||||
| cpu | All except Mac[^1] | CPU utilization metrics |
|
||||
| disk | All except Mac[^1] | Disk I/O metrics |
|
||||
| load | All | CPU load metrics |
|
||||
| filesystem | All | File System utilization metrics |
|
||||
| memory | All | Memory utilization metrics |
|
||||
| network | All | Network interface I/O metrics & TCP connection metrics |
|
||||
| paging | All | Paging/Swap space utilization and I/O metrics |
|
||||
| processes | Linux, Mac | Process count metrics |
|
||||
| process | Linux, Windows, Mac | Per process CPU, Memory, and Disk I/O metrics |
|
||||
| Scraper | Supported OSs | Description |
|
||||
| ---------- | --------------------- | ------------------------------------------------------ |
|
||||
| cpu | All except macOS[^1] | CPU utilization metrics |
|
||||
| disk | All except macOS[^1] | Disk I/O metrics |
|
||||
| load | All | CPU load metrics |
|
||||
| filesystem | All | File System utilization metrics |
|
||||
| memory | All | Memory utilization metrics |
|
||||
| network | All | Network interface I/O metrics & TCP connection metrics |
|
||||
| paging | All | Paging/Swap space utilization and I/O metrics |
|
||||
| processes | Linux, macOS | Process count metrics |
|
||||
| process | Linux, macOS, Windows | Per process CPU, Memory, and Disk I/O metrics |
|
||||
|
||||
[^1]:
|
||||
Not supported on Mac when compiled without cgo, which is the default for the
|
||||
images released by the Collector SIG.
|
||||
Not supported on macOS when compiled without cgo, which is the default for
|
||||
the images released by the Collector SIG.
|
||||
|
||||
For specific details about which metrics are collected and specific
|
||||
configuration details, see
|
||||
|
|
|
|||
|
|
@ -108,9 +108,9 @@ corresponding to the service is injected during setup. This lets you get access
|
|||
to an instance in your endpoint mapping (or controllers if you're using an older
|
||||
version of .NET).
|
||||
|
||||
It's not required to inject a service-level tracer, nor does it improve
|
||||
performance either. You will need to decide where you'll want your tracer
|
||||
instance to live, though.
|
||||
It isn't required to inject a service-level tracer and it doesn't improve
|
||||
performance. You will need to decide where you'll want your tracer instance to
|
||||
live, though.
|
||||
|
||||
This is also where you can configure instrumentation libraries.
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@
|
|||
contact: ''
|
||||
- name: Dyte
|
||||
url: https://dyte.io
|
||||
components: [Go, Javascript]
|
||||
components: [Go, JavaScript]
|
||||
reference: 'https://dyte.io/blog/opentelemetry-at-dyte-part-i/'
|
||||
referenceTitle: blog post
|
||||
contact: https://github.com/ethicalmohit
|
||||
|
|
@ -110,7 +110,7 @@
|
|||
contact: https://github.com/igorestevanjasinski
|
||||
- name: Skyscanner
|
||||
url: https://www.skyscanner.net/
|
||||
components: [Collector, Go, Java, Javascript, Python]
|
||||
components: [Collector, Go, Java, JavaScript, Python]
|
||||
reference: https://www.infoq.com/presentations/opentelemetry-observability/
|
||||
referenceTitle: presentation
|
||||
contact: https://github.com/danielgblanco/
|
||||
|
|
|
|||
Loading…
Reference in New Issue