roshan8 / slo-tracker Goto Github PK

It would be great if slo-tracker could integrate with VictoriaMetrics + vmalert.

Running docker-compose up --build -d results in the following error:

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is not defined by "exports" in /usr/src/app/node_modules/postcss-safe-parser/node_modules/postcss/package.json
    at new NodeError (node:internal/errors:371:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:429:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:705:3)
    at resolveExports (node:internal/modules/cjs/loader:482:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:27)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/usr/src/app/node_modules/postcss-safe-parser/lib/safe-parser.js:1:17) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v17.5.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
1 error occurred:
	* Status: The command '/bin/sh -c yarn build' returned a non-zero code: 1, Code: 1

As a fix i changed the image version in ui/Dockerfile from node:latest to node:16 and it worked

As mentioned below, this has been adopted by Squadcast some time ago but there haven't been any active updates to the project since then. Are there plans to keep this in line with the version implemented at Squadcast? Adoption seems a lot less attractive if it won't be receiving any or ongoing updates.

I'm planning to start contributing back to the open-source project with all the new features that we added to squadcast.com once I get time!

Originally posted by @roshan8 in #20 (comment)

What is currently happening:

1. An incident is created in the dashboard for an alert in one of the available monitoring tools
2. The incident is in open state
3. The incident is marked as a false positive post analysis
4. The incident still remains in the open state

What should happen:

1. An incident is created in the dashboard for an alert in one of the available monitoring tools
2. The incident is in open state
3. The incident is marked as a false positive post analysis
4. The incident is moved to closed state

Why should the behaviour change:
The incident still should be moved to closed state since it is irrelevant when marked as a false positive and should not be accounted towards the error budget calculations or analytics

Step 6/14 : RUN npm install react-scripts --save -legacy-peer-deps
---> Running in c8d0aa420339
npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! errno ERR_SOCKET_TIMEOUT
npm ERR! network Invalid response body while trying to fetch https://registry.npmjs.org/rc-tree: Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-04-01T13_40_04_573Z-debug-0.log
The command '/bin/sh -c npm install react-scripts --save -legacy-peer-deps' returned a non-zero code: 1
ERROR: Service 'slo-fe' failed to build : Build failed

I see network-related errors/timeouts but my internet connectivity is solid.

Even though environment variables are available, we still end up using strings like:

    dbConnectionString := fmt.Sprintf("root:SecretPassword@tcp(%s:3306)/", config.DBHost)

which is really only valid for MySQL. It would be nice to make this all more flexible. At least allowing for sqlite installations for easier testing.

Hi,

Is Elastic APM and AWS CloudWatch supported as integration for SLO tracker?

Hey, just stumbled upon this via Reddit and wanted to take a look at the demo installation referenced at the bottom of the README. But it seems I need credentials. demo / demo didn't work, admin/admin did. Maybe you want to add this in the README