#1917 Easy way to filter attributes which are not empty in logs Issue created by pranay01 Is your feature request related to a problem? Currently, there is no easy way to filter log lines which don't have non empty values for a particular attribute. Today, there is a work around by setting

NCONTAINS

or

NIN

and filter out such logs, but IMO it should be easier to filter log lines as this may be a common use case. Something like

IS SET

/

IS NOT SET

may be useful here Describe the solution you'd like Introduce specific operators like

IS SET

/

IS NOT SET

Describe alternatives you've considered setting

NCONTAINS

or

NIN

to

''

other nul values Additional context Add any other context or screenshots about the feature request here. Thank you for your feature request – we love each and every one! SigNoz/signoz

#1918 fix: resolves issue related ops not flowing from search box to panel Pull request opened by mindhash This PR solves issue related to logs filter. Steps to reproduce: • Enter query in search box. keep query panel open while you enter the search query • The entered query should auto populate search fields in the panel but current operators like "IN" is not set as expected. SigNoz/signoz

#1919 add exception page filters support Pull request opened by makeavish Closes #1893 SigNoz/signoz

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/4b13b0a8a4f4ab041d197d3cce16bc0f276ee407|4b13b0a8>

- fix: resolves issue related ops not flowing from search box to panel (#1918) SigNoz/signoz

#1921 fulltext only work with `contains` or `ncontains` operators? Issue created by pranay01 Does fulltext only work with

contains

or

ncontains

operators? Trying to use it with

in

/`nin` is giving inaccurate results Slack Message SigNoz/signoz

#1920 fix: added clear filters button Pull request opened by mindhash on <!date^1672066439^{date_short}|2022-12-26T14:53:59Z> This PR adds clear filters button in log search query panel. SigNoz/signoz GitHub Actions: e2e-k3s SonarCloud: Quality Gate failed GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: Codeball GitHub Actions: Ensure Pull Request has a linked issue. ✅ 7 other checks have passed 7/13 successful checks

#1922 Chore/analytics Pull request opened by ankitnayan SigNoz/signoz

1 new commit pushed to

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

by prashant-shahi

<https://github.com/SigNoz/charts/commit/a2d3e965fbf32b0f69ca1fb68725751ed705428e|a2d3e965>

- fix: proxy_read_timeout updated in nginx conf (#116) SigNoz/charts

#49 Add cardinality logs and exclude pattern capability Pull request opened by srikanthccv Fixes #41 SigNoz/signoz-otel-collector GitHub Actions: lint-and-test GitHub Actions: Analyze ✅ No checks have passed 0/2 successful checks

#1900 fix: respect durationSort feature flag on getSpanFilters API Pull request opened by makeavish on <!date^1671707678^{date_short}|2022-12-22T11:14:38Z> SigNoz/signoz GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: Ensure Pull Request has a linked issue. ✅ 9 other checks have passed 9/12 successful checks

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/eef48c54f837f0d5f0614ab0767afd973c3169d4|eef48c54>

- fix(query_range): invalid memory address or nil pointer dereference (#1875) SigNoz/signoz

#1923 Command `sudo make dev-setup` gives Error if `sqlite3` is not installed already in a system. Issue created by axaysagathiya Is your feature request related to a problem? The

sudo make dev-setup

command gives Error if

sqlite3

is not installed already in a system. Please describe. Describe the solution you'd like • Add commands in Makefile to install

sqlite3

. Describe alternatives you've considered • We could add steps to install

sqlite3

in the Documentation. Additional context Add any other context or screenshots about the feature request here. Thank you for your feature request – we love each and every one! SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/13a6d7f7c6d0007466f20e802522152be58bc6ba|13a6d7f7>

- fix: live tail time out is updated (#1899) SigNoz/signoz

#1924 add commands to install sqlite3 in Makefile. Pull request opened by axaysagathiya Added commands to install

sqlite3

in Makefile. Closes #1923 SigNoz/signoz

#1925 increase dimensions_cache_size for signozspanmetrics processor Pull request opened by srikanthccv The memory allocation for cache entries is dynamic and not pre-allocated at the initialisation. Big-scale users can always bump it up if their resources can support more. When it starts to fill unexpectedly they will be able to see some informative logs after this SigNoz/signoz-otel-collector#49 SigNoz/signoz

#118 Increase dimensions_cache_size for signozspanmetrics processor Pull request opened by srikanthccv Same as SigNoz/signoz#1925 for charts SigNoz/charts

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/48a6f536fad59d38b5f791d18d56faa342663498|48a6f536>

- chore: increase dimensions_cache_size for signozspanmetrics processor (#1925) SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/charts/commit/1a352acb593af3fd366ce200ec4fd742efc8e1f2|1a352acb>

- Increase dimensions_cache_size for signozspanmetrics processor (#118) SigNoz/charts

#1926 fix: per page is added in the dependancy Pull request opened by palashgdev Close #1916 SigNoz/signoz

#1927 feat: loading is added in the button Pull request opened by palashgdev Close #1914 SigNoz/signoz

#1928 Terraform timeout when deploying helm chart to minikube Issue created by mariuskimmina Bug description Hey, I was attempted to deploy SigNoz to a local minikube. I was using the helm chart https://github.com/SigNoz/charts for it. Terraform Code

terraform {
  required_providers {
    kubernetes = {
      source  = "hashicorp/kubernetes"
      version = "2.11.0"
    }
  }
}

provider "kubernetes" {
  config_path    = "~/.kube/config"
  config_context = "minikube"
}

provider "helm" {
  kubernetes {
    config_path = "~/.kube/config"
  }
}

resource "helm_release" "signoz" {
  name       = "signoz"
  repository = "<https://charts.signoz.io>"
  chart      = "signoz"
}

When running

terraform apply

I ran into a timeout after 5 Minutes. Looking at Minikube dashboard, the otel collectors failed to start From their logs:

2022-12-27T12:49:38.224Z info service/telemetry.go:111 Setting up own telemetry...
2022-12-27T12:49:38.224Z info service/telemetry.go:141 Serving Prometheus metrics {"address": "0.0.0.0:8888", "level": "Basic"}
2022-12-27T12:49:38.224Z info components/components.go:30 Stability level of component is undefined {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "stability": "Undefined"}
time="2022-12-27T12:49:38Z" level=info msg="Executing:\nCREATE DATABASE IF NOT EXISTS signoz_metrics ON CLUSTER cluster\n" component=clickhouse
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x3864f79]

That being said, despite Terraform timing out (probably because it couldn't bring up the otel collectors), the other service are running and I can access the frontend (using kubectl port-forward) Related to: #1851 SigNoz/signoz

#1929 fix(sidebar): highlight active feature in nested route Pull request opened by jyash97 Currently if we go to a nested route like

alerts/edit

it doesnt highlight the correct menu item. New behavior Highlight the correct feature based on the sub route SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/40ec4517c27cde70f8a2436e55741ed01a411e22|40ec4517>

- fix: per page is added in the dependancy (#1926) SigNoz/signoz

#1930 Multiple API calls are being made in logs page Issue created by ankitnayan Multiple APi calls are being made in the logs page causing the chart to load data again which is not a good user experience. Places where multiple api calls are being made: • On clearing the filter • On moving across menu items in the left panel https://www.loom.com/share/7cf61a67c08d496d82fca108b3615e81 SigNoz/signoz

#1931 fix(version): use link instead of click handler Pull request opened by jyash97 Links cant be opened using

CMD + Click

and we cant right click to open in new tab. using anchor tag fixes this a11y issue SigNoz/signoz

#1932 Flickering of chart in the logs page Issue created by ankitnayan https://www.loom.com/share/7c28b1d1cfd64be0b310470ef89d2f81 SigNoz/signoz

#1933 ci(deployments): workflows for staging and testing deployments and related changes Pull request opened by prashant-shahi • docker-standalone: introduce tag environment variables for easy custom deployments • Makefile: remove no-cache from all docker build commands • Makefile: update target names •

run-x86

to

run-signoz

•

down-x86

to

down-signoz

• Makefile: introduce

pull-signoz

to pull latest image from standalone docker-compose YAML Signed-off-by: Prashant Shahi prashant@signoz.io SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/35f5fb69578dc70c896bd9fd94da902837cf5923|35f5fb69>

- fix: respect durationSort feature flag on getSpanFilters API (#1900) SigNoz/signoz

1 new commit pushed to

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

by srikanthccv

<https://github.com/SigNoz/signoz-otel-collector/commit/90d02971ed39a2abfbd2a2c368be54bcda9a7e43|90d02971>

- Add cardinality logs and exclude pattern capability (#49) SigNoz/signoz-otel-collector