How do I fill in the method for my traces? I thought it was just the http.method tag but that seems to be set already

Hi team, tow question about logs: 1、maybe signoz cannot support application inside logs? 2、and can go-zero framework be supported by signoz? my go application used go-zero framework not gin。 thanks

what should be the value of clickhouse endpoint if I am using a standalone(seperately hosted) cluster of three shards.....should I just point to a load balancer which forwards to all my shards randomly or do I have to mention the host of all the three clickhouse nodes?

Is there a way to delete the data from click house directly. The frontend is taking a lot of time.

Hi, #support how to integrate signoz with grpc front end react app.. please share some sample repo.

is there a way to customize the name using a processor in this screen:

HI [12:44 AM] Getting below error while installing signoz helm through flux signoz-apm-monitoring False Helm install failed: template: signoz/charts/k8s-infra/templates/otel-deployment/deployment.yaml5816: executing "signoz/charts/k8s-infra/templates/otel-deployment/deployment.yaml" at <include "snippet.otlp-env" .>: error calling include: template: signoz/charts/k8s-infra/templates/_helpers.tpl37812: executing "snippet.otlp-env" at <include "otel.endpoint" .>: error calling include: template: signoz/charts/k8s-infra/templates/_helpers.tpl25022: executing "otel.endpoint" at <.Chart.IsRoot>: can't evaluate field IsRoot in type interface {} False

Hello, I want to monitor Apache. For this, in otel-collector-config.yaml I have added these lines: receivers: Apache: endpoint: "http://localhost:80/server-status?auto" Where can I see the metrics of my Apache server? In alerts I can't see the metrics.

Hi.. I am getting error on server deployment of alert manager because SIGNOZ_LOCAL_DB_PATH(/var/lib/signoz/signoz.db) .. Trying to figure out what is alternative for server deployment. I am trying to deploy via docker standalone.

can go-zero framework be supported by signoz? my go application used go-zero framework not gin。

how can I send my logs to the otel collector from my gin app without outputting it in a file? (I tried to use otel.SetLogger function but it does not seem to work)

Hi Team, Need help on below error. 2023-02-27T185923.248Z error exporterhelper/queued_retry.go:394 Exporting failed. The error is not retryable. Dropping data. {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination", "errorCauses": [{"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}], "dropped_items": 47} go.opentelemetry.io/collector/exporter/exporterhelper.(*retrySender).send /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/queued_retry.go:394 go.opentelemetry.io/collector/exporter/exporterhelper.(*metricsSenderWithObservability).send /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/metrics.go:135 go.opentelemetry.io/collector/exporter/exporterhelper.(*queuedRetrySender).start.func1 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/queued_retry.go:205 go.opentelemetry.io/collector/exporter/exporterhelper/internal.(*boundedMemoryQueue).StartConsumers.func1 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/internal/bounded_memory_queue.go:61

In the new table log view (which is a great improvement), how do I add a field to the table which does not show up under _INTERESTING_FIELDS_? For some reason the log message body is not showing up there, which I find quite interesting.

@Prashant Shahi @nitya-signoz @Ankit Nayan In services, we are not getting all the metrics data like no data base calls, no external calls metrics etc. Below are the screen shots Could u plz help me to debug the issue?

#2405 Signoz Otel Collect Issue Issue created by kskr0244 Hello Team, Please find the issue details below. 2023-02-28T031315.576Z error exporterhelper/queued_retry.go:394 Exporting failed. The error is not retryable. Dropping data. {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination; Permanent error: invalid temporality and type combination", "errorCauses": [{"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}, {"error": "Permanent error: invalid temporality and type combination"}], "dropped_items": 48} go.opentelemetry.io/collector/exporter/exporterhelper.(*retrySender).send /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/queued_retry.go:394 go.opentelemetry.io/collector/exporter/exporterhelper.(*metricsSenderWithObservability).send /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/metrics.go:135 go.opentelemetry.io/collector/exporter/exporterhelper.(*queuedRetrySender).start.func1 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/queued_retry.go:205 go.opentelemetry.io/collector/exporter/exporterhelper/internal.(*boundedMemoryQueue).StartConsumers.func1 /go/pkg/mod/go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/internal/bounded_memory_queue.go:61 SigNoz/signoz

Hi, After adding json parser to my logs in

k8s-infra

log counter in

logs

section works but there is no data in events section, also fields are loaded correctly

