* test: added few test cases for Tooltip
* fix: some of the stale frontend package are removed
* chore: flat package is removed
---------
Co-authored-by: Sanjib <sanjib.sah@yahoo.com>
* feat: flag is updated
* feat: feature flag is updated
* feat: onrefetch is added on several actions on app
* chore: tab is updated
* chore: creating dashbaord error is handled
* fix: message is fixed
* chore: jest test is updated
* fix: disabled content being copied on keyDown action
* chore: tab index and role is updated
* fix: reverted lodash changes
---------
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
* fix: add support for bool values in time series result
* chore: reserved target column can never be bool so removed obsolete code
---------
Co-authored-by: Ankit Nayan <ankit@signoz.io>
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
* fix: position of where caluse is changed for metrics
* fix: by default enabled for logs & traces
* fix: to many api call for key on search
* fix: make chip on enter for exists/nexists
* fix: flickering issue on selection of option
* fix: text change
* fix: orderby payload issue
* fix: removed replace logic
* fix: responsive qb & disabled issue
---------
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
Co-authored-by: Ankit Nayan <ankit@signoz.io>
* feat: trace to logs and logs to trace is added
* chore: icons and spanId is updated
* chore: feedback changes are updated
---------
Co-authored-by: Ankit Nayan <ankit@signoz.io>
* fix: search filter validation on data source
* fix: value search not working for in/nin
* fix: unwanted key api while searching value & disabled tag
* fix: unnecessary , at end of in/nin value
* fix: added space after operator to get value
* fix: custom value not being selected
* fix: space after tag and value
* fix: api call debounce duration
* fix: suggested changes
* fix: updated query params
* fix: search filter data for logs and traces
* fix: search filter value data type issue
* fix: search filter value tag type
* fix: chip & iscolumn issue
* fix: null handled
* fix: label in list of search filter component
* fix: label in list of search filter component
* fix: code level changes
* fix: incorrect filter operators
* fix: key selection dancing
* fix: missing suggestion
* fix: keys are not getting updated
* fix: strange behaviour - removed duplicate options
* fix: driver id exclusion not working
* fix: loader when 0 options
* fix: exists/not-exists tag value issue
* fix: some weird behaviour about exists
* fix: added duplicate option remove logic at hook level
* fix: removed empty options from list
* fix: closable chip handler on edit
* fix: search filter validation on data source
* fix: value search not working for in/nin
* fix: unwanted key api while searching value & disabled tag
* fix: unnecessary , at end of in/nin value
* fix: added space after operator to get value
* fix: custom value not being selected
* fix: space after tag and value
* fix: api call debounce duration
* fix: suggested changes
* fix: updated query params
* fix: search filter data for logs and traces
* fix: search filter value data type issue
* fix: search filter value tag type
* fix: chip & iscolumn issue
* fix: null handled
* fix: label in list of search filter component
* fix: label in list of search filter component
* fix: code level changes
* fix: incorrect filter operators
* fix: key selection dancing
* fix: missing suggestion
* fix: keys are not getting updated
* fix: strange behaviour - removed duplicate options
* fix: driver id exclusion not working
* fix: loader when 0 options
* fix: exists/not-exists tag value issue
* fix: some weird behaviour about exists
* fix: added duplicate option remove logic at hook level
* fix: removed empty options from list
* fix: closable chip handler on edit
* fix: search filter validation on data source
* fix: lint issues is fixed
* fix: chip & iscolumn issue
* fix: lint changes are updated
* fix: undefined case handled
* fix: undefined case handled
* fix: removed settimeout
* fix: delete chip getting value undefined
* fix: payload correctness
* fix: incorrect value selection
* fix: key text typing doesn't change anything
* fix: search value issue
* fix: payload updated
* fix: auto populate value issue
* fix: payload updated & populate values
* fix: split value for in/nin
* fix: split value getting undefined
* fix: new version of search filter using papaparse library
* fix: removed unwanted space before operator
* fix: added exact find method & removed includes logic
* fix: issue when user create chip for exists not exists operator
* fix: white space logic removed
* fix: allow custom key in from list
* fix: issue when user create chip for exists not exists operator
* fix: removed unwanted includes
* fix: removed unwanted utils function
* fix: replaced join with papa unparse
* fix: removed get count of space utils
* fix: resolved build issue
* fix: code level fixes
* fix: space after key
* fix: quote a value if comma present
* fix: handle custom key object onchange
* chore: coverted into string
* Merge branch 'develop' into fix/issue-search-filter
* chore: eslint rule disabling is removed
* fix: serviceName contains sql
* chore: less restrictive expression
* fix: custom key selection issue
* chore: papa parse version is made exact
---------
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
* fix: having value data type
* feat: connect new builder to dashboard
* Fix/query builder filters (#2623)
* feat: rename query data type
* fix: remove reset of groupBy
* fix: filters search
* fix: calls autocomplete times
* fix: response mapper
* fix: removee unnecessary field
* fix: no check ts types for old query builder
* fix: disable check utils old builder
* feat: add query builder to the alerts
* fix: alert response integration with query builder
* fix: validation of query builder rules
* fix: rules query builder
* fix: filter value with similar keys
* fix: null values for options
* fix: query builder disabled when exist formula
* fix: removing filter key with underscore
* feat: add builder data to metric application (#2665)
* feat: add builder data to metric application
* fix: query types to single variant
* fix: formula legend formatting
* fix: argumant name
* fix: date for graph
---------
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
* fix: pipeline
---------
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
* fix: having value data type
* feat: connect new builder to dashboard
* Fix/query builder filters (#2623)
* feat: rename query data type
* fix: remove reset of groupBy
* fix: filters search
* fix: calls autocomplete times
* fix: response mapper
* fix: removee unnecessary field
* fix: no check ts types for old query builder
* fix: disable check utils old builder
* fix: removing key from groupby is not updating value of orderby
* fix: removing operator is not updating value of orderby
---------
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
* fix: clear filter is fixed
* chore: action bar empty query condition is handled
* feat: local state is clear for filters
(cherry picked from commit 6c11c6d4da)
Signed-off-by: Prashant Shahi <prashant@signoz.io>
* chore: add payload types for autocomplete requests
* chore: update the query params file location and payload
* chore: add query range v3 API request/response payload types
* feat: metric attribute autocomplete for the aggregation type
* feat: add attrs filters autocomplete endpoints
* feat(logs): add tag attribute autocomplete for logs
* chore: added support for multiple datatype in value suggestion api for attributes
* feat: int64/float64 added for AttributeKeyDataType along with validation
* feat: filterAttributeValueResponse type updated
* fix: number type updated and query updated
* feat: remove tagType in keys autocomplete
* feat: return isColumn value correctly for attibute keys
* Update pkg/query-service/app/clickhouseReader/reader.go
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
* fix: don't skip empty strings in value autocomplete
* fix: allow empty string search
* feat: add top level column names of logs in key sugestion
* fix: tagType column removed
* feat: get attribute values from logs table for top level fields
* feat: don't throw error if dataType and tagType is not present
* feat: timerange select corrected
* feat: autocomplete for int/float added
* fix: reverted attributeValueResponse change
* fix: null values handled for int and float
* feat: add support for get log aggreagte attributes
* feat: aggreate attribute logic updated and body added in keys autocomplete
* fix: constants updaetd
* fix: body type updated and empty response for noop and count
* fix: isColumn logic updated
---------
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
Co-authored-by: Vishal Sharma <makeavish786@gmail.com>
Co-authored-by: palashgdev <palashgdev@gmail.com>
* feat: resource attribute is added in the exception
* fix: build is fixed
* chore: methods is updated to post
* fix: build is fixed
* fix: listErrors, countErrors API request body
* chore: type of the function is updated
* chore: convertRawQueriesToTraceSelectedTags is updated
* fix: resource attribute is updated
* chore: selected tags is updated
* feat: key is updated
---------
Co-authored-by: Vishal Sharma <makeavish786@gmail.com>
* feat: add span links support
* fix: handle an edge case
* chore: test is fixed
* chore: some of the refactoring is updated
---------
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
* logs is updated
* fix: log live tail is updated
* fix: live tail is fixed
* chore: build is fixed
* chore: useEffect is removed
* chore: getLogsAggregate callback is added in the useEffect
* style: corrected the positioning of the charts tooltip
* style: stored value for pixel in variable
* chore: logic is shifted to plugin
---------
Co-authored-by: palashgdev <palashgdev@gmail.com>
* feat: multiple values can be selected
* chore: tag value is updated
* fix: handle few edge cases
---------
Co-authored-by: makeavish <makeavish786@gmail.com>
* feat: add list and table views for logs
* chore: some of the changes are updated
* chore: some of the refactoring is done
* chore: px to updated to rem
* chore: constant is moved to local storage
* refactor: some of the refactoring is updated
* chore: some of the changes are updated
* fix: resize log table issue
* chore: logs is updated
* chore: resize header is updated
* chore: font observer is added in package json and hook is added for same
* chore: no logs text is updated
* chore: no logs text is updated
* chore: updated some feedback in raw logs line
* chore: types is added
---------
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
Co-authored-by: Pranay Prateek <pranay@signoz.io>
Co-authored-by: Vishal Sharma <makeavish786@gmail.com>
Co-authored-by: Chintan Sudani <csudani7@gmail.com>
* fix: it has been fixed of difficult to click on metrics graph points
* fix: resolve conflict
* fix: changed hover point & memoized the passed props
* fix: memo from develop
* fix: add condition for end and start stamps
* chore: type position is updated
---------
Co-authored-by: palashgdev <palashgdev@gmail.com>
* feat(query-service): ✨ Add health check route and handler
* chore(install-script): 🔧 use health endpoint with instead of services list
---------
Signed-off-by: Prashant Shahi <prashant@signoz.io>
* create a visual loading state with header
* updates loading with WidgetHeader component
* chore: onview and ondelete is updated
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
* fix: query builder formula fails to eval
* fix: result label set without reference
* chore: update tests
Co-authored-by: Prashant Shahi <prashant@signoz.io>
* feat: v5 is in progress
* feat: antdv5 is updated
* fix: build is fixed
* fix: default config is over written by custom one
* chore: onchange handler is updated
* chore: overflow is hidden in the layout
* Update index.tsx
* fix: import is fixed
* chore: un used import is fixed
* fix: dark mode is updated in service map
* fix: config dropdown is updated
* fix: logs types is updated
* fix: copy clipboard notification is updated
* chore: layout changes are updated
* chore: colors is updated
* chore: action width is updated
Co-authored-by: Pranay Prateek <pranay@signoz.io>
Co-authored-by: Vishal Sharma <makeavish786@gmail.com>
* feat: v5 is in progress
* feat: antdv5 is updated
* fix: build is fixed
* fix: default config is over written by custom one
* chore: onchange handler is updated
* chore: overflow is hidden in the layout
* feat: react is updated from v17 to v18
* feat: antdv5 is updated (#1880)
* feat: v5 is in progress
* feat: antdv5 is updated
* fix: build is fixed
* fix: default config is over written by custom one
* chore: onchange handler is updated
* chore: overflow is hidden in the layout
* Update index.tsx
* fix: import is fixed
* chore: un used import is fixed
* fix: dark mode is updated in service map
* fix: config dropdown is updated
* fix: logs types is updated
* fix: copy clipboard notification is updated
Co-authored-by: Pranay Prateek <pranay@signoz.io>
* chore: all channel is updated move from usefetch to usequery
* fix: typescript is fixed
Co-authored-by: Pranay Prateek <pranay@signoz.io>
Co-authored-by: Ankit Nayan <ankit@signoz.io>
* add commands to install sqlite3 in Makefile.
* Add code to check if it's running on Linux System.
* Revert "Add code to check if its running on Linux"
This reverts commit 552cfb08c9.
* Revert "add commands to install sqlite3 in Makefi"
This reverts commit 781c23d12d.
* Add Docuentation to install SQLite3.
Co-authored-by: Pranay Prateek <pranay@signoz.io>
Co-authored-by: Vishal Sharma <makeavish786@gmail.com>
Co-authored-by: Prashant Shahi <prashant@signoz.io>
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
* feat: v5 is in progress
* feat: antdv5 is updated
* fix: build is fixed
* fix: default config is over written by custom one
* chore: onchange handler is updated
* chore: overflow is hidden in the layout
* Update index.tsx
* fix: import is fixed
* chore: un used import is fixed
* fix: dark mode is updated in service map
* fix: config dropdown is updated
* fix: logs types is updated
* fix: copy clipboard notification is updated
Co-authored-by: Pranay Prateek <pranay@signoz.io>
* fix: reduced rate limit to 2 of each events in 1 min
* feat: added new event for length of filters in logs search page
* feat: added distributed cluster info
* fix: length of filters in logs
* feat: dashboard metadata with no rateLimit
* feat: active user
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
* fix: live tail time out is updated
* Update livetail.ts
Co-authored-by: Pranay Prateek <pranay@signoz.io>
Co-authored-by: Ankit Nayan <ankit@signoz.io>
* fix: allow multiple spaces between a filter expression
* fix: regex updated to respect spaces between a search string
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
* Fix case sensitivity in query parsing - now the parser correctly recognize fields which contains uppercase letters
* fix: logs parser respects the case of fields
Co-authored-by: nityanandagohain <nityanandagohain@gmail.com>
Co-authored-by: Pranay Prateek <pranay@signoz.io>
Co-authored-by: Ankit Nayan <ankit@signoz.io>
* chore: introduce docker_multi_node_cluster and by default set to false
* chore(query-service): 🔧 include docker_multi_node_cluster for tests
Co-authored-by: Prashant Shahi <prashant@signoz.io>
Co-authored-by: Prashant Shahi <me@prashantshahi.dev>
Co-authored-by: Ankit Nayan <ankit@signoz.io>
* fix: remove shared variable in TTL
* fix: set distributed_ddl_task_timeout to 0 for async TTL
* chore: updated distributed_ddl_task_timeout to sync TTL queries
* feat: usage collection updated with new schema and logic
* fix: added exporter id and common collector id
* fix: upload usage only when license is present
* fix: handle if db doesn't exists
* fix: select query updated for usage collection to support distributed table
Co-authored-by: Pranay Prateek <pranay@signoz.io>
Co-authored-by: Vishal Sharma <makeavish786@gmail.com>
Co-authored-by: Ankit Nayan <ankit@signoz.io>
* [feat] initial version for google oauth
* chore: arranged the sso packages and added prepare request for google auth
* feat: added google auth config page and backend to handle the request
* chore: code cleanup for domain SSO parsing
* Update constants.go
* chore: moved redirect sso error
* chore: lint issue fixed with domain
* chore: added tooltip for enforce sso and few changes to auth domain
* chore: moved question mark in enforce sso
* fix: resolved pr review comments
* chore: fixed type check for saml config
* fix: fixed saml config form
* chore: added util for transformed form values to samlconfig
Co-authored-by: mindhash <mindhash@mindhashs-MacBook-Pro.local>
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
Co-authored-by: Ankit Nayan <ankit@signoz.io>
* fix: live tail is fixed
* fix: graph state is updated
* chore: step size is updated
* chore: xaxis config is updated
* chore: isDisabled state is updated for top navigation
* chore: selected interval is updated in the reducer
* fix: build is fixed
* chore: xAxis config is updated
Co-authored-by: Pranay Prateek <pranay@signoz.io>
Co-authored-by: Ankit Nayan <ankit@signoz.io>
* fix: [alerts] [ch-query] added aliases in metric query result
* fix: added more column type support for target in ch query
* fix: added error handling when data type is unexpected in metric result
Co-authored-by: Pranay Prateek <pranay@signoz.io>
* feat: added ui changes to support clickhouse queries in alert builder
* chore: minor fix to alert rules ui
* feat: alert form changes: ch query support, alert type selection
* chore: resolved review comments
* chore: added list for alert type selection instead
* chore: removed hard coded color and added antd/colors
* fix: resolved some issues found during testing alerts
* fix: moved alert defaults and added default queries for logs and traces
* feat: added default queries for logs and traces to reflect ts vars
* chore: fixed px to rem
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
Co-authored-by: Pranay Prateek <pranay@signoz.io>
* feat: added ch query support
* fix: added new vars to resolve alert query format issue
* fix: replaced timestamp vars in metric query range
Co-authored-by: Pranay Prateek <pranay@signoz.io>
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
* feat: logs is updated
* chore: width:100% is removed
* chore: position of filter is updated
* chore: min time and max time are now tracked from global state
Co-authored-by: Pranay Prateek <pranay@signoz.io>
* chore: 🔥 remove docker-compose-prod.yaml as redundant and update Makefile
* chore: 🔧 scrape otel-collector internal metrics in same container and related changes
* chore: 📌 Bump version of clickhouse to 22.8.8 LTS
Signed-off-by: Prashant Shahi <prashant@signoz.io>
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
* feat: integrate config service with query service
* feat: add tooltip checkpoint
* feat: add support for dark and light mode icons
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
* chore: update the import from constant rather than static string
* chore: removed redundant div
* feat: added auto refresh component
* refactor: top nav is refactored
* externaltab-promql-to-querybuilder
* refactored the queries into separate file
* added logic for resourceattribute to tagFilter items conversion
* refactor: use useMemo
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
* feat: show messaging/cron/browser services in listing page
* chore: issue maximum of ten queries to clickhouse
Co-authored-by: Palash Gupta <palashgdev@gmail.com>
* feat: added patch rule api
* feat: added backend api for patching rule status
* fix: improved patchRule and also editRule
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
* feat: added rule url to the title link in slack message
* fix: corrected duplication of code for generator url in rules engine
* fix: removed unnecessary import in rules engine
* feat: metrics builder
* feat: tag key selection
* feat: metrics builder
* poc version
* added more changes to query builder
* added types for composite queries
* (feat): added edit rules and create rules forms
* added label key value input item
* (chore): added hidden labels for labelinput
* (chore): resolved some merge conflicts from develop
* (chore): added translations
* (chore): removed some old files in metric builder
* (chore): restored some of the files from develop branch
* (chore): restored env.ts
* (fix): solved empty builder queries errors
* (fix): changed queryIndex and formulaIndex type to string|number from number
* (feat): added chart preview for alert metric ui
* (feat): added threshold in chart, translations in alert form and a few fixes
* (fix): restoring env.ts
* (fix): placed threshold on horizontal line
* fix: resolved review comments
* fix: resolved label remove issue
* fix: removed console log
* fix: resolved issue with edit rule - old state values shown after update of threshold
* fix: resolved issue with match condition dropdown in alert ui
* fix: increased size of timeframe drop down
* fix: fixed label key value field and chart auto update when eval window changes
* feat: added a link for alert name in list alerts page and source for each rule update
* fix: resolved review coments in querysection of alerts ui
* feat: adding panel user guide in alerting form
* feat: added user guide panel in the alert form
* feat: added more help icon in user guide and fixed the sizing issue
Co-authored-by: Pranshu Chittora <pranshu@signoz.io>
* fix: remove requirement of exceptionType and serviceName from errorDetail page URL
* chore: id is updated
* chore: commented code is removed
* chore: eslint error is fixed
Co-authored-by: Palash <palashgdev@gmail.com>
* chore: 🔧 otel-collector config changes
* chore: 🗑️ remove redundant users.xml
* chore: 🔧 otel-config changes
- seperate scraper job for otel-collector and otel-collector-metrcs internal metrics
- use resourcedetection only for hostmetrics
- add swarm service name and task name in resource attributes env
Signed-off-by: Prashant Shahi <prashant@signoz.io>
* added more changes to query builder
* added types for composite queries
* (feat): added edit rules and create rules forms
* (feat): added chart preview for alert metric ui
* (feat): added threshold in chart, translations in alert form and a few fixes
* feat: added a link for alert name in list alerts page and source for each rule update
Co-authored-by: Pranshu Chittora <pranshu@signoz.io>
* test: sign-up test are updated
* test: fail test of version api is added
* test: more test case over signup page is added
* test: coverage is added
* chore: auth json is updated
* test: auth token and refresh token test is updated
* feat: update ListErrors API
* feat: update error detail APIs and add a new API for fetching next prev error IDs
* feat: update GetNextPrevErrorIDs API to handle an edge case
* perf: use timestamp for fetching individual column
* feat: add countErrors API
* Queryrange params tests
* review suggestions, quantile, simple metric filter and some refactoring
* Add value type support
* Add supprot for re2 regex, refactor, update tests and other changes
* chore: update govaluate dep to signoz/govaluate
* chore: add name to grouping
* chore: add support for NOOP
* fix: make result format compatible with prom HTTP API
* chore: update clickhouse server and update query builder to use new schema
* chore: use metric_name in auto suggest APIs
* chore: add reduce operator and new aggregate functions
* chore: add support for not like op
* chore: fix the dip at the end for incomplete time range
* chore: rounddown the end to exclude the incomplete collection
* feat: dashboard layout is updated
* feat: onClick is made fixed
* feat: layout is updated
* feat: layout is updated
* feat: layout is updated
* fix: memo is removed and grid layout component is refactored to use use query
* fix: saveDashboard is updated
* feat: layout is fixed
* fix: tsc error are fixed
* fix: delete widgets is updated
* fix: useMount once is added
* fix: useMount once is removed
* chore: removed the commented code
Co-authored-by: Ankit Nayan <ankit@signoz.io>
*feat: Update query-service Go version to 1.17 #911
*chore: Upgrade to clickhouse versions v2 #751
*feat: Duration sorting in events table of Trace-filter page #826
*feat: Add grpc status code to traces view #975
*feat: added filtering by resource attributes #881
* feat: new dashboard widget's option selection
* fix: overflowing legend
* feat: delete menu item is of type danger
* feat: added keyboard events onFocus and onBlur
* feat: useFetch in tag value is removed and moved to use query
* feat: useFetch in all channels is removed and moved to use query
* feat: useFetch in edit rule is removed and moved to use query
* feat: useFetch in general settings is removed and moved to use query
* feat: useFetch in all alerts is changed into use query
- set information log level in clickhouse logger config
- maximum logs size 150m (3 files each of 50m)
Signed-off-by: Prashant Shahi <prashant@signoz.io>
* feat👔 : getLatestVersion api is added
* chore: VERSION page is added
* feat: ✨ version page is added
* chore: all string is grabbed from locale
* chore: warning is removed
* chore: translation json is added
* chore: feedback about version is added
* chore: made two different functions
* unused import is removed
* feat: version changes are updated
* chore: if current version is present then it is displayed
* feat: dynamic step size for the data for graphs
* fix: remove console.log
* chore: add jest globals
* feat: add step size for dashboard
* chore: undo .eslintignore
* order is added in the url
* local min max duration is kept in memory to show min and max even after filtering by duration
* checkbox ordering does not change when the user selects or un-selects a checkbox
* (fix): Duplicate alerts in triggered alerts fixed by changing source api from /alert/groups to /alerts
* (fix): added comments for removed lines of group api call
* (fix): restored all getGroup
* chore: eslint is updated
* chore: some eslint fixes are made
* chore: some more eslint fix are updated
* chore: some eslint fix is made
* chore: styled components type is added
* chore: some more eslint fix are made
* chore: some more eslint fix are updated
* chore: some more eslint fix are updated
* fix: eslint fixes
Co-authored-by: Pranshu Chittora <pranshu@signoz.io>
* chore: 🔧 set dimensions_cache_size in signozspanmetrics processor
- add example usage of limit_percentage and spike_limit_percentage
Signed-off-by: Prashant Shahi <prashant@signoz.io>
* bug: useHistory is removed and dashboard loading component is removed
* chore: new dashboard is updated
* chore: new dashboard is updated
* chore: sidenav is updated
* chore: getX console is removed
* chore: sidenav is updated with correct pathname
* feat: data time and graph label consistency across FE
* feat: saved state of sidebar and horizontal scroll fix for trace filter page
* feat: add Y-Axis unit for missing metrics graphs
* chore: update node version from 12.18 to 12.22
* fix: 24hr time unit on graph
* Initial work on s3
* some more work
* Add policy api
* Cleanup
* Add multi-tier TTL and remove storagePolicy API
* Cleanup
* Typo fix
* Revert constants
* Cleanup
* Add API to get disks
* Add more validations
* Initial work on e2e tests
* Basic ttl test
* Add test which checks for objects in Minio
* Address comments
Co-authored-by: Ankit Nayan <ankit@signoz.io>
* Initial work on s3
* some more work
* Add policy api
* Cleanup
* Add multi-tier TTL and remove storagePolicy API
* Cleanup
* Typo fix
* Revert constants
* Cleanup
* Add API to get disks
* Add more validations
* Cleanup
* fix: save layout bug is resolved
* chore: onClick is also added in the component slider
* chore: dashboard Id is added
* chore: non dashboard widget is filtered out
* chore: panel layout stack issue is resolved
# This Action will scan dependency manifest files that change as part of a Pull Request, surfacing known-vulnerable versions of the packages declared or updated in the PR. Once installed, if the workflow run is marked as required, PRs introducing known-vulnerable packages will be blocked from merging.
# Public documentation: https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement
There are primarily 2 areas in which you can contribute in SigNoz
## Welcome to SigNoz Contributing section 🎉
- Frontend ( written in Typescript, React)
- Backend - ( Query Service - written in Go)
Hi there! We're thrilled that you'd like to contribute to this project, thank you for your interest. Whether it's a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.
Depending upon your area of expertise & interest, you can chose one or more to contribute. Below are detailed instructions to contribute in each area
Please read through this document before submitting any issues or pull requests to ensure we have all the necessary information to effectively respond to your bug report or contribution.
> Please note: If you want to work on an issue, please ask the maintainers to assign the issue to you before starting work on it. This would help us understand who is working on an issue and prevent duplicate work. 🙏🏻
- We accept contributions made to the [SigNoz `develop` branch]()
> If you just raise a PR, without the corresponding issue being assigned to you - it may not be accepted.
## Finding contributions to work on 💬
# Develop Frontend
Looking at the existing issues is a great way to find something to contribute on.
Also, have a look at these [good first issues label](https://github.com/SigNoz/signoz/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) to start with.
Need to update [https://github.com/SigNoz/signoz/tree/main/frontend](https://github.com/SigNoz/signoz/tree/main/frontend)
### Contribute to Frontend with Docker installation of SigNoz
- [How to Contribute](#2-how-to-contribute-%EF%B8%8F)
- [Develop Frontend](#3-develop-frontend-)
- [Contribute to Frontend with Docker installation of SigNoz](#31-contribute-to-frontend-with-docker-installation-of-signoz)
- [Contribute to Frontend without installing SigNoz backend](#32-contribute-to-frontend-without-installing-signoz-backend)
- [Contribute to Backend (Query-Service)](#4-contribute-to-backend-query-service-)
- [To run ClickHouse setup](#41-to-run-clickhouse-setup-recommended-for-local-development)
- [Contribute to SigNoz Helm Chart](#5-contribute-to-signoz-helm-chart-)
- [To run helm chart for local development](#51-to-run-helm-chart-for-local-development)
- [Other Ways to Contribute](#other-ways-to-contribute)
-`git clone https://github.com/SigNoz/signoz.git && cd signoz`
- comment out frontend service section at `deploy/docker/clickhouse-setup/docker-compose.yaml#L59`
- run `cd deploy` to move to deploy directory
- Install signoz locally without the frontend
- If you are using x86_64 processors (All Intel/AMD processors) run `sudo docker-compose -f docker/clickhouse-setup/docker-compose.yaml up -d`
- If you are on arm64 processors (Apple M1 Macbooks) run `sudo docker-compose -f docker/clickhouse-setup/docker-compose.arm.yaml up -d`
-`cd ../frontend` and change baseURL to `http://localhost:8080` in file `src/constants/env.ts`
-`yarn install`
-`yarn dev`
# 1. General Instructions 📝
> Notes for Maintainers/Contributors who will change Line Numbers of Frontend & Query-Section. Please Update Line Numbers in `./scripts/commentLinesForSetup.sh`
## 1.1 For Creating Issue(s)
Before making any significant changes and before filing a new issue, please check [existing open](https://github.com/SigNoz/signoz/issues?q=is%3Aopen+is%3Aissue), or [recently closed](https://github.com/SigNoz/signoz/issues?q=is%3Aissue+is%3Aclosed) issues to make sure somebody else hasn't already reported the issue. Please try to include as much information as you can.
### Contribute to Frontend without installing SigNoz backend
If you don't want to install SigNoz backend just for doing frontend development, we can provide you with test environments which you can use as the backend. Please ping us in #contributing channel in our [slack community](https://signoz.io/slack) and we will DM you with `<test environment URL>`
#### Details like these are incredibly useful:
-`git clone https://github.com/SigNoz/signoz.git && cd signoz/frontend`
-Create a file `.env` with `FRONTEND_API_ENDPOINT=<test environment URL>`
-`yarn install`
-`yarn dev`
-**Requirement** - what kind of use case are you trying to solve?
-**Proposal** - what do you suggest to solve the problem or improve the existing
situation?
-Any open questions to address❓
**_Frontend should now be accessible at `http://localhost:3301/application`_**
#### If you are reporting a bug, details like these are incredibly useful:
# Contribute to Query-Service
- A reproducible test case or series of steps.
- The version of our code being used.
- Any modifications you've made relevant to the bug🐞.
- Anything unusual about your environment or deployment.
Need to update [https://github.com/SigNoz/signoz/tree/main/pkg/query-service](https://github.com/SigNoz/signoz/tree/main/pkg/query-service)
Discussing your proposed changes ahead of time will make the contribution
process smooth for everyone 🙌.
### To run ClickHouse setup (recommended for local development)
**[`^top^`](#)**
<hr>
- git clone https://github.com/SigNoz/signoz.git
- run `sudo make dev-setup` to configure local setup to run query-service
- comment out frontend service section at `docker/clickhouse-setup/docker-compose.yaml#L59`
- comment out query-service section at `docker/clickhouse-setup/docker-compose.yaml#L38`
- Install signoz locally without the frontend and query-service
- If you are using x86_64 processors (All Intel/AMD processors) run `sudo make run-x86`
- If you are on arm64 processors (Apple M1 Macbooks) run `sudo make run-arm`
## 1.2 For Pull Request(s)
> Notes for Maintainers/Contributors who will change Line Numbers of Frontend & Query-Section. Please Update Line Numbers in `./scripts/commentLinesForSetup.sh`
Contributions via pull requests are much appreciated. Once the approach is agreed upon ✅, make your changes and open a Pull Request(s).
Before sending us a pull request, please ensure that,
**_Query Service should now be available at `http://localhost:8080`_**
- Fork the SigNoz repo on GitHub, clone it on your machine.
- Create a branch with your changes.
- You are working against the latest source on the `develop` branch.
- Modify the source; please focus only on the specific change you are contributing.
- Ensure local tests pass.
- Commit to your fork using clear commit messages.
- Send us a pull request, answering any default questions in the pull request interface.
- Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation
- Once you've pushed your commits to GitHub, make sure that your branch can be auto-merged (there are no merge conflicts). If not, on your computer, merge main into your branch, resolve any merge conflicts, make sure everything still runs correctly and passes all the tests, and then push up those changes.
- Once the change has been approved and merged, we will inform you in a comment.
> If you want to see how, frontend plays with query service, you can run frontend also in you local env with the baseURL changed to `http://localhost:8080` in file `src/constants/env.ts` as the query-service is now running at port `8080`
---
Instead of configuring a local setup, you can also use [Gitpod](https://www.gitpod.io/), a VSCode-based Web IDE.
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
**Note:** Unless your change is small, **please** consider submitting different Pull Rrequest(s):
* 1️⃣ First PR should include the overall structure of the new component:
* Readme, configuration, interfaces or base classes, etc...
* This PR is usually trivial to review, so the size limit does not apply to
it.
* 2️⃣ Second PR should include the concrete implementation of the component. If the
size of this PR is larger than the recommended size, consider **splitting** ⚔️ it into
multiple PRs.
* If there are multiple sub-component then ideally each one should be implemented as
a **separate** pull request.
* Last PR should include changes to **any user-facing documentation.** And should include
end-to-end tests if applicable. The component must be enabled
only after sufficient testing, and there is enough confidence in the
stability and quality of the component.
You can always reach out to `ankit@signoz.io` to understand more about the repo and product. We are very responsive over email and [SLACK](https://signoz.io/slack).
### Pointers:
- If you find any **bugs** → please create an [**issue.**](https://github.com/SigNoz/signoz/issues/new?assignees=&labels=&template=bug_report.md&title=)
- If you find anything **missing** in documentation → you can create an issue with the label **`documentation`**.
- If you want to build any **new feature** → please create an [issue with the label **`enhancement`**.](https://github.com/SigNoz/signoz/issues/new?assignees=&labels=&template=feature_request.md&title=)
- If you want to **discuss** something about the product, start a new [**discussion**.](https://github.com/SigNoz/signoz/discussions)
<hr>
### Conventions to follow when submitting Commits and Pull Request(s).
We try to follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/), more specifically the commits and PRs **should have type specifiers** prefixed in the name. [This](https://www.conventionalcommits.org/en/v1.0.0/#specification) should give you a better idea.
e.g. If you are submitting a fix for an issue in frontend, the PR name should be prefixed with **`fix(FE):`**
- Follow [GitHub Flow](https://guides.github.com/introduction/flow/) guidelines for your contribution flows.
- Feel free to ping us on [`#contributing`](https://signoz-community.slack.com/archives/C01LWQ8KS7M) or [`#contributing-frontend`](https://signoz-community.slack.com/archives/C027134DM8B) on our slack community if you need any help on this :)
**[`^top^`](#)**
<hr>
# 2. How to Contribute 🙋🏻♂️
#### There are primarily 2 areas in which you can contribute to SigNoz
- [**Frontend**](#3-develop-frontend-) (Written in Typescript, React)
- [**Backend**](#4-contribute-to-backend-query-service-) (Query Service, written in Go)
Depending upon your area of expertise & interest, you can choose one or more to contribute. Below are detailed instructions to contribute in each area.
**Please note:** If you want to work on an issue, please ask the maintainers to assign the issue to you before starting work on it. This would help us understand who is working on an issue and prevent duplicate work. 🙏🏻
⚠️ If you just raise a PR, without the corresponding issue being assigned to you - it may not be accepted.
**[`^top^`](#)**
<hr>
# 3. Develop Frontend 🌚
**Need to Update: [https://github.com/SigNoz/signoz/tree/develop/frontend](https://github.com/SigNoz/signoz/tree/develop/frontend)**
Also, have a look at [Frontend README.md](https://github.com/SigNoz/signoz/blob/develop/frontend/README.md) sections for more info on how to setup SigNoz frontend locally (with and without Docker).
## 3.1 Contribute to Frontend with Docker installation of SigNoz
- Clone the SigNoz repository and cd into signoz directory,
```
git clone https://github.com/SigNoz/signoz.git && cd signoz
```
- Comment out `frontend` service section at [`deploy/docker/clickhouse-setup/docker-compose.yaml#L68`](https://github.com/SigNoz/signoz/blob/develop/deploy/docker/clickhouse-setup/docker-compose.yaml#L68)
- Install signoz locally **without** the frontend,
- Add / Uncomment the below configuration to query-service section at [`deploy/docker/clickhouse-setup/docker-compose.yaml#L47`](https://github.com/SigNoz/signoz/blob/develop/deploy/docker/clickhouse-setup/docker-compose.yaml#L47)
sudo docker-compose -f docker/clickhouse-setup/docker-compose.yaml up -d
```
- `cd ../frontend` and change baseURL in file [`frontend/src/constants/env.ts#L2`](https://github.com/SigNoz/signoz/blob/develop/frontend/src/constants/env.ts#L2) and for that, you need to create a `.env` file in the `frontend` directory with the following environment variable (`FRONTEND_API_ENDPOINT`) matching your configuration.
If you have backend api exposed via frontend nginx:
```
FRONTEND_API_ENDPOINT=http://localhost:3301
```
If not:
```
FRONTEND_API_ENDPOINT=http://localhost:8080
```
- Next,
```
yarn install
yarn dev
```
### Important Notes:
The Maintainers / Contributors who will change Line Numbers of `Frontend` & `Query-Section`, please update line numbers in [`/.scripts/commentLinesForSetup.sh`](https://github.com/SigNoz/signoz/blob/develop/.scripts/commentLinesForSetup.sh)
**[`^top^`](#)**
## 3.2 Contribute to Frontend without installing SigNoz backend
If you don't want to install the SigNoz backend just for doing frontend development, we can provide you with test environments that you can use as the backend.
- Clone the SigNoz repository and cd into signoz/frontend directory,
```
git clone https://github.com/SigNoz/signoz.git && cd signoz/frontend
````
- Create a file `.env` in the `frontend` directory with `FRONTEND_API_ENDPOINT=<testenvironmentURL>`
- Next,
```
yarn install
yarn dev
```
Please ping us in the [`#contributing`](https://signoz-community.slack.com/archives/C01LWQ8KS7M) channel or ask `@Prashant Shahi` in our [Slack Community](https://signoz.io/slack) and we will DM you with `<testenvironmentURL>`.
**Frontend should now be accessible at** [`http://localhost:3301/services`](http://localhost:3301/services)
**[`^top^`](#)**
<hr>
# 4. Contribute to Backend (Query-Service) 🌑
**Need to Update: [https://github.com/SigNoz/signoz/tree/develop/pkg/query-service](https://github.com/SigNoz/signoz/tree/develop/pkg/query-service)**
## 4.1 Prerequisites
### 4.1.1 Install SQLite3
- Run `sqlite3` command to check if you already have SQLite3 installed on your machine.
- If not installed already, Install using below command
- on Linux
- on Debian / Ubuntu
```
sudo apt install sqlite3
```
- on CentOS / Fedora / RedHat
```
sudo yum install sqlite3
```
## 4.2 To run ClickHouse setup (recommended for local development)
- Clone the SigNoz repository and cd into signoz directory,
```
git clone https://github.com/SigNoz/signoz.git && cd signoz
```
- run `sudo make dev-setup` to configure local setup to run query-service,
- Comment out `frontend` service section at [`deploy/docker/clickhouse-setup/docker-compose.yaml#L68`](https://github.com/SigNoz/signoz/blob/develop/deploy/docker/clickhouse-setup/docker-compose.yaml#L68)
- Comment out `query-service` section at [`deploy/docker/clickhouse-setup/docker-compose.yaml#L41`,](https://github.com/SigNoz/signoz/blob/develop/deploy/docker/clickhouse-setup/docker-compose.yaml#L41)
<img width="1068" alt="Screenshot 2022-07-14 at 22 48 07" src="https://user-images.githubusercontent.com/52788043/179044151-a65ba571-db0b-4a16-b64b-ca3fadcf3af0.png">
- add below configuration to `clickhouse` section at [`deploy/docker/clickhouse-setup/docker-compose.yaml`,](https://github.com/SigNoz/signoz/blob/develop/deploy/docker/clickhouse-setup/docker-compose.yaml)
```
ports:
- 9001:9000
```
<img width="1013" alt="Screenshot 2022-07-14 at 22 50 37" src="https://user-images.githubusercontent.com/52788043/179044544-a293d3bc-4c4f-49ea-a276-505a381de67d.png">
- run `cd pkg/query-service/` to move to `query-service` directory,
- Then, you need to create a `.env` file with the following environment variable
```
SIGNOZ_LOCAL_DB_PATH="./signoz.db"
```
to set your local environment with the right `RELATIONAL_DATASOURCE_PATH` as mentioned in [`./constants/constants.go#L38`,](https://github.com/SigNoz/signoz/blob/develop/pkg/query-service/constants/constants.go#L38)
- Now, install SigNoz locally **without** the `frontend` and `query-service`,
- If you are using `x86_64` processors (All Intel/AMD processors) run `sudo make run-x86`
- If you are on `arm64` processors (Apple M1 Macs) run `sudo make run-arm`
#### Run locally,
```
ClickHouseUrl=tcp://localhost:9001 STORAGE=clickhouse go run main.go
The docker images of query-service is available at https://hub.docker.com/r/signoz/query-service
```
docker pull signoz/query-service
```
```
docker pull signoz/query-service:latest
```
```
docker pull signoz/query-service:develop
```
### Important Note:
The Maintainers / Contributors who will change Line Numbers of `Frontend` & `Query-Section`, please update line numbers in [`/.scripts/commentLinesForSetup.sh`](https://github.com/SigNoz/signoz/blob/develop/.scripts/commentLinesForSetup.sh)
**Query Service should now be available at** [`http://localhost:8080`](http://localhost:8080)
If you want to see how the frontend plays with query service, you can run the frontend also in your local env with the baseURL changed to `http://localhost:8080` in file [`frontend/src/constants/env.ts`](https://github.com/SigNoz/signoz/blob/develop/frontend/src/constants/env.ts) as the `query-service` is now running at port `8080`.
<!-- Instead of configuring a local setup, you can also use [Gitpod](https://www.gitpod.io/), a VSCode-based Web IDE.
Click the button below. A workspace with all required environments will be created.
[](https://gitpod.io/#https://github.com/SigNoz/signoz)
> To use it on your forked repo, edit the 'Open in Gitpod' button url to `https://gitpod.io/#https://github.com/<your-github-username>/signoz`
> To use it on your forked repo, edit the 'Open in Gitpod' button URL to `https://gitpod.io/#https://github.com/<your-github-username>/signoz` -->
# Contribute to SigNoz Helm Chart
**[`^top^`](#)**
<hr>
Need to update [https://github.com/SigNoz/charts](https://github.com/SigNoz/charts).
# 5. Contribute to SigNoz Helm Chart 📊
### To run helm chart for local development
**Need to Update: [https://github.com/SigNoz/charts](https://github.com/SigNoz/charts).**
- run `git clone https://github.com/SigNoz/charts.git` followed by `cd charts`
- it is recommended to use lightweight kubernetes (k8s) cluster for local development:
## 5.1 To run helm chart for local development
- Clone the SigNoz repository and cd into charts directory,
```
git clone https://github.com/SigNoz/charts.git && cd charts
```
- It is recommended to use lightweight kubernetes (k8s) cluster for local development:
You can always reach out to `ankit@signoz.io` to understand more about the repo and product. We are very responsive over email and [slack](https://signoz.io/slack).
There are many other ways to get involved with the community and to participate in this project:
- If you find any bugs, please create an issue
- If you find anything missing in documentation, you can create an issue with label **documentation**
- If you want to build any new feature, please create an issue with label `enhancement`
- If you want to discuss something about the product, start a new [discussion](https://github.com/SigNoz/signoz/discussions)
- Use the product, submitting GitHub issues when a problem is found.
- Help code review pull requests and participate in issue threads.
- Submit a new feature request as an issue.
- Help answer questions on forums such as Stack Overflow and [SigNoz Community Slack Channel](https://signoz.io/slack).
- Tell others about the project on Twitter, your blog, etc.
### Conventions to follow when submitting commits, PRs
1. We try to follow https://www.conventionalcommits.org/en/v1.0.0/
Again, Feel free to ping us on [`#contributing`](https://signoz-community.slack.com/archives/C01LWQ8KS7M) or [`#contributing-frontend`](https://signoz-community.slack.com/archives/C027134DM8B) on our slack community if you need any help on this :)
More specifically the commits and PRs should have type specifiers prefixed in the name. [This](https://www.conventionalcommits.org/en/v1.0.0/#specification) should give you a better idea.
e.g. If you are submitting a fix for an issue in frontend - PR name should be prefixed with `fix(FE):`
2. Follow [GitHub Flow](https://guides.github.com/introduction/flow/) guidelines for your contribution flows
3. Feel free to ping us on `#contributing` or `#contributing-frontend` on our slack community if you need any help on this :)
Portions of this software are licensed as follows:
* All content that resides under the "ee/" directory of this repository, if that directory exists, is licensed under the license defined in "ee/LICENSE".
* All third party components incorporated into the SigNoz Software are licensed under the original license provided by the owner of the applicable component.
* Content outside of the above mentioned directories or restrictions above is available under the "MIT Expat" license as defined below.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
@@ -86,9 +85,9 @@ Hier findest du die vollständige Liste von unterstützten Programmiersprachen -
### Bereitstellung mit Docker
Bitte folge den [hier](https://signoz.io/docs/deployment/docker/) aufgelisteten Schritten um deine Anwendung mit Docker bereitzustellen.
Bitte folge den [hier](https://signoz.io/docs/install/docker/) aufgelisteten Schritten um deine Anwendung mit Docker bereitzustellen.
Die [Anleitungen zur Fehlerbehebung](https://signoz.io/docs/deployment/troubleshooting) könnten hilfreich sein, falls du auf irgendwelche Schwierigkeiten stößt.
Die [Anleitungen zur Fehlerbehebung](https://signoz.io/docs/install/troubleshooting/) könnten hilfreich sein, falls du auf irgendwelche Schwierigkeiten stößt.
SigNoz helps developers monitor applications and troubleshoot problems in their deployed applications. SigNoz uses distributed tracing to gain visibility into your software stack.
SigNoz helps developers monitor applications and troubleshoot problems in their deployed applications. With SigNoz, you can:
👉 Visualise Metrics, Traces and Logs in a single pane of glass
👉 You can see metrics like p99 latency, error rates for your services, external API calls and individual end points.
@@ -32,14 +33,43 @@ SigNoz helps developers monitor applications and troubleshoot problems in their
👉 Run aggregates on trace data to get business relevant metrics
👉 Filter and query logs, build dashboards and alerts based on attributes in logs
- Unified UI for metrics, traces and logs. No need to switch from Prometheus to Jaeger to debug issues, or use a logs tool like Elastic separate from your metrics and traces stack.
- Application overview metrics like RPS, 50th/90th/99th Percentile latencies, and Error Rate
- Slowest endpoints in your application
- See exact request trace to figure out issues in downstream services, slow DB queries, call to 3rd party services like payment gateways, etc
- Filter traces by service name, operation, latency, error, tags/annotations.
- Run aggregates on trace data (events/spans) to get business relevant metrics. e.g. You can get error rate and 99th percentile latency of `customer_type: gold` or `deployment_version: v2` or `external_call: paypal`
-Unified UI for metrics and traces. No need to switch from Prometheus to Jaeger to debug issues.
-Native support for OpenTelemetry Logs, advanced log query builder, and automatic log collection from k8s cluster
Prometheus is good if you want to do just metrics. But if you want to have a seamless experience between metrics and traces, then current experience of stitching together Prometheus & Jaeger is not great.
Prometheus is good if you want to do just metrics. But if you want to have a seamless experience between metrics and traces, then current experience of stitching together Prometheus & Jaeger is not great.
Our goal is to provide an integrated UI between metrics & traces - similar to what SaaS vendors like Datadog provides - and give advanced filtering and aggregation over traces, something which Jaeger currently lack.
@@ -118,27 +152,60 @@ Our goal is to provide an integrated UI between metrics & traces - similar to wh
### SigNoz vs Jaeger
Jaeger only does distributed tracing. SigNoz does both metrics and traces, and we also have log management in our roadmap.
Jaeger only does distributed tracing. SigNoz supports metrics, traces and logs - all the 3 pillars of observability.
Moreover, SigNoz has few more advanced features wrt Jaeger:
- Jaegar UI doesn’t show any metrics on traces or on filtered traces
- Jaeger can’t get aggregates on filtered traces. For example, p99 latency of requests which have tag - customer_type='premium'. This can be done easily on SigNoz
<p>  </p>
### SigNoz vs Elastic
- SigNoz Logs management are based on ClickHouse, a columnar OLAP datastore which makes aggregate log analytics queries much more efficient
- 50% lower resource requirement compared to Elastic during ingestion
We have published benchmarks comparing Elastic with SigNoz. Check it out [here](https://signoz.io/blog/logs-performance-benchmark/?utm_source=github-readme&utm_medium=logs-benchmark)
<p>  </p>
### SigNoz vs Loki
- SigNoz supports aggregations on high-cardinality data over a huge volume while loki doesn’t.
- SigNoz supports indexes over high cardinality data and has no limitations on the number of indexes, while Loki reaches max streams with a few indexes added to it.
- Searching over a huge volume of data is difficult and slow in Loki compared to SigNoz
We have published benchmarks comparing Loki with SigNoz. Check it out [here](https://signoz.io/blog/logs-performance-benchmark/?utm_source=github-readme&utm_medium=logs-benchmark)
SigNoz is looking forward to working with security researchers across the world to keep SigNoz and our users safe. If you have found an issue in our systems/applications, please reach out to us.
## Supported Versions
We always recommend using the latest version of SigNoz to ensure you get all security updates
## Reporting a Vulnerability
If you believe you have found a security vulnerability within SigNoz, please let us know right away. We'll try and fix the problem as soon as possible.
**Do not report vulnerabilities using public GitHub issues**. Instead, email <security@signoz.io> with a detailed account of the issue. Please submit one issue per email, this helps us triage vulnerabilities.
Once we've received your email we'll keep you updated as we fix the vulnerability.
## Thanks
Thank you for keeping SigNoz and our users safe. 🙇
# Notes for Maintainers/Contributors who will change Line Numbers of Frontend & Query-Section. Please Update Line Numbers in `./scripts/commentLinesForSetup.sh` & `./CONTRIBUTING.md`
# Notes for Maintainers/Contributors who will change Line Numbers of Frontend & Query-Section. Please Update Line Numbers in `./scripts/commentLinesForSetup.sh` & `./CONTRIBUTING.md`
- --queryService.url=http://query-service:8085
- --storage.path=/data
# Notes for Maintainers/Contributors who will change Line Numbers of Frontend & Query-Section. Please Update Line Numbers in `./scripts/commentLinesForSetup.sh` & `./CONTRIBUTING.md`
# Check is Docker daemon is installed and available. If not, the install & start Docker for Linux machines. We cannot automatically install Docker Desktop on Mac OS
echo"+++++++++++ IMPORTANT READ ++++++++++++++++++++++"
echo"Docker Desktop must be installed manually on Mac OS to proceed. Docker can only be installed automatically on Ubuntu / openSUSE / SLES / Redhat / Cent OS"
echo"+++++++++++ IMPORTANT READ ++++++++++++++++++++++"
echo"Docker must be installed manually on your machine to proceed. Docker can only be installed automatically on Ubuntu / openSUSE / SLES / Redhat / Cent OS"
echo"or reach us on SigNoz for support https://signoz.io/slack"
echo"++++++++++++++++++++++++++++++++++++++++"
@@ -494,21 +516,15 @@ else
echo""
echo -e "🟢 Your frontend is running on http://localhost:3301"
echo""
echo"ℹ️ By default, retention period is set to 7 days for logs and traces, and 30 days for metrics."
echo -e "To change this, navigate to the General tab on the Settings page of SigNoz UI. For more details, refer to https://signoz.io/docs/userguide/retention-period \n"
if[$setup_type=='clickhouse'];then
if is_arm64;then
echo"ℹ️ To bring down SigNoz and clean volumes : sudo docker-compose -f ./docker/clickhouse-setup/docker-compose.arm.yaml down -v"
else
echo"ℹ️ To bring down SigNoz and clean volumes : sudo docker-compose -f ./docker/clickhouse-setup/docker-compose.yaml down -v"
fi
else
echo"ℹ️ To bring down SigNoz and clean volumes : sudo docker-compose -f ./docker/druid-kafka-setup/docker-compose-tiny.yaml down -v"
fi
echo"ℹ️ To bring down SigNoz and clean volumes : $sudo_cmd docker-compose -f ./docker/clickhouse-setup/docker-compose.yaml down -v"
zap.S().Errorf("[receiveGoogleAuth] sso requested but feature unavailable %s in org domain %s",model.SSO)
http.Redirect(w,r,fmt.Sprintf("%s?ssoerror=%s",redirectUri,"feature unavailable, please upgrade your billing plan to access this feature"),http.StatusMovedPermanently)
return
}
q:=r.URL.Query()
iferrType:=q.Get("error");errType!=""{
zap.S().Errorf("[receiveGoogleAuth] failed to login with google auth",q.Get("error_description"))
http.Redirect(w,r,fmt.Sprintf("%s?ssoerror=%s",redirectUri,"failed to login through SSO "),http.StatusMovedPermanently)
return
}
relayState:=q.Get("state")
zap.S().Debug("[receiveGoogleAuth] relay state received",zap.String("state",relayState))
parsedState,err:=url.Parse(relayState)
iferr!=nil||relayState==""{
zap.S().Errorf("[receiveGoogleAuth] failed to process response - invalid response from IDP",err,r)
handleSsoError(w,r,redirectUri)
return
}
// upgrade redirect url from the relay state for better accuracy
// this is the source url that initiated the login request
redirectUri:=constants.GetDefaultSiteURL()
ctx:=context.Background()
if!ah.CheckFeature(model.SSO){
zap.S().Errorf("[receiveSAML] sso requested but feature unavailable %s in org domain %s",model.SSO)
http.Redirect(w,r,fmt.Sprintf("%s?ssoerror=%s",redirectUri,"feature unavailable, please upgrade your billing plan to access this feature"),http.StatusMovedPermanently)
return
}
err:=r.ParseForm()
iferr!=nil{
zap.S().Errorf("[receiveSAML] failed to process response - invalid response from IDP",err,r)
handleSsoError(w,r,redirectUri)
return
}
// the relay state is sent when a login request is submitted to
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.