99#include < datadog/telemetry/metrics.h>
1010
1111#include < memory>
12- #include < unordered_map>
1312#include < vector>
1413
1514// / Telemetry functions are responsibles for handling internal telemetry data to
1918namespace datadog ::telemetry {
2019
2120// / Initialize the telemetry module
22- // / Once initialized, the telemetry module is running for the entier lifecycle
23- // / of the application.
21+ // / Once initialized, sends a notification indicating that the application has
22+ // / started. The telemetry module is running for the entire lifecycle of the
23+ // / application.
2424// /
2525// / @param configuration The finalized configuration settings.
2626// / @param logger User logger instance.
@@ -36,21 +36,6 @@ void init(FinalizedConfiguration configuration,
3636 tracing::HTTPClient::URL agent_url,
3737 tracing::Clock clock = tracing::default_clock);
3838
39- // / Sends a notification indicating that the application has started.
40- // /
41- // / This function is responsible for reporting the application has successfully
42- // / started. It takes a configuration map as a parameter, which contains various
43- // / configuration settings helping to understand how our product are used.
44- // /
45- // / @param conf A map containing configuration names and their corresponding
46- // / metadata.
47- // /
48- // / @note This function should be called after the application has completed its
49- // / initialization process to ensure that all components are aware of the
50- // / application's startup status.
51- void send_app_started (const std::unordered_map<tracing::ConfigName,
52- tracing::ConfigMetadata>& conf);
53-
5439// / Sends configuration changes.
5540// /
5641// / This function is responsible for sending reported configuration changes
0 commit comments