Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed observability code. #84

Merged
merged 2 commits into from
Nov 6, 2023
Merged

Removed observability code. #84

merged 2 commits into from
Nov 6, 2023

Conversation

mwhittaker
Copy link
Member

A Service Weaver application has logs, traces, and metrics. Before this PR, weaver kube deploy generated Kubernetes YAML to set up Prometheus, Jaegar, Grafana, and Loki. The weaver kube babysitter exported logs, traces, and metrics to these systems. However, there was no way for a user to customize how telemetry was handled. If you wanted to export traces to Datadog, for example, well, you couldn't.

To address this problem in the long term, we're considering introducing a general purpose mechanism that would allow developers to customize deployers using a set of components. A metric exporting component, for example, would customize how metrics are exported.

In the short term, we're going to introduce a much simpler and less general approach where a developer can plug in custom ways to manage telemetry. This also means that weaver kube no longer has to generate YAML to run Prometheus, Jaegar, and whatnot. Instead, they will be plugins.

A Service Weaver application has logs, traces, and metrics. Before this
PR, `weaver kube deploy` generated Kubernetes YAML to set up Prometheus,
Jaegar, Grafana, and Loki. The `weaver kube` babysitter exported logs,
traces, and metrics to these systems. However, there was no way for a
user to customize how telemetry was handled. If you wanted to export
traces to Datadog, for example, well, you couldn't.

To address this problem in the long term, we're considering introducing
a general purpose mechanism that would allow developers to customize
deployers using a set of components. A metric exporting component, for
example, would customize how metrics are exported.

In the short term, we're going to introduce a much simpler and less
general approach where a developer can plug in custom ways to manage
telemetry. This also means that `weaver kube` no longer has to generate
YAML to run Prometheus, Jaegar, and whatnot. Instead, they will be
plugins.
@mwhittaker mwhittaker self-assigned this Oct 25, 2023
Copy link
Collaborator

@rgrandl rgrandl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great.

internal/impl/kube.go Show resolved Hide resolved
Copy link
Member Author

@mwhittaker mwhittaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Robert!

internal/impl/kube.go Show resolved Hide resolved
@mwhittaker mwhittaker merged commit b03aba6 into main Nov 6, 2023
10 checks passed
@mwhittaker mwhittaker deleted the no_observability branch November 6, 2023 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants