collect OpenTelemetry logs from services in our hosting-provider infrastructure #1010
No reviewers
fediversity/developers
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
fediversity/fediversity!1010
Loading…
Reference in a new issue
No description provided.
Delete branch "kiara/fediversity:opentelemetry-collection"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #184.
d694793288517ac8d54dwindmillmachine andresources-otelnix-unitWIP: collect OpenTelemetry logs from services in our hosting-provider infrastructureto collect OpenTelemetry logs from services in our hosting-provider infrastructure*-otel.nixfilesEach `${app}-otel.nix` now exports the full resource request (`{ enable; nixos-configuration; }`) rather than just the `nixos-configuration` function. The hosting-provider group iterates generically: if `${app}-otel.nix` exists next to `${app}.nix`, attach it as the app's `otel` request. No more per-app dispatch in the group file. Assisted-by: Claude:claude-opus-4-7[1m]otel-wiring-testto call new*-otel.nixrequest shape`windmill-otel.nix` is now a resource-request attrset (`{ enable; nixos-configuration; }`) rather than a curried module function. The standalone wiring test consumes the module by calling `.nixos-configuration <endpoint>`. Assisted-by: Claude:claude-opus-4-7[1m]