You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: stable/enterprise/README.md
+75-1Lines changed: 75 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -418,6 +418,52 @@ anchoreConfig:
418
418
419
419
For those using the [Prometheus operator](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/developer/getting-started.md), a ServiceMonitor can be deployed within the same namespace as your Anchore Enterprise release. Once deployed, the Prometheus operator will automatically begin scraping the pre-configured endpoints for metrics.
**Note:** This feature is currently in **BETA**. More features, functionality, and support for this is planned.
424
+
425
+
Enabling this feature is optional. It provides a built-in Prometheus instance configured for monitoring Anchore Enterprise. It is setup to be internal only, scrape targets internally, and the intention is to provide service information and metrics for debugging and troubleshooting purposes. There is no ingress created for this Prometheus instance by default. There are also no dashboards or other human-friendly configurations set inside Prometheus since this iteration is intended to support automated tooling only, not direct human use.
426
+
427
+
**If you are looking to add Prometheus monitoring to your deployment for Operational purposes, it is recommended to use an external Prometheus instance and configure it to scrape the Anchore Enterprise services as shown above in the "Prometheus Metrics" section above.*
428
+
429
+
This chart uses the community Prometheus chart and sets up a ConfigMap containing a working `prometheus.yml` with a scalable scrape configuration for Anchore Enterprise and common Kubernetes targets automatically.
430
+
431
+
- Toggle with `prometheus.chartEnabled` (default: `false`).
432
+
- You **MUST** enable the Anchore metrics endpoint as shown above for the Enterprise services to expose metrics.
433
+
434
+
**Example usage:**
435
+
436
+
Minimal example to enable metrics and the internal Prometheus:
437
+
438
+
```yaml
439
+
anchoreConfig:
440
+
metrics:
441
+
enabled: true
442
+
# Note: The current beta Prometheus implementation requires metrics to be unauthenticated.
443
+
auth_disabled: true
444
+
445
+
prometheus:
446
+
chartEnabled: true
447
+
```
448
+
449
+
**Obtaining more detail by enabling the Node Exporter**
450
+
451
+
Additionally, adding the optional Node Exporter with this Prometheus deployment can provide additional node-level metrics for your Anchore Enterprise deployment.
452
+
453
+
Minimal example to enable metrics, the internal Prometheus, and the Node Exporter:
454
+
455
+
```yaml
456
+
anchoreConfig:
457
+
metrics:
458
+
enabled: true
459
+
# Note: The current beta Prometheus implementation requires metrics to be unauthenticated.
460
+
auth_disabled: true
461
+
prometheus:
462
+
chartEnabled: true
463
+
prometheus-node-exporter:
464
+
enabled: true
465
+
```
466
+
421
467
#### Example ServiceMonitor Configuration
422
468
423
469
The `targetPort` values in this example use the default Anchore Enterprise service ports.
@@ -1205,16 +1251,44 @@ To restore your deployment to using your previous driver configurations:
1205
1251
| `osaaMigrationJob.objectStoreMigration.object_store` | The configuration of the object_store for the dest-config.yaml | `{}` |
1206
1252
| `extraManifests` | List of additional manifests to be included in the chart | `[]` |
1207
1253
1254
+
### Optional Prometheus Monitoring for Anchore Enterprise
| `prometheus.server.name` | Name override for Prometheus server resources | `internal-anchore-prometheus-server` |
1269
+
| `prometheus.server.configMapOverrideName` | Name of an existing ConfigMap to override the default Prometheus server configuration | `anchore-enterprise-prometheus-config` |
| `prometheus.prometheus-node-exporter.nameOverride` | Base name for node-exporter resources (will be prefixed by release name) | `enterprise-prometheus-node-exporter` |
1272
+
| `prometheus.prometheus-node-exporter.port` | Container port where node-exporter exposes metrics | `9120` |
1273
+
| `prometheus.prometheus-node-exporter.service.name` | Service name for node-exporter | `enterprise-prometheus-node-exporter` |
1274
+
| `prometheus.prometheus-node-exporter.service.port` | Service port for node-exporter | `9120` |
1275
+
| `prometheus.prometheus-node-exporter.service.targetPort` | Target port on the node-exporter pod the Service forwards to | `9120` |
1276
+
1208
1277
## Release Notes
1209
1278
1210
1279
For the latest updates and features in Anchore Enterprise, see the official [Release Notes](https://docs.anchore.com/current/docs/releasenotes/).
1211
1280
1281
+
1212
1282
- **Major Chart Version Change (e.g., v0.1.2 -> v1.0.0)**: Signifies an incompatible breaking change that necessitates manual intervention, such as updates to your values file or data migrations.
1213
1283
- **Minor Chart Version Change (e.g., v0.1.2 -> v0.2.0)**: Indicates a significant change to the deployment that does not require manual intervention.
1214
1284
- **Patch Chart Version Change (e.g., v0.1.2 -> v0.1.3)**: Indicates a backwards-compatible bug fix or documentation update.
1215
1285
1286
+
### v3.19.x
1287
+
#### V3.19.0
1288
+
- Adds an optional Prometheus monitoring setup to Anchore Enterprise for future internal monitoring and support
1289
+
1216
1290
### V3.18.x
1217
-
#### V3.17.0
1291
+
#### V3.18.0
1218
1292
- Adds support for specifying custom init containers in deployments and jobs
0 commit comments