Add OpenTelemetry #16
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Investigation
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Backstube/bookkeeping#16
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Aspire already provides default configs for capturing open telemetry data. We now just need to gather the information and store it for later examination.
At work a colleague used it in his bachelor thesis and has some great instructions on how to set it up
Maybe a separate service should be used that takes incomming OTel data and stores it. Usually one configures an OTel endpoint where data gets sent too. If we can do this with Aspire service discovery thats fine. If not the separate service might be a good idea to have the OTel config in one place
OTel doesn't store or visualise any data, it is just the protocol/standard for gathering them.
The following tools should be used for storing and visualising the data: