Files
zitadel/proto/zitadel
Livio Spring 63c92104ba chore: service ping api design (#9984)
# Which Problems Are Solved

Add the possibility to report information and analytical data from
(self-hosted) ZITADEL systems to a central endpoint.
To be able to do so an API has to be designed to receive the different
reports and information.

# How the Problems Are Solved

- Telemetry service definition added, which currently has two endpoints:
- ReportBaseInformation: To gather the zitadel version and instance
information such as id and creation date
- ReportResourceCounts: Dynamically report (based on #9979) different
resources (orgs, users per org, ...)
- To be able to paginate and send multiple pages to the endpoint a
`report_id` is returned on the first page / request from the server,
which needs to be passed by the client on the following pages.
- Base error handling is described in the proto and is based on gRPC
standards and best practices.

# Additional Changes

none

# Additional Context

Public documentation of the behaviour / error handling and what data is
collected, resp. how to configure will be provided in
https://github.com/zitadel/zitadel/issues/9869.

Closes https://github.com/zitadel/zitadel/issues/9872
2025-06-05 10:13:26 +00:00
..
2025-04-02 16:53:06 +02:00
2023-02-23 18:08:06 +07:00
2023-02-23 18:08:06 +07:00
2023-02-23 18:08:06 +07:00
2023-02-23 18:08:06 +07:00
2023-07-17 10:08:20 +02:00
2024-06-18 11:27:44 +00:00
2023-02-15 02:52:11 +01:00
2024-06-18 11:27:44 +00:00
2024-09-11 10:53:55 +00:00