Is your feature request related to a problem? No.

It would be nice to have a single binary with the frontend build embedded in query-service go binary.

Describe the solution you'd like

We can use go.rice to embed the frontend build with query-service.

https://github.com/GeertJohan/go.rice

Additional context

It would help not only for getting started with SigNoz

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

In the collector we used to use Viper, but we found lots of bugs, and decided to build our own config.Map based on Koanf (not exposed publicly). I think in the builder we should use Koanf or the config.Map defined in the collector.

Bug Report

The current OTLP exporter below flattens nested array in Span.Atttributes (Activity.Tags in .NET) into a list of key value pairs with the same key for all these kv pairs. For example, activity.SetTag('arraykey', new int [] {1, 2, 3} is converted to JSON like list {{'arraykey': 1}, {'arraykey': 2}, {'arraykey': 3}} in OTLP. This could cause problem if the OTLP listener would lik

In the doc page https://opentelemetry.io/docs/java/manual_instrumentation/, it would be nice if a layer could be added, using the latests dependencies, bom and inner project dependencies(api, sdk, and opentelemetry-exporters-otlp) to use the provided code.

It would be nice if the sample could provide the gradle/maven, etc. dependencies as a block to copy/paste int the https://opentelemetry.io/

Description

The new APM guide doesn't contain the transaction metrics that are generated in the APM Server which power the APM UI. We still have them in the legacy documentation https://github.com/elastic/apm-server/blob/master/docs/legacy/metricset-indices.asciidoc#transaction-metrics.

Ideally we should port most if not all of the document's content over to the data model document: https

The recently added flags in timescale/promscale#578 are yet to be updated in prom-migrator's readme which can be found here.

Is your feature request related to a problem? Please describe.

Sometimes, due to routingprocessor's limitations (like routing only on one key) a routing key has to be created specifically for this issue.
Because of that users might want to drop this from being sent through the exporter to prevent having "polluted" data in the system that consumes data.
Since routingprocessor has to be pla

It would be handy if the basic-otlp example showed how to set the service name for a tracer, since this is a fairly crucial setting when tracing.

The example produces span with unknown_service, and I couldn't see an obvious way to set it.

A lot of other examples use the Jaeger exporter, which uses:

The SdkBundle documentation could use same be improvements in regards of the configuration.

• Show how to enable/disable the SDK or parts of it in different environements (dev, staging, prod, etc.)
• Show how to configure Resource Limits and Attributes.
• Show how to configure different Span Samplers, especially the ParentBased Sampler and how to reference custom Samplers.
• S

Hello,

I am trying to deploy opentelemetry-operator in GKE Autopilot (v1.21) and I am finding a weird behavior when I create a collector, the control-plane operator seems to start to create new replicaSets out of control.

1. First I installed the latest cert-manager
2. Enable firewall in GKE
3. Installed the latest release of opentelemetry-operator
4. Created a collector.

I noticed t

Currently (as of 0.7.0) NEOS tutorial that is opening up next to Cloud Shell window has 9 pages. 6 of them look similar but shorter versions of what's available in the user guide.
We want to shorten the NEOS tutorial and move details into the user guide. (Hugo static website under /website folder)

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.

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:

Apple comes with CFNetwork API to enable applications to interact with FTP and HTTP protocols to access Internet resources. This means it doesn't explicitly need to use curl as an HTTP client library.

otel-cpp is designed to plugin any external client library by extending abstract classes defined in the ext::http::client namespace.
And HttpClientFactory factory is responsible to pick up the co

The current Getting Started guide includes a demo that use Zipkin, Jaeger and Prometheus. I am looking for a more simpler guide. Something that would show how to send a metric(s) using a utility like CURL and seeing the metric being recorded in a local file. This would help confirm that the installation of OTEL Collector is working normally.

Currently, we allow to filter by specific databases/orm like mongo/sequelize.

We want to enable this same behavior on elasticsearch, so users could filter by elasticsearch spans easily.

This is an example of usage in sequelize

const sequelizeActivities = spans.sequelize();
expect(sequelizeActivities.length).toBe(1);
expect(sequelizeActivities.first.dbOperation).toBe("SELECT");
expec