#1820 fix: logs is updated Pull request opened by palashgdev on <!date^1670327996^{date_short}|2022-12-06T11:59:56Z> Paritally close #1784 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/02898d14f978ebea7099193bca6e0778b464a11d|02898d14>

- fix: removes password validations other than length (#1909) SigNoz/signoz

#1910 fix: logs selection of filter is fixed Pull request opened by palashgdev Close SigNoz/engineering-pod#925 SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/1cceab4d5e0633478a1ba6eafe2cb95c00fb9e85|1cceab4d>

- fix(FE): remove unnecessary complexity from password check (#1904) SigNoz/signoz

#1606 signup fails Issue created by tomquas Bug description http://localhost:3301/signup According to screenshot, password policies are a) a pain b) useless if not implemented correctly c) not worth a dime - as many studies and reports found out before. why not drop them? Expected behavior i can sign up / log in. How to reproduce 1. $ cd deploy/docker/clickhouse-setup 2. $ docker compose up 3. $ open http://localhost:3301/signup 4. see screenshot Version information • Signoz version: 0.11.1 (docker > create • Browser version: chrome 10x.y SigNoz/signoz

#1911 The search results do no clear when adding filter in live mode on logs Issue created by ankitnayan https://www.loom.com/share/b7a44d542dd040a4a9711fb0b5ad79ba SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/ac446294e72a8695adb9051437d7dc3bc31047d0|ac446294>

- fix: logs selection of filter is fixed (#1910) SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/d1d2829d2b92f110ec28ea118dd83b3080de94b9|d1d2829d>

- fix: logs issues (#1889) SigNoz/signoz

#1912 fix: flush logs before starting Pull request opened by palashgdev Close #1911 SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/092c02762f1f902a853a8bf7885770fa52e4f3ff|092c0276>

- feat: add no found with no events are present (#1874) SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/0595cdc7af861226f106e854680e0bb86c6b5243|0595cdc7>

- fix: scroll is added (#1873) SigNoz/signoz

#1754 Unable to see the actual span for multiple spans in traces Page Issue created by abhinavramana on <!date^1669328689^{date_short}|2022-11-24T22:24:49Z> Bug description Unable to see problematic spans in case span number exceeds a certain threshold More details: https://drive.google.com/file/d/1JVUSX9OPl32dDFYHcMQKdaOxlHPcHdw1/view?usp=share_link Expected behavior There should be a way to scroll horizontally not just vertically Or atleast be able to click on the problematic span How to reproduce Check https://drive.google.com/file/d/1JVUSX9OPl32dDFYHcMQKdaOxlHPcHdw1/view?usp=share_link SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/3dcb44a75862cc4dab238fec6eb49bb202130a0a|3dcb44a7>

- fix docker-compose for swarm and related changes for distributed clickhouse (#1863) SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/6f6499c267fbc7c340061865b7d9de80c907cda4|6f6499c2>

- fix: flush logs before starting (#1912) SigNoz/signoz

#65 Metricsexporter tests fail with panic Issue created by srikanthccv Example test run https://github.com/SigNoz/signoz-otel-collector/actions/runs/3731714139/jobs/6330251346. This should be fixed either by passing the mock or the original ClickHouse connection. SigNoz/signoz-otel-collector

#66 Grok parser custom field name concurrency issues. Issue created by nityanandagohain If we use something like

%{COMMONLOG}

to parse a log line, the benchmarks run well and there is no concurrency issue. but whenever we add our own variables like

%{DATA:podname}_%{DATA:namespace}_%{GREEDYDATA:container_name}-%{WORD:container_id}.log

, there is concurrency issue.

fatal error: concurrent map writes

goroutine 98 [running]:
runtime.throw({0x1027c9330?, 0x0?})
	/usr/local/go/src/runtime/panic.go:992 +0x50 fp=0x14000455b70 sp=0x14000455b40 pc=0x1021dc850
runtime.mapassign_faststr(0x14000119720?, 0x1027e9662?, {0x14000468018, 0x7})
	/usr/local/go/src/runtime/map_faststr.go:212 +0x3bc fp=0x14000455be0 sp=0x14000455b70 pc=0x1021ba72c
<http://github.com/vjeantet/grok.(*Grok).aliasizePatternName(...)|github.com/vjeantet/grok.(*Grok).aliasizePatternName(...)>
	/Users/nityanandagohain/go/pkg/mod/github.com/vjeantet/grok@v1.0.1/grok.go:390
<http://github.com/vjeantet/grok.(*Grok).denormalizePattern|github.com/vjeantet/grok.(*Grok).denormalizePattern>(0x14000048280, {0x1027e965b, 0x57}, 0x57?)
	/Users/nityanandagohain/go/pkg/mod/github.com/vjeantet/grok@v1.0.1/grok.go:345 +0x1ec fp=0x14000455dd0 sp=0x14000455be0 pc=0x1024c32ec
<http://github.com/vjeantet/grok.(*Grok).compile(0x14000048280|github.com/vjeantet/grok.(*Grok).compile(0x14000048280>, {0x1027e965b, 0x57})
	/Users/nityanandagohain/go/pkg/mod/github.com/vjeantet/grok@v1.0.1/grok.go:315 +0x194 fp=0x14000455e40 sp=0x14000455dd0 pc=0x1024c2f34
<http://github.com/vjeantet/grok.(*Grok).Parse(0x0|github.com/vjeantet/grok.(*Grok).Parse(0x0>?, {0x1027e965b?, 0x0?}, {0x140002d0400, 0x79})
	/Users/nityanandagohain/go/pkg/mod/github.com/vjeantet/grok@v1.0.1/grok.go:232 +0x30 fp=0x14000455e80 sp=0x14000455e40 pc=0x1024c2620
<http://github.com/SigNoz/signoz-otel-collector/pkg/parser/grok.(*Parser).match(0x14000398900|github.com/SigNoz/signoz-otel-collector/pkg/parser/grok.(*Parser).match(0x14000398900>, {0x140002d0400, 0x79})
	/Users/nityanandagohain/projects/signoz-otel-collector/signoz-otel-collector/pkg/parser/grok/grok.go:138 +0xa4 fp=0x14000455f60 sp=0x14000455e80 pc=0x1027ae0e4

someone reported this issue but closed it vjeantet/grok#33 SigNoz/signoz-otel-collector

#1913 Check if `live` mode in logs eats up memory in browser Issue created by ankitnayan Monitor the memory usage with live mode and if some anomaly is found check the breakdown of memory usage SigNoz/signoz

#67 Temporarily skip some metrics exporter tests Pull request opened by srikanthccv They should be enabled when there is a proper fix for #65. On a side note, I would like to ask if it's generally recommended/practised approach that the connection should be established in the new object instantiation with

NewXX

or when the

Start

is actually called on the exporter even outside this project, is it common? SigNoz/signoz-otel-collector

#1914 Disable Previous/Next button/Go to latest when less data than what pagination setting allows Issue created by ankitnayan Previous/Next button/Go to latest - should be disabled/ not shown when there is less number of log lines than what page limit allows https://www.loom.com/share/9cb2efe26f1c49d3bd3b26eacb81faa3 SigNoz/signoz

#1915 Update start and end timestamps in logs page on a few actions Issue created by ankitnayan Currently, the timestamps are only updated when the user hits the refresh button or auto-refresh is triggered. Ideally, the api/v1/logs? api calls should be triggered with updated timestamps except for the actions at next, previous and x/page . The same should be reflected at the last refreshed value below the datetime picker. The above is based on user expectations. SigNoz/signoz

#1916 Changing the page size in pagination in the logs page should trigger a new api call with new `limit` value Issue created by ankitnayan Currently changing the page size in the logs page does not trigger any api call and hence the number of results does not change. The change is only reflected when a new api call is made due to other actions. We should always fire a new api call when the page size is changed in the pagination with new

limit

param SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz-otel-collector/commit/a81d21b96b40f6760c090f02508046175e584d12|a81d21b9>

- Update span metrics processor (#47) SigNoz/signoz-otel-collector

#21 Sync up signozspanmetrics processor with upstream span metrics processor fixes Issue created by srikanthccv SigNoz/signoz-otel-collector

#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