-
Updated
Aug 4, 2021 - Go
OpenTelemetry
OpenTelemetry provides a single set of APIs, libraries, agents, and collector services to capture distributed traces and metrics from your application. You can analyze them using Prometheus, Jaeger, and other observability tools.
Here are 190 public repositories matching this topic...
-
Updated
Aug 4, 2021 - Java
-
Updated
Aug 3, 2021 - TypeScript
I think I've had about a 10% success rate with markdownlint since it seems to get throttled by GitHub. I've heard this was an issue that should have improved, but it doesn't seem to have been and I can't find any context for that in this repo.
Perhaps switching markdownlint to a GitHub Action would work around the throttling "for free" (actions automatically have GitHub creds for the repo). Jus
Similar to open-telemetry/opentelemetry-dotnet#2138, we can cut .NET Core 2.1 from support matrix, as .NET Core 2.1 is end of life next month (https://devblogs.microsoft.com/dotnet/net-core-2-1-will-reach-end-of-support-on-august-21-2021/).
Since most of the projects list NETSTANDARD2.0 as the supported one, and not .NETCore2.1, the changes may be minimal, and mostly r
#3615 improves reload behavior by failing with an error rather than hanging, if the config is invalid. This issue tracks creating an automated test to verify this going forward.
(Guessing there's an actual way to make this a test, maintainers will know better ;) )
_Originally posted by @carlosalberto in open-telemetry/opentelemetry-collector#3615 (comment)
-
Updated
Jul 31, 2021 - Java
-
Updated
Aug 4, 2021 - Go
It currently is:
private static boolean isKeyValid(String name) { return name != null && !name.isEmpty() && StringUtils.isPrintableString(name); }
It needs to be:
private static boolean isKeyValid(String name) { return name != null && !name.trim().isEmpty() && StringUtils.isPrintableString(name); }
Or it needs to use something like apache StringUtils isBlank.
Environment:
Python 3.7.9, Ubuntu 20.04
opentelemetry-api 1.4.0
opentelemetry-sdk 1.4.0
flask 1.1.3
requests 2.26.0
Setup: A flask upstream server (to set_baggage) and downstream server (to get_baggage).
Attached requirements.txt if any additional dependency information is needed
**Steps to
See the spec change for details open-telemetry/opentelemetry-specification#1775
We have no automatic check for CODEOWNERS on CI.
A CI check can be added so that
- every component has a CODEOWNERS line and
- every
componentfolder listed on CODEOWNERS actually exists (to prevent typos).
-
Updated
Apr 22, 2021 - Shell
open-telemetry/opentelemetry-specification#1839
We need to change the default OTLP HTTP port from 4317 to 4318
Our Rack instrumentation allows configuration of a URL quantization function https://github.com/open-telemetry/opentelemetry-ruby/blob/1c37b00dc82d490dace1f92739977aa4674d7039/instrumentation/rack/lib/opentelemetry/instrumentation/rack/middlewares/tracer_middleware.rb#L122-L137
We should add the same functionality to the Sinatra instrumentation. @genebean reported this requirement in Gitter:
Use Case
- Provide a sample application to test DBs, messaging systems and HTTP, GRPC backend resolution and call view.
Proposal
- A simple app where backend can be swapped or we can use multiple backends.
Context: open-telemetry/opentelemetry-collector#3743
We need to:
- make sure we create a new -legacy port, for 55681
- change the default port from 55681 to 4318
- schedule a ticket to remove the legacy port in two releases
This PR can be used as a reference, which did the same when the gRPC port changed from 55680 to 4317: https://github.com/open-telemetry/op
Actually, opentelemetry-java allows user to customize the metadata in the header, which is convenient to implement our own authentication in collector, any plan for cpp? Thank you.
Is your feature request related to a problem?
No.
Describe the solution you'd like
Provide the ability to customize the gRPC header.
Describe alternatives you've considered
No.
**Additional co
-
Updated
Aug 2, 2021 - Go
-
Updated
Jul 9, 2021
per #268
-
Updated
Aug 3, 2021 - Makefile
-
Updated
Aug 1, 2021 - Scala
-
Updated
Apr 18, 2021 - Go
typeorm tests are creating a new db connection in each test. If something goes wrong (assertion fails, exception thrown), the test does not close this connection which causes the following tests to fail as well.
We need to move the logic into afterEach hook so tests clean the environment after they are done for whatever reason.
-
Updated
Aug 4, 2021 - TypeScript
- Organization
- open-telemetry
- Website
- opentelemetry.io
Bug description
There seem to be more space between 'Application Metrics' and 'External Calls' compared to the space between 'External Calls' and 'Database Calls' on Macbook Air 13 inch model.
Expected behavior
The tabs should be evenly spac