Feat/db event writer elx #2624
No reviewers
Labels
No labels
1week
2weeks
Failed compliance check
IP cameras
NATS
Possible security concern
Review effort 1/5
Review effort 2/5
Review effort 3/5
Review effort 4/5
Review effort 5/5
UI
aardvark
accessibility
amd64
api
arm64
auth
back-end
bgp
blog
bug
build
checkers
ci-cd
cleanup
cnpg
codex
core
dependencies
device-management
documentation
duplicate
dusk
ebpf
enhancement
eta 1d
eta 1hr
eta 3d
eta 3hr
feature
fieldsurvey
github_actions
go
good first issue
help wanted
invalid
javascript
k8s
log-collector
mapper
mtr
needs-triage
netflow
network-sweep
observability
oracle
otel
plug-in
proton
python
question
reddit
redhat
research
rperf
rperf-checker
rust
sdk
security
serviceradar-agent
serviceradar-agent-gateway
serviceradar-web
serviceradar-web-ng
siem
snmp
sysmon
topology
ubiquiti
wasm
wontfix
zen-engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
carverauto/serviceradar!2624
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/2624/head"
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?
Imported from GitHub pull request.
Original GitHub pull request: #2215
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2215
Original created: 2025-12-29T15:50:14Z
Original updated: 2025-12-30T17:36:33Z
Original head: carverauto/serviceradar:feat/db_event_writer_elx
Original base: testing
Original merged: 2025-12-30T17:36:31Z by @mfreeman451
IMPORTANT: Please sign the Developer Certificate of Origin
Thank you for your contribution to ServiceRadar. Please note, when contributing, the developer must include
a DCO sign-off statement indicating the DCO acceptance in one commit message. Here
is an example DCO Signed-off-by line in a commit message:
Describe your changes
Issue ticket number and link
Code checklist before requesting a review
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2215#discussion_r2651515024
Original created: 2025-12-29T18:23:51Z
Original path: elixir/serviceradar_core/lib/serviceradar/event_writer/processors/logs.ex
Original line: 18
should be in ocsf schema
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2215#discussion_r2651516397
Original created: 2025-12-29T18:24:50Z
Original path: elixir/serviceradar_core/lib/serviceradar/event_writer/processors/otel_metrics.ex
Original line: 18
i believe this should be in ocsf metrics schema format as well
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2215#discussion_r2651517252
Original created: 2025-12-29T18:25:29Z
Original path: elixir/serviceradar_core/lib/serviceradar/event_writer/processors/otel_metrics.ex
Original line: 147
cant these be re-usable functions here seems like we are recreating these a bunch
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2215#discussion_r2651517519
Original created: 2025-12-29T18:25:38Z
Original path: elixir/serviceradar_core/lib/serviceradar/event_writer/processors/otel_traces.ex
Original line: 18
should be in ocsf?
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2215#discussion_r2651518233
Original created: 2025-12-29T18:26:08Z
Original path: elixir/serviceradar_core/lib/serviceradar/event_writer/processors/sweep.ex
Original line: 30
again, can we put this in an ocsf format?
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2215#discussion_r2651518722
Original created: 2025-12-29T18:26:26Z
Original path: elixir/serviceradar_core/lib/serviceradar/event_writer/processors/telemetry.ex
Original line: 29
is this in ocsf? should it be?
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2215#discussion_r2652162388
Original created: 2025-12-30T03:55:50Z
Original path: elixir/serviceradar_core/lib/serviceradar/jobs/refresh_trace_summaries_worker.ex
Original line: 17
shouldnt we be using an ash adapter here?