Deployment to staging by prashant-shahi SigNoz/signoz

1 new commit pushed to

<https://github.com/SigNoz/signoz/tree/develop|develop>

by srikanthccv

<https://github.com/SigNoz/signoz/commit/c5991b50bc1bbb37c3374c20388c04171490ef4f|c5991b50>

- fix: nan aggregation values are ignored (#2664) SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz

#2675 Unable to filter exceptions using resource attributes Issue created by al-mcintosh Bug description Please describe. If this affects the front-end, screenshots would be of great help. Currently, there is only one available field available signoz.collector.id nothing else. Here is an exception record that does indeed contain

k8s_namespace_name

select * FROM signoz_traces.distributed_signoz_error_index_v2 limit 1

┌─────────────────────timestamp─┬─errorID──────────────────────────┬─groupID──────────────────────────┬─traceID──────────────────────────┬─spanID───────────┬─serviceName─┬─exceptionType────────────────────────────────────────┬─exceptionMessage───┬─exceptionStacktrace────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┬─exceptionEscaped─┬─resourceTagsMap────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐  
│ 2023-05-02 00:00:12.326284860 │ a78affb938ab4d85ba7364c0351fa656 │ f767290ce9682bc52f8b23267e352bc5 │ e7eca14967f924759b77d39fa062494a │ 63351f06a0bbc171 │ acme-server │ com.biztech.acme.exceptions.NotFound │ Pin Not Recognized │ com.biztech.acme.central.api.exceptions.NotFound: Pin Not Recognized  
│ false │ {'os.description':'Linux 5.15.0-1035-azure','os.type':'linux','process.pid':'1','process.runtime.name':'OpenJDK Runtime Environment','service.name':'acme-server','telemetry.sdk.language':'java','k8s.deployment.name':'acme','k8s.pod.name':'acme-7c96459d5-mrg5f','k8s.pod.uid':'ebab11df-2a4a-4e27-af67-4af8432b5dc9','container.id':'6eea1b662df0e810d789a792a81677161663817e109c1a30a4dd878b86cf5e71','host.arch':'amd64','telemetry.sdk.version':'1.23.1','k8s.node.name':'agentpool-000013','telemetry.auto.version':'1.23.0','k8s.pod.ip':'10.240.0.41','k8s.pod.start_time':'2023-04-14 06:30:34 +0000 UTC','signoz.collector.id':'89eb1714-a562-4c0f-82f0-9fea2a673757','host.name':'acme-7c96459d5-mrg5f','telemetry.sdk.name':'opentelemetry','k8s.namespace.name':'lecreuset'} │  
└───────────────────────────────┴──────────────────────────────────┴──────────────────────────────────┴──────────────────────────────────┴──────────────────┴─────────────┴──────────────────────────────────────────────────────┴────────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┴──────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

Expected behavior How to reproduce 1. Visit /exceptions 2. Click into the Search and filter field, Note: The Loading activity spinner appears for 1 - 2 seconds, then

signoz.collector.id

(the only filter field option) appears. Version information • Signoz version: 0.18.3 • Browser version: Chrome 112.0.5615.138 (Official Build) (64-bit) • Your OS and version: Ubuntu 18.04.6 LTS • *Your CPU Architecture*(ARM/Intel): linux (amd64) Additional context Thank you for your bug report – we love squashing them! SigNoz/signoz

#128 Feat/v0.69.0 Pull request opened by nityanandagohain on <!date^1682662442^{date_short}|2023-04-28T06:14:02Z> This PR upgrades upstream dependency to v0.69.0 SigNoz/signoz-otel-collector GitHub Actions: lint-and-test ✅ 2 other checks have passed 2/3 successful checks

#221 Release/signoz 0.14.4 Pull request opened by prashant-shahi Signed-off-by: Prashant Shahi prashant@signoz.io SigNoz/charts ✅ All checks have passed 2/2 successful checks

1 new commit pushed to

<https://github.com/SigNoz/signoz/tree/develop|develop>

by srikanthccv

<https://github.com/SigNoz/signoz/commit/12349d79a94ae6621cbbdb014e67c6c516dffe29|12349d79>

- feat(query-service): alerts integration with query builder v3 (#2663) SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz

#2676 SigNoz - Architecture New discussion created by PlaySon-cloud Hi, there. I would like to request some help to try to understand the logic view of SigNoz. Like, the software architecture design decisions. Basically, I would like to be able to do some diagrams like this one, but I've the required knowledge yet about SigNoz to achieve that. Regards, PlaySon SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz

#2677 Fix: Key operations table show NaN if no value Pull request opened by ksorv As seen in the screenshot, for my initial setup of the repo, I think some dummy data comes.. But there is no check for what happens if

value

in the table operations is undefined, leading to

NaN

. Fixed by simply using 0 of value is falsy. Please check and let know if its needed. SigNoz/signoz GitHub Actions: build-ee-query-service GitHub Actions: build-frontend GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: build-query-service GitHub Actions: Codeball ✅ 3 other checks have passed 3/9 successful checks

1 new commit pushed to

<https://github.com/SigNoz/charts/tree/main|main>

by prashant-shahi

<https://github.com/SigNoz/charts/commit/e285fab628c6eeddccd3c29f597ffda95478c0bd|e285fab6>

- Release/signoz 0.14.4 (#221) SigNoz/charts

Release - signoz-0.14.4 New release published by github-actions[bot] SigNoz Observability Platform Helm Chart SigNoz/charts

Deployment to github-pages by github-pages[bot] SigNoz/charts

1 new commit pushed to

<https://github.com/SigNoz/signoz/tree/develop|develop>

by palashgdev

<https://github.com/SigNoz/signoz/commit/f7cd0d49347033fcf9b26a34d627ccb9d694b6ab|f7cd0d49>

- [Fix]: Alert Channels breadcrumbs (#2669) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#222 Is it possible to configure/set QoS to Guaranteed? Issue created by erplsf Greetings, We want to run Clickhouse (and other components) at QoS of Guaranteed, but I see that there are init containers which don't inherit the main container resource settings which prevents k8s from giving the pod QoS of Guaranteed, and as such, it will not perform as good as it could. Is there any plans or existing support to mitigate this or should someone suggest a PR for it? SigNoz/charts

#2681 Issues with tracing in Vue application New discussion created by alvaro-baranoski Greetins everyone, I am trying to connect my Vue frontend to SigNoz via OpenTelemetry. I am following this tutorial, however, since our project is using TypeScript I had to do some modifications. The problem that I'm facing is that the application is not able to connect to the /v1/traces endpoint. I've tried creating a single simple span to test the connection, but it still fails (in firefox, the request gets blocked and I get the NS_BINDING_ABORTED error). Has someone experienced the same issue? Is there another tutorial/documentation that I can look into to solve my issue? Thanks a bunch! My tracing.ts:

import { WebTracerProvider } from '@opentelemetry/sdk-trace-web';
import { getWebAutoInstrumentations } from '@opentelemetry/auto-instrumentations-web';
import { CollectorTraceExporter } from '@opentelemetry/exporter-collector';
import { ConsoleSpanExporter, SimpleSpanProcessor, Span } from '@opentelemetry/sdk-trace-base';
import { registerInstrumentations } from '@opentelemetry/instrumentation';
import { ZoneContextManager } from '@opentelemetry/context-zone';
import { B3Propagator } from '@opentelemetry/propagator-b3';
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http'
import { Resource } from '@opentelemetry/resources';
import { FetchInstrumentation } from '@opentelemetry/instrumentation-fetch';

export default function setupTracing() {
  console.log("[INFO] Setting up tracing...");
  
  const serviceName = "AssistenteFrontend";
  const resource = new Resource({ "service.name": serviceName });
  const provider = new WebTracerProvider({ resource });
  
  const collector = new OTLPTraceExporter({
    url: "<http://172.31.29.XXX:4318/v1/traces>",
    headers: { }
  });

  provider.addSpanProcessor(new SimpleSpanProcessor(collector));
  provider.register({
      contextManager: new ZoneContextManager()
  });
  
  const webTracerWithZone = provider.getTracer(serviceName);

  const span = webTracerWithZone.startSpan("");
  span.updateName("POST <http://google.com>");

  for (let index = 0; index < 1000; index++) {
    continue;
  }
  span.end();
}

My

otel-collector-config.yaml

CORS configuration:

otlp:
  protocols:
    http:
      cors:
        allowed_origins: ["*"]
        allowed_headers: ["*"]
        max_age: 7200

SigNoz/signoz

#2682 chore: removed some of the stage logic in the query builder Pull request opened by palashgdev part of #2356 can be addressed after #2657 SigNoz/signoz GitHub Actions: build-query-service GitHub Actions: build-ee-query-service GitHub Actions: lint-commits GitHub Actions: dependency-review GitHub Actions: update_release_draft GitHub Actions: Codeball GitHub Actions: remove GitHub Actions: build-frontend GitHub Actions: playwright ✅ No checks have passed 0/9 successful checks

1 new commit pushed to

<https://github.com/SigNoz/signoz/tree/develop|develop>

by palashgdev

<https://github.com/SigNoz/signoz/commit/8679f2c37a068cf83935a478acac23ce3d22d0a6|8679f2c3>

- feat: add query builder to the alerts (#2657) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#2683 fix: query builder filter label is adopted for dark mode Pull request opened by palashgdev fixed the dark mode and light of the query builder current: fixed: Screen.Recording.2023-05-10.at.11.51.07.PM.mov SigNoz/signoz GitHub Actions: playwright GitHub Actions: lint-commits ✅ 7 other checks have passed 7/9 successful checks

#2678 fix: disable prometheus.NormalizeName flag Pull request opened by srikanthccv Part of SigNoz/signoz-otel-collector#130 This flag strips away the Prometheus suffixes (

total

,

sum

,

count

) and has been enabled by default since v0.76.3. This isn't just limited to

signoz_calls_total

but at the receiver level in general. Disabling seemed the best action for now. SigNoz/signoz GitHub Actions: remove GitHub Actions: update_release_draft GitHub Actions: dependency-review GitHub Actions: build-ee-query-service GitHub Actions: lint-commits GitHub Actions: build-query-service GitHub Actions: build-frontend GitHub Actions: playwright GitHub Actions: Codeball ✅ No checks have passed 0/9 successful checks

#2679 fix: update the resource detection processor name for GCP Pull request opened by srikanthccv Part of SigNoz/signoz-otel-collector#130 SigNoz/signoz GitHub Actions: build-frontend GitHub Actions: update_release_draft GitHub Actions: remove GitHub Actions: dependency-review GitHub Actions: playwright GitHub Actions: Codeball GitHub Actions: build-query-service GitHub Actions: lint-commits ✅ No checks have passed 0/8 successful checks

#2684 Question about license New discussion created by prasanna4742 Hi, If I want to use community open-source edition in production - do I need to clone the repo, remove ee directory, build and then use that binary? Or I can simply use the docker image provided by signoz, and enterprise features would be locked somehow? (Point is, I want to use community edition in production, do not want to end-up violating license just becasue I'm using direct docker image.) Thanks, Prasanna SigNoz/signoz

Comment on #2684 Question about license Discussion answered by ankitnayan

I can simply use the docker image provided by signoz, and enterprise features would be locked somehow?

This is correct SigNoz/signoz

1 new commit pushed to

<https://github.com/SigNoz/signoz/tree/develop|develop>

by srikanthccv

<https://github.com/SigNoz/signoz/commit/38bfc41190b2a9e9bff49e1b120421b37033039a|38bfc411>

- fix: disable prometheus.NormalizeName flag (#2678) SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz

1 new commit pushed to

<https://github.com/SigNoz/signoz/tree/develop|develop>

by srikanthccv

<https://github.com/SigNoz/signoz/commit/25398d9d35b7b08050e166aa1d0799d968fcd86c|25398d9d>

- fix: query builder filter label is adopted for dark mode (#2683) SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz