Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion docs/deployments/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -709,7 +709,7 @@ logging:
logSuccessful: false
```

## Defining Separate Logging Configurations
#### Defining Separate Logging Configurations

Harper's logger supports defining multiple logging configurations for different components in the system. Each logging configuration can be assigned its own `path` (or `root`), `level`, `tag`, and flag to enable/disable logging to `stdStreams`. All logging defaults to the configuration of the "main" logger as configured above, but when logging is configured for different loggers, they will use their own configuration. Separate loggers can be defined:

Expand Down Expand Up @@ -1223,6 +1223,26 @@ Using the API:
}
```

### analytics

`analytics_aggregatePeriod` - _Type_: number; _Default_: 60 (seconds)

This defines how often recorded metrics in the `system.hdb_raw_analytics` table are aggregated into the `system.hdb_analytics` table. The analytics operations in the operations API exclusively use the aggregated analytics.

```yaml
analytics:
aggregatePeriod: 60
```

`analytics_replicate` - _Type_: boolean; _Default_: false

This defines whether or not the aggregated analytics data in `system.hdb_analytics` should be replicated to the rest of the cluster.

```yaml
analytics:
replicate: true
```

---

### Components
Expand Down