Hey I've created an alert in which I've set the condition to fire the alert when the value goes below threshold, but instead it's firing even when the value is higher than that of threshold, attached screenshots for more insight

We're deploying signoz on our test servers. I see there are quite a lot of containers started.

Are all of them important?

clickhouse
clickhouse-setup-alertmanager-1
clickhouse-setup-otel-collector-1
clickhouse-setup-otel-collector-metrics-1
frontend
hotrod
load-hotrod
query-service
zookeeper-1

I installed SigNoz with the provider docker-compose that has the sample application running. However I don’t see any database calls on any of the services. Why is that?

Even with my application instrumented I don’t see any entries in the “Database Calls” screen. I do see SQL in traces

The documentation states that manual instrumentation can be combined with automatic instrumentation for java applications. Is there an example of this? Having difficultly finding the right set of jars. The documentation here : https://opentelemetry.io/docs/instrumentation/java/manual/ has code snippets and jars to use but the io.opentelemetry.sdk.resources.Resource class is not present in the 1.23.1 sdk jar

I added the following code but where “my-service-name” matches the service name from the automatic instrumentation and what appears in SigNoz. However the operation “my-operation-name” never appears anywhere.

Tracer tracer = GlobalOpenTelemetry.getTracer("my-service-name");

        Span childSpan = tracer.spanBuilder("my-operation-name").setSpanKind(SpanKind.SERVER).startSpan();
        childSpan.setAttribute("foo", "bar");

Hi team, One quick question is there a way to implement retention of logs data via helm chart and not fromt the UI, or do we have a way to clear that vial clickhouse command?

If I am hosting my own clickhouse cluster with three shards how should I mention the url of my three shards https://signoz.io/docs/operate/clickhouse/distributed-clickhouse/, in this doc we are not really changing the clickhouse url in otel-collector-config file...so does signoz automatically distribute data between different nodes/shards....should I connect a load balancer between the clickhouse instances and other services to distribute the load?(also is it possible to run migrations without toggling the setting in otel collector service env DOCKER_MULTI_NODE_CLUSTER=false)

Given that there is no way to use the

datadog

exporter with the signoz otel collector, would it be possible to disable the OTEL collector entirely within the signoz helm chart, and only install the query service, front-end, clickhouse and alert manager? and let an external otel collector provide the actual telemetry? I need to export my traces and metrics to both services.

Hi, I made my fastapi app to log data into json format also I added

span_id

and

trace_id

in my log (type is

int

) but logs are not shown in signoz here is my code

import json_logging
import logging
import sys
from config import config
from fastapi import FastAPI

app = FastAPI(title=config.app_title)


class JSONLogWebFormatter(json_logging.JSONLogFormatter):
    """
    Formatter for web application log
    """

    def _format_log_object(self, record, request_util):
        json_log_object = super(JSONLogWebFormatter, self)._format_log_object(
            record, request_util
        )
        current_span = trace.get_current_span()
        if current_span:
            json_log_object["span_id"] = current_span.get_span_context().span_id
            json_log_object["trace_id"] = current_span.get_span_context().trace_id
        json_log_object.update(
            {
                "correlation_id": request_util.get_correlation_id(
                    within_formatter=True
                ),
            }
        )
        return json_log_object


json_logging.init_fastapi(enable_json=True, custom_formatter=JSONLogWebFormatter)
json_logging.init_request_instrument(app, custom_formatter=JSONLogWebFormatter)

# init the logger as usual
logger = logging.getLogger()
logger.setLevel(logging._nameToLevel[config.log_level.upper()])
logger.addHandler(logging.StreamHandler(sys.stdout))

Hi Everyone, Excited to setup Signoz for our NestJS based microservices architecture, I just setup the docker installation and found out that the dashboard already contains some garbage data, how can I remove that ? can some one point me to the documentation if it already exists ?

Here is a screenshot of all the services I am running for Signoz hosted in a k8 cluster.

Hi Everybody! I had just configured Signoz on my POC server - a Kubernetes single node with a Flask application executed with Gunicorn. I get traces all right but I have questions regarding logs: A - The only logs I get are from the k8s operator, which follows the k8s logs file. That's an issue since it will break any multiline log into single lines, which is not useable. How do I get the python OTEL instrumentation to send logs to the collector? B - I guess it's a side effect of A but the Exceptions tab stays clean even though I trigger some exceptions on the Flask server.