-
Notifications
You must be signed in to change notification settings - Fork 320
RudderStack Telemetry
Amey Varangaonkar edited this page May 22, 2020
·
1 revision
To help us improve RudderStack, we collect performance and diagnostic metrics about how you use it and how it is working. No customer data is present in the metrics.
The metrics collection can be disabled by setting the variable enableDiagnostics
to false in config/config.toml
The following are the metrics that are being collected. They are listed in config/config.toml
under the Diagnostics section.
-
enableServerStartMetric
: Tracks when the server starts -
enableConfigIdentifyMetric
: Tracks when the configuration is fetched for the first time from the Control Plane -
enableServerStartedMetric
: Tracks when the server is ready to accept requests -
enableConfigProcessedMetric
: Tracks any change in the configuration -
enableGatewayMetric
: Tracks the number of successful/failed requests -
enableRouterMetric
: Tracks the number of successful/aborted/retries requests for every router destination -
enableBatchRouterMetric
: Tracks the number of successful/failed requests for every batch router destination -
enableDestinationFailuresMetric
: Tracks the destination failures
To know more about RudderStack, you can contact us or start a conversation in our Slack community. To see RudderStack in action, make sure you request a demo today!