update docs - Telemetry #66
Conversation
…okern link) Signed-off-by: idohu <[email protected]>
✅ Deploy Preview for kubescape-io ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@matthyx can you please look at this through your more knowledgable 👓 please? |
docs/docs/operator/telemetry.md
Outdated
| insecure: <whether your otel endpoint requires ssl> | ||
| headers: <optional - map of headers required by tracing tool> | ||
| configurations: | ||
| otelUrl: # default is empty ,add yours otel URL here |
There was a problem hiding this comment.
also we should still include the endpoint settings because it's required depending on which otel backend we're talking to
There was a problem hiding this comment.
what do you mean ?
in capabillities?
There was a problem hiding this comment.
this configuration:
comment: opentelemetry collector
otelCollector:
name: otel-collector
endpoint:
insecure: true
headers:
uptrace-dsn: ""
comment: enable/disable hostmetrics collection
hostmetrics:
enabled: true
scrapeInterval: 30s
image:
repository: docker.io/otel/opentelemetry-collector
tag: 0.97.0
pullPolicy: IfNotPresent
resources:
requests:
cpu: 100m
memory: 500Mi
limits:
cpu: 1
memory: 1Gi
There was a problem hiding this comment.
just the endpoint:
endpoint:
insecure: true
headers:
uptrace-dsn: ""
There was a problem hiding this comment.
the user is configuring this?
There was a problem hiding this comment.
he might need to, depending on which Otel endpoint he's using, for instance with uptrace https://uptrace.dev/get/get-started.html#resource-attributes
There was a problem hiding this comment.
so it is enough?
or to add
There was a problem hiding this comment.
the uptrace is all the configuration from this page?
There was a problem hiding this comment.
just merge it like that, it's fine
Signed-off-by: idohu <[email protected]>
Signed-off-by: idohu <[email protected]>
updated operator capabilities + fix telemetry page (updated config+broken link)