diff --git a/docs/deployment/kubernetes.mdx b/docs/deployment/kubernetes.mdx index 07119266e..593cd15ae 100644 --- a/docs/deployment/kubernetes.mdx +++ b/docs/deployment/kubernetes.mdx @@ -18,8 +18,8 @@ helm install keep keephq/keep Notice for it to work locally, you'll need this port forwarding: ``` +# expose the UI kubectl port-forward svc/keep-frontend 3000:3000 -kubectl port-forward svc/keep-backend 8080:8080 ``` To learn more about Keep's helm chart, see https://github.com/keephq/helm-charts/blob/main/README.md diff --git a/docs/deployment/stress-testing.mdx b/docs/deployment/stress-testing.mdx index 0959c925b..9f9dc9716 100644 --- a/docs/deployment/stress-testing.mdx +++ b/docs/deployment/stress-testing.mdx @@ -35,18 +35,18 @@ The primary parameters that affect the specification requirements for Keep are: ### Testing Scenarios: -- **Low Volume (< 10,000 total alerts, 100's of alerts per day)**: +- **Low Volume (< 10,000 total alerts, hundreds of alerts per day)**: - **Setup**: Use a standard relational database (e.g., MySQL, PostgreSQL) with default configurations. - **Expectations**: Keep should handle queries and alert ingestion with minimal resource usage. -- **Medium Volume (10,000 - 100,000 total alerts, 1000's of alerts per day)**: +- **Medium Volume (10,000 - 100,000 total alerts, thousands of alerts per day)**: - **Setup**: Scale the database to larger instances or clusters. Adjust best practices to the DB (e.g. increasing innodb_buffer_pool_size) - **Expectations**: CPU and RAM usage should increase proportionally but remain within acceptable limits. -3. **High Volume (100,000 - 1,000,000 total alerts, 5000's of alerts per day)**: +3. **High Volume (100,000 - 1,000,000 total alerts, >five thousands of alerts per day)**: - **Setup**: Deploy Keep with Elasticsearch for storing alerts as documents. - **Expectations**: The system should maintain performance levels despite the large alert volume, with increased resource usage managed through scaling strategies. -4. **Very High Volume (> 1,000,000 total alerts, 10k's of alerts per day)**: +4. **Very High Volume (> 1,000,000 total alerts, tens of thousands of alerts per day)**: - **Setup**: Deploy Keep with Elasticsearch for storing alerts as documents. - **Setup #2**: Deploy Keep with Redis and with ARQ to use Redis as a queue. diff --git a/examples/workflows/incident_example.yml b/examples/workflows/incident_example.yml new file mode 100644 index 000000000..46ce6266f --- /dev/null +++ b/examples/workflows/incident_example.yml @@ -0,0 +1,15 @@ +workflow: + id: aks-example + description: aks-example + triggers: + - type: incident + events: + - updated + - created + + actions: + - name: just-echo + provider: + type: console + with: + message: "Hey there! I am an incident!" diff --git a/keep-ui/app/alerts/alert-name.tsx b/keep-ui/app/alerts/alert-name.tsx index 7c31232a2..17cd0de51 100644 --- a/keep-ui/app/alerts/alert-name.tsx +++ b/keep-ui/app/alerts/alert-name.tsx @@ -62,11 +62,11 @@ export default function AlertName({ } return ( -