#2062 Rearranging layout of a dashboard causes all APIs to be fired again and all panels reload Issue created by ankitnayan https://www.loom.com/share/0801a7afd8184f719b64647c5f70f7c5 SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/1e39131c38108eb7ebf12cc19f91464a278db53d|1e39131c>

- feat: drag select timeframe on charts (#2018) SigNoz/signoz

Deployment to staging by ankitnayan SigNoz/signoz

#2063 highlight the value in tooltip of chart line which is nearer to the cursor Issue created by ankitnayan https://www.loom.com/share/fd50281b39c8464da532ac9e476ca8d0 SigNoz/signoz

#1856 Not able to send resource attributes in nodejs application Issue created by rajsingh1109 I tried sending the resource attributes by setting environment variables and also by making changes in tracing.js file but only three resource attributes(service.name, service.namespace, deployment.environment) are able to reflect in dashboard. Remaining attributes(application.owner,project.name,application.location,application.department,company.name) are not shown. Few Attempts - 1-

resource: new Resource({

	"service.name": "nodejs1",
	"service.namespace": "gs1",
	"deployment.environment": "prod1",
	   "application.owner": "owner",
	   "project.name": "p1",
	   "application.location": "l1",
	   "application.department": 'd3',
	   "company.name": "c4"
      })

2-

resource: new Resource({
      [SemanticResourceAttributes.SERVICE_NAME]: 'appServiceName',
      [SemanticResourceAttributes.SERVICE_NAMESPACE]: 'appServiceNameSpace',
      [SemanticResourceAttributes.COMPANY_NAME]: 'myCompany',
      [SemanticResourceAttributes.DEPLOYMENT_ENVIRONMENT]: 'prod',
      [SemanticResourceAttributes.APPLICATION_LOCATION]: 'mumbai',
      [SemanticResourceAttributes.PROJECT_NAME]: 'newProject',
      [SemanticResourceAttributes.APPLICATION_DEPARTMENT]: 'dev',
      [SemanticResourceAttributes.APPLICATION_OWNER]: 'owner'
      })

3-

['service.name']: 'nodejs12',
	['service.namespace']: "gs12",
	['deployment.environment']: 'prod12',
	['application.owner']: "raj",
	   ['project.name']: "raj1",
	   ['application.location']: 'raj2',
	   ['application.department']: 'raj3',
	   ['company.name']: "raj4"

4-

const resource = new Resource({
    [SemanticResourceAttributes.SERVICE_NAME]: 'api-service-11',
});
const anotherResource = new Resource({
    'service.version': '2.0.0',
    'service.group': 'instrumentation-group-11',
    'service.namespace': "gs11",
	'deployment.environment': 'prod11',
	   'application.owner': 'raj',
	   'project.name': 'raj1
const mergedResource = resource.merge(anotherResource);

5- `env OTEL_RESOURCE_ATTRIBUTES="service.name=app.js,application.owner= raj,project.name=raj1,application.location=raj2,application.department=raj3,company.name=raj4,service.namespace=tutorial,service.version=1.0,service.instance.id=`uuidgen`" node --require './tracing.js' wss2.js` all attempts show only thre attributes (service.name, service.namespace, deployment.environment) SigNoz/signoz

#2064 [EPIC] - Cost Control of Observability data Issue created by ankitnayan ☐ Show ingestion rate and cardinality of metrics ☐ Drop rules for metrics ☐ Sampling rules for traces ☐ Sampling rules for logs ☐ Query analysis and insights SigNoz/signoz

#2037 feat(ui): dashboard variable chaining Pull request opened by srikanthccv Addresses #1973 https://www.loom.com/share/75fb347f451e4c12b49c6f227e2918fc This PR adds support for variable chaining. Whenever a variable changes, its dependent variable should be updated too. The default value for this dependent variable will be ALL values for multi-select and the first option for single-select. The independent variable remains the same. Code changes: There is a new API for this. This new API is

POST

request which accept the payload of the following type.

{
  "query": "select distinct(JSONExtractString(labels, 'operation')) FROM signoz_metrics.time_series_v2 Where JSONExtractString(labels, 'service_name') IN {{.service_name}};",
  "variables": {
    "http_status_code": "",
    "op": [
      "/driver.DriverService/FindNearest",
      "HTTP GET /dispatch",
      "HTTP GET: /route",
      "HTTP GET: /customer",
      "HTTP GET",
      ""
    ],
    "service_name": [
      "frontend"
    ],
    "span_kind": "SPAN_KIND_SERVER"
  }
}

And the VariableItem is updated with its

onVarUpdate

triggering subsequent updates for dependent vars. SigNoz/signoz GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: remove ✅ 9 other checks have passed 9/12 successful checks

#2065 Out-of-the-box monitoring and metrics for Kafka clusters Issue created by pranay01 Feature request from a SigNoz user There are absolutely resources for hooking up OTEL up to Kafka clients but there's a gap there for measuring Kafka itself. Atm we've got some janky dashboards on AWS Cloudwatch that show max offset lag for a few topics. It would be insane if there was some .jar or Kafka Connect Connector that we could configure to push metrics (and logs) to Signoz. We could then create some dashboards that give us an idea of the health of our Kafka clusters running in both dev and prod in the same place SigNoz/signoz

#2066 Support shareable filters in `/logs` page URLs Issue created by inbrewj-udc Is your feature request related to a problem? Yes and no - I don't think this is a bug per se, just a feature that hasn't been fleshed out yet. Describe the solution you'd like Whenever I type a query into the field in the

Logs

module, I see the query being added to the query parameters in the URL: However, if I were to share this link with colleagues, or add it to a tag on an alert, the query params would be lost as soon as the page loads. It would be brilliant if the

/logs

page would read the query parameters and populate the query field after the page loads (whilst still keeping the query params visible in the address bar!) Describe alternatives you've considered • Saving queries in text files and other manual copy / paste solutions SigNoz/signoz

#2067 High memory usage by clickhouse Issue created by ankitnayan Clickhouse consumes high memory when kept running for weeks. Data ingestion rate is ~500M spans/day. Retention period of 7days. Disk usage of 1.2 TB

NAME                                                        CPU(cores)   MEMORY(bytes)
chi-my-release-clickhouse-cluster-0-0-0                     2100m        174286Mi
my-release-clickhouse-operator-6684c886f8-gpzwk             1m           95Mi
my-release-signoz-alertmanager-0                            2m           47Mi
my-release-signoz-frontend-664c588f54-hlk5n                 1m           106Mi
my-release-signoz-otel-collector-f5977cfc9-78w2t            966m         1290Mi
my-release-signoz-otel-collector-f5977cfc9-9q9dp            1017m        1012Mi
my-release-signoz-otel-collector-f5977cfc9-fqxd6            999m         1221Mi
my-release-signoz-otel-collector-metrics-566b4c9f86-h2gpn   413m         762Mi
my-release-signoz-query-service-0                           11m          330Mi
my-release-zookeeper-0                                      3m           482Mi

SigNoz/signoz

#143 k8sattribute fixes with related hostmetrics and clusterrole changes Pull request opened by prashant-shahi Signed-off-by: Prashant Shahi prashant@signoz.io SigNoz/charts ✅ All checks have passed 2/2 successful checks

#2068 fix: Chart loaders on reload and change of time interval at dashboard Pull request opened by csudani7 Close #2073 Close #2074 SigNoz/signoz SonarCloud: Quality Gate failed GitHub Actions: playwright GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: Codeball GitHub Actions: lint-commits ✅ 7 other checks have passed 7/12 successful checks

#2069 Tier queries to clickhouse based on priority Issue created by ankitnayan We should tier the requests based on priority of the query/feature. Eg alerts should be run with higher priority. We can control resources allocated to requests using 2 settings: •

os_thread_priority

•

max_threads

the query-service should maintain multiple connections to clickhouse and different connections can be used to query for different use cases. There is probably some more work going in clickhouse and let's check them out when building this functionality in signoz. SigNoz/signoz

#83 chore: add trace exporter db latency Pull request opened by makeavish closes: #77 SigNoz/signoz-otel-collector ✅ All checks have passed 3/3 successful checks

#2070 Logs page doesn't respect query string present in url. Issue created by nityanandagohain Bug description If we share a logs url which contains a query, it is not respected when we paste the url with query. Expected behavior It should render the query present in the url How to reproduce 1. Select a filter in logs 2. Copy the url 3. Open the url in the new tab, the filter will be lost SigNoz/signoz

#2071 Deploying SigNoz the GitOps way Issue created by ankitnayan Some references to look into https://www.gitops.tech/ https://medium.com/engineering-at-palo-alto-networks/garuda-journey-towards-unified-operator-for-observability-platform-part-1-82b453a1111a SigNoz/signoz

#2072 Feeback to GitOps using SigNoz Issue created by ankitnayan https://www.infoq.com/articles/observability-gitops/ https://www.weave.works/blog/gitops-part-3-observability SigNoz/signoz

#84 Add default timestamp if timestamp is empty Pull request opened by nityanandagohain Fixes SigNoz/signoz#1806 SigNoz/signoz-otel-collector GitHub Actions: Analyze ✅ 1 other check has passed 1/2 successful checks

#2073 Replace loading icon in central panel to top right smaller one Issue created by palashgdev SigNoz/signoz

#2074 Show the old data in the chart unless the API call is complete Issue created by palashgdev SigNoz/signoz

#2075 Check if we need to re-render the chart on data change or a smoother interaction is possible? Issue created by palashgdev SigNoz/signoz

#2076 Highlight the datapoint in charts Issue created by ankitnayan Adding a cursor has reduced the visibility of datapoint. Can we make the datapoint more prominent by making it a bit larger and filling with color of the chart? Or suggest alternate ways to increase visibility and clickability. SigNoz/signoz

#2077 Fixing tooltip position Issue created by ankitnayan https://www.loom.com/share/cf502c9329f54e8e9381f2456385ecbb SigNoz/signoz

2 new commits pushed to

<https://github.com/SigNoz/signoz-otel-collector/tree/main|main>

by nityanandagohain

<https://github.com/SigNoz/signoz-otel-collector/commit/d54dd7c3e7a0f70fcfbe2412a9778ad273a040d4|d54dd7c3>

- Add default timestamp if timestamp is empty

<https://github.com/SigNoz/signoz-otel-collector/commit/c9b8f8ee1ca3e0e6e82f45f98bca0d9a6b05d26e|c9b8f8ee>

- Merge pull request #84 from SigNoz/issue-1806 SigNoz/signoz-otel-collector

#1806 Default current timestamp if timestamp not present or timestamp parsing fails. Issue created by nityanandagohain Is your feature request related to a problem? As of now if there is no timestamp present in logs it is set to epoch 0, which makes it difficult to debug. Describe the solution you'd like We can set it to current time when the log is received by the collector. SigNoz/signoz

1 new commit pushed to

<https://github.com/SigNoz/signoz-otel-collector/tree/main|main>

by makeavish

<https://github.com/SigNoz/signoz-otel-collector/commit/39e7a617da43dae0d2040407f705b38c62d719a4|39e7a617>

- chore: add trace exporter db latency (#83) SigNoz/signoz-otel-collector

#2078 fix: Changed Legends UI & Scrollable Pull request opened by csudani7 Close: #787 SigNoz/signoz GitHub Actions: playwright GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: lint-commits GitHub Actions: Codeball ✅ 8 other checks have passed 8/12 successful checks

#2079 Update the graph y/x axis color to be more visible/clear Issue created by palashgdev Bug description Please describe. If this affects the front-end, screenshots would be of great help. reference: https://www.loom.com/share/0c75ee846aac41c493e79561dd482dc4 Expected behavior ticks in graph would be visible in light and dark mode SigNoz/signoz

#2080 fix: Changed axis label color Pull request opened by csudani7 Close: #2079 SigNoz/signoz GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: Codeball ✅ 8 other checks have passed 8/12 successful checks

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/fa652be926cd699e54f718fe2f674461168cef0a|fa652be9>

- fix: Changed axis label color (#2080) SigNoz/signoz