Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix warning callout for metrics configuration #203

Merged
merged 1 commit into from
Mar 6, 2025
Merged

Fix warning callout for metrics configuration #203

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 3 additions & 4 deletions content/configuration/16.metrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,8 @@ To enable performance and error measurement of connected services, Directus can
| `METRICS_TOKENS` | A CSV of tokens to allow access to via a `Authorization: Metrics <token>` header. By default it is restricted to admins | -- |
| `METRICS_SERVICES` | A CSV of directus services to observe metrics for. Currently `database`, `cache`, `redis` and `storage` are supported | `database,cache,redis,storage` |

::: warning Metric Aggregation

::callout{icon="material-symbols:warning-rounded" color="amber"}
**Metric Aggregation**
If Directus is running within a PM2 context, then metrics will be aggregated on a per scheduled job frequency. Ensure
Prometheus' scrape frequency takes that into account.

:::
::