Skip to content

Commit dcf98f4

Browse files
authored
Merge branch 'master' into rob-846_holmes_docs_allow_direct_loki_tempo_connection
2 parents 7207423 + dfc97f6 commit dcf98f4

22 files changed

Lines changed: 183 additions & 43 deletions

File tree

.gitignore

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,3 +21,5 @@ skaffold.dev.yaml
2121
tests/last_used_tag.txt
2222
pytest.ini
2323
gen-config-test
24+
25+
**/.claude/settings.local.json

docs/configuration/alertmanager-integration/_pull_integration.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,12 @@ If Robusta fails to auto-detect the Prometheus and Alertmanager urls - and you s
2424
# prometheus_auth: ...
2525
# alertmanager_auth: ...
2626
27+
# If using a multi-tenant prometheus or alertmanager, pass the org id to all queries
28+
# prometheus_additional_headers:
29+
# X-Scope-OrgID: <org id>
30+
# alertmanager_additional_headers:
31+
# X-Scope-OrgID: <org id>
32+
2733
.. code-annotations::
2834
1. Example: http://alertmanager-Helm_release_name-kube-prometheus-alertmanager.default.svc.cluster.local:9093.
2935
2. Example: http://Helm_Release_Name-kube-prometheus-prometheus.default.svc.cluster.local:9090

docs/configuration/alertmanager-integration/_testing_integration.rst

Lines changed: 33 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,43 @@ Verify it Works
33

44
Send a dummy alert to AlertManager:
55

6-
.. code-block:: bash
6+
.. tab-set::
77

8-
robusta demo-alert
8+
.. tab-item:: Robusta CLI
9+
10+
If you have the Robusta CLI installed, you can send a test alert using the following command:
11+
12+
.. code-block:: bash
13+
14+
robusta demo-alert
15+
16+
.. tab-item:: Robusta UI
17+
18+
In the Robusta UI, go to the "Clusters" tab, choose the right cluster and click "Simulate Alert".
19+
20+
.. image:: /images/robusta-ui-simulate-alert-1.png
21+
:alt: Choose the cluster
22+
:width: 900
23+
:align: center
24+
25+
Then
26+
27+
1. Check **Send alert with no resource**.
28+
2. Provide a name for the alert in the **Alert name (identifier)** field (e.g., "Testing Prod AlertManager").
29+
3. Select **Alert Manager** under the "Send alert to" section.
30+
4. Click the **Simulate Alert** button to send the test alert.
31+
32+
.. image:: /images/robusta-ui-simulate-alert-2.png
33+
:alt: Send Test Alert
34+
:width: 600
35+
:align: center
936

1037
If everything is setup properly, this alert will reach Robusta. It will show up in the Robusta UI, Slack, and other configured sinks.
1138

39+
.. note::
40+
41+
It might take a few minutes for the alert to arrive due to AlertManager's `group_wait` and `group_interval` settings. More info `here <https://prometheus.io/docs/alerting/latest/configuration/#:~:text=How%20long%20to%20wait%20before%20sending%20a%20notification%20about%20new%20alerts%20that%0A%23%20are%20added%20to%20a%20group%20of%20alerts%20for%20which%20an%20initial%20notification%20has%0A%23%20already%20been%20sent>`_.
42+
1243
.. details:: I configured AlertManager, but I'm not receiving alerts?
1344
:class: warning
1445

docs/configuration/alertmanager-integration/coralogix_managed_prometheus.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,12 @@ Metrics querying lets Robusta pull metrics from Coralogix Managed Prometheus.
8282
# grafana_api_key: <YOUR GRAFANA EDITOR API KEY> # (1)
8383
# alertmanager_flavor: grafana
8484
85+
# If using a multi-tenant prometheus or alertmanager, pass the org id to all queries
86+
# prometheus_additional_headers:
87+
# X-Scope-OrgID: <org id>
88+
# alertmanager_additional_headers:
89+
# X-Scope-OrgID: <org id>
90+
8591
.. code-annotations::
8692
1. This is necessary for Robusta to create silences when using Grafana Alerts, because of minor API differences in the AlertManager embedded in Grafana.
8793

docs/configuration/alertmanager-integration/grafana-alert-manager.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -83,6 +83,12 @@ Modify and add the following config to ``generated_values.yaml`` and :ref:`updat
8383
# prometheus_additional_labels:
8484
# cluster: 'CLUSTER_NAME_HERE'
8585
86+
# If using a multi-tenant prometheus or alertmanager, pass the org id to all queries
87+
# prometheus_additional_headers:
88+
# X-Scope-OrgID: <org id>
89+
# alertmanager_additional_headers:
90+
# X-Scope-OrgID: <org id>
91+
8692
.. code-annotations::
8793
1. This is necessary for Robusta to create silences when using Grafana Alerts, because of minor API differences in the AlertManager embedded in Grafana.
8894

docs/configuration/alertmanager-integration/victoria-metrics.rst

Lines changed: 36 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,26 +8,48 @@ You will need to configure two integrations: one to send alerts to Robusta and a
88
Send Alerts to Robusta
99
============================
1010

11-
To configure, edit AlertManager's configuration:
11+
Add the following to your Victoria Metrics Alertmanager configuration (e.g., Helm values file or VMAlertmanagerConfig CRD):
12+
13+
.. code-block:: yaml
14+
15+
receivers:
16+
- name: 'robusta'
17+
webhook_configs:
18+
- url: 'http://<ROBUSTA-HELM-RELEASE-NAME>-runner.<NAMESPACE>.svc.cluster.local/api/alerts'
19+
send_resolved: true # (3)
20+
21+
route: # (1)
22+
routes:
23+
- receiver: 'robusta'
24+
group_by: [ '...' ]
25+
group_wait: 1s
26+
group_interval: 1s
27+
matchers:
28+
- severity =~ ".*"
29+
repeat_interval: 4h
30+
continue: true # (2)
31+
32+
.. code-annotations::
33+
1. Put Robusta's route as the first route, to guarantee it receives alerts. If you can't do so, you must guarantee all previous routes has ``continue: true`` set.
34+
2. Keep sending alerts to receivers defined after Robusta.
35+
3. Important, so Robusta knows when alerts are resolved.
1236

13-
.. include:: ./_alertmanager-config.rst
1437

1538
.. include:: ./_testing_integration.rst
1639

17-
Configure Metric Querying
40+
Configure Metrics Querying
1841
====================================
1942

20-
Metrics querying lets Robusta pull metrics and create silences.
43+
Robusta can query metrics and create silences using Victoria Metrics. If both are in the same Kubernetes cluster, Robusta can auto-detect the Victoria Metrics service. To verify, go to the "Apps" tab in Robusta, select an application, and check for usage graphs.
2144

22-
Add the following to ``generated_values.yaml`` and :ref:`update Robusta <Simple Upgrade>`.
45+
If auto-detection fails you must add the ``prometheus_url`` parameter and :ref:`update Robusta <Simple Upgrade>`.
2346

2447
.. code-block:: yaml
2548
2649
globalConfig: # this line should already exist
2750
# add the lines below
28-
alertmanager_url: "http://ALERT_MANAGER_SERVICE_NAME.NAMESPACE.svc.cluster.local:9093"
29-
grafana_url: ""
30-
prometheus_url: "http://VICTORIA_METRICS_SERVICE_NAME.NAMESPACE.svc.cluster.local:8429"
51+
alertmanager_url: "http://<VM_ALERT_MANAGER_SERVICE_NAME>.<NAMESPACE>.svc.cluster.local:9093" # Example:"http://vmalertmanager-victoria-metrics-vm.default.svc.cluster.local:9093/"
52+
prometheus_url: "http://VM_Metrics_SERVICE_NAME.NAMESPACE.svc.cluster.local:8429" # Example:"http://vmsingle-vmks-victoria-metrics-k8s-stack.default.svc.cluster.local:8429"
3153
# Add any labels that are relevant to the specific cluster (optional)
3254
# prometheus_additional_labels:
3355
# cluster: 'CLUSTER_NAME_HERE'
@@ -39,6 +61,12 @@ Add the following to ``generated_values.yaml`` and :ref:`update Robusta <Simple
3961
# grafana_api_key: <YOUR GRAFANA EDITOR API KEY> # (1)
4062
# alertmanager_flavor: grafana
4163
64+
# If using a multi-tenant prometheus or alertmanager, pass the org id to all queries
65+
# prometheus_additional_headers:
66+
# X-Scope-OrgID: <org id>
67+
# alertmanager_additional_headers:
68+
# X-Scope-OrgID: <org id>
69+
4270
.. code-annotations::
4371
1. This is necessary for Robusta to create silences when using Grafana Alerts, because of minor API differences in the AlertManager embedded in Grafana.
4472

docs/configuration/holmesgpt/toolsets/aws.rst

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -74,21 +74,7 @@ Configuration
7474

7575
.. md-tab-item:: Robusta Helm Chart
7676

77-
.. code-block:: yaml
78-
79-
holmes:
80-
additionalEnvVars:
81-
- name: AWS_ACCESS_KEY_ID
82-
value: AKIXDDDSDSdSA
83-
- name: AWS_SECRET_ACCESS_KEY
84-
value: =wJalrXUtnFEMI/KNG/bPxRfiCYEXAMPLEKEY
85-
- name: AWS_DEFAULT_REGION
86-
value: us-west-2
87-
toolsets:
88-
aws/rds:
89-
enabled: true
90-
91-
.. include:: ./_toolset_configuration.inc.rst
77+
This builtin toolset is currently only available in HolmesGPT CLI.
9278

9379
.. md-tab-item:: Holmes CLI
9480

216 KB
Loading
236 KB
Loading

docs/playbook-reference/index.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,4 @@
1212
automatic-remediation-examples/index
1313
prometheus-examples/index
1414
kubernetes-examples/index
15-
logs-triggers/index
15+
Log Based Alerting <logs-triggers/index>

0 commit comments

Comments
 (0)