mirror of
https://github.com/zitadel/zitadel.git
synced 2025-12-05 06:42:03 +00:00
rework configuration and docs
This commit is contained in:
@@ -14,43 +14,19 @@ Tracing:
|
||||
Fraction: 1.0
|
||||
MetricPrefix: zitadel
|
||||
|
||||
Analytics:
|
||||
# Push analytics data to defined endpoints
|
||||
Push:
|
||||
# Push the data to all these endpoints at least once.
|
||||
# If one endpoint returns an unsuccessful response code or times out,
|
||||
# ZITADEL retries to push the data point to all configured endpoints again until it succeeds.
|
||||
# The endpoints can be reconfigured at runtime.
|
||||
# Three redirects are followed.
|
||||
# Configure delivery guarantees and intervals in the section Projections.Customizations.Analytics
|
||||
Endpoints:
|
||||
# Include https://zitadel.com/usage if you want to help the ZITADEL maintainers improve the product's usability by giving them some insights.
|
||||
# Don't forget to opt in by setting AllEnabled to true.
|
||||
- https://zitadel.com/usage
|
||||
# If AllEnabled is true, all data listed below is pushed, regardless if they have the value true or false
|
||||
AllEnabled: false
|
||||
EnabledMetrics:
|
||||
# InstanceCreated is sent when a new virtual instance is created.
|
||||
# It is also emitted, when the first instance is created during the setup phase.
|
||||
# If InstanceCreated is false and AllEnabled is false, then the data points about created instances are omitted.
|
||||
InstanceCreated: false
|
||||
# FirstInstanceAuthenticationSucceeded is sent when the first authentication to a virtual instance succeeds.
|
||||
# This is the first authentication with the instances automatically setupped admin user, which can be a human or a machine.
|
||||
# If FirstInstanceAuthenticationSucceeded is false and AllEnabled is false, then the data points about first instance logins are omitted.
|
||||
FirstInstanceAuthenticationSucceeded: false
|
||||
# FirstProjectCreated is sent when a first project after the automatically setupped ZITADEL project is created in a virtual instance.
|
||||
# If FirstProjectCreated is false and AllEnabled is false, then the data points about first projects created are omitted.
|
||||
FirstProjectCreated: false
|
||||
# FirstApplicationCreated is sent when a first application after the automatically setupped applications in the ZITADEL project are created in a virtual instance.
|
||||
# If FirstApplicationCreated is false and AllEnabled is false, then the data points about first applications created are omitted.
|
||||
FirstApplicationCreated: false
|
||||
# FirstApplicationAuthenticationSucceeded is sent when the first login to a self-created application succeeds.
|
||||
# This can be a human users login or a machine user authentication.
|
||||
# If FirstApplicationAuthenticationSucceeded is false and AllEnabled is false, then the data points about first application logins are omitted.
|
||||
FirstApplicationAuthenticationSucceeded: false
|
||||
# InstanceDeleted is sent when a virtual instance is deleted.
|
||||
# If InstanceDeleted is false and AllEnabled is false, then the data points about deleted instances are omitted.
|
||||
InstanceDeleted: false
|
||||
Telemetry:
|
||||
# If Enabled is true, usage data is sent to the configured Telemetry.Endponts
|
||||
Enabled: false
|
||||
# Push telemetry data to all these endpoints at least once.
|
||||
# If one endpoint returns an unsuccessful response code or times out,
|
||||
# ZITADEL retries to push the data point to all configured endpoints again until it succeeds.
|
||||
# Configure delivery guarantees and intervals in the section Projections.Customizations.Analytics
|
||||
# The endpoints can be reconfigured at runtime.
|
||||
# Three redirects are followed.
|
||||
Endpoints:
|
||||
# Include https://zitadel.com/usage if you want to help the ZITADEL maintainers improve the product's usability by giving them some insights.
|
||||
# Don't forget to opt in by setting Telemetry.Enabled to true.
|
||||
- https://zitadel.com/usage
|
||||
|
||||
# Port ZITADEL will listen on
|
||||
Port: 8080
|
||||
@@ -216,15 +192,15 @@ Projections:
|
||||
HandleActiveInstances: 1080h
|
||||
# As quota notification projections don't result in database statements, retries don't have any effects
|
||||
MaxFailureCount: 0
|
||||
# Quota notifications are not so time critical. Setting RequeueEvery every five minutes doesn't annoy the db too much.
|
||||
# Quota notifications are not so time critical. Setting RequeueEvery every five minutes doesn't annoy the database too much.
|
||||
RequeueEvery: 300s
|
||||
Analytics:
|
||||
# Analytics delivery guarantee requirements are a bit higher, as they are not interactively retryable
|
||||
Telemetry:
|
||||
# Telemetry delivery guarantee requirements are a bit higher, as they are not interactively retryable
|
||||
# Defaults to 15 days
|
||||
HandleActiveInstances: 360h
|
||||
# As sending analytics data doesn't result in database statements, retries don't have any effects
|
||||
# As sending telemetry data doesn't result in database statements, retries don't have any effects
|
||||
MaxFailureCount: 0
|
||||
# Analytics data synchronization is not time critical. Setting RequeueEvery every 55 minutes doesn't annoy the db too much.
|
||||
# Telemetry data synchronization is not time critical. Setting RequeueEvery every 55 minutes doesn't annoy the database too much.
|
||||
RequeueEvery: 3300s
|
||||
|
||||
Auth:
|
||||
|
||||
Reference in New Issue
Block a user