Add initial collector dashboards #246
Conversation
| exporter: | ||
| otlp: | ||
| # the endpoint of the selfmonitoring collector. In this case, it is assumed that there is a service called `selfmon-collector` that exposes port 4317. | ||
| endpoint: selfmon-collector:4317 |
There was a problem hiding this comment.
"selfmon-collector" is only defined in your k8s deployment below, right? Would localhost here as well and also on bare metal deployments?
There was a problem hiding this comment.
0.0.0.0 would only work if the collector sends to itself. For all other collectors it does not work. I guess we could do
| endpoint: selfmon-collector:4317 | |
| endpoint: <location-of-your-selfmon-collector>:4317 |
or something similar to make it explicit.
There was a problem hiding this comment.
Alternatively, we could think about distributing the .yaml files for Kubernetes along with the json files, but I am not sure if that wouldn't make it even more complicated
There was a problem hiding this comment.
This particular section here is about the selfmon collector scraping itself specifically, right?
There was a problem hiding this comment.
This particular section is, but I still opted for using the name of the service as the endpoint instead of 0.0.0.0 so they are consistent. This works, and if someone is copying together yaml files I believe it's easier to have them all be the same to avoid accidentally copying the wrong one.
| The `sidecar-collector` and `gateway-collectors` are used to send application telemetry to Dynatrace (e.g. traces, metrics, logs that the application produces). | ||
| Both of these collectors send only their selfmonitoring data (or internal telemetry) to the `selfmon-collector`. | ||
| The `selfmon-collector` is responsible for collecting, transforming and forwarding the internal telemetry for all collectors (including the `selfmon-collector` itself). | ||
| Only monitoring data about the collector passes through it; no monitoring data from non-collector applicaitons is sent via the `selfmon-collector`. |
There was a problem hiding this comment.
| Only monitoring data about the collector passes through it; no monitoring data from non-collector applicaitons is sent via the `selfmon-collector`. | |
| Only monitoring data about the collector passes through it; no monitoring data from non-collector applications is sent via the `selfmon-collector`. |
| The `selfmon-collector` is responsible for collecting, transforming and forwarding the internal telemetry for all collectors (including the `selfmon-collector` itself). | ||
| Only monitoring data about the collector passes through it; no monitoring data from non-collector applicaitons is sent via the `selfmon-collector`. | ||
|
|
||
| ```mermaid |
There was a problem hiding this comment.
This picture is difficult to read when having GitHub configured for the dark background.
| # Inject DT_ENDPOINT and DT_API_TOKEN as environment variables. This should be the environment where the selfmonitoring data will go. | ||
| # See <https://docs.dynatrace.com/docs/shortlink/otel-getstarted-otlpexport> for instructions on which endpoint and token scope to use. | ||
| otlphttp/selfmon: | ||
| endpoint: "${DT_ENDPOINT}/api/v2/otlp" |
There was a problem hiding this comment.
The endpoint and api token env variables should follow the same format as in our other use cases, for example https://docs.dynatrace.com/docs/extend-dynatrace/opentelemetry/collector/use-cases/batch
| exporters: | ||
| # Inject DT_ENDPOINT and DT_API_TOKEN as environment variables. This should be the environment where the selfmonitoring data will go. | ||
| # See <https://docs.dynatrace.com/docs/shortlink/otel-getstarted-otlpexport> for instructions on which endpoint and token scope to use. | ||
| otlphttp/selfmon: |
There was a problem hiding this comment.
| otlphttp/selfmon: | |
| otlphttp/dynatrace: |
| protocol: grpc/protobuf | ||
| temporality_preference: delta | ||
|
|
||
| extensions: [] |
There was a problem hiding this comment.
| extensions: [] |
For me this line caused the following problem with helm:
"Error: execution error at (opentelemetry-collector/templates/NOTES.txt:24:3): [ERROR] The opentelemetry-collector chart requires that the health_check extension to be included in the extension list."
|
Closed in favor of #274 |
No description provided.