[OpenNMS/opennms] df50b3: fix(flows): emit a _msg field on VictoriaLogs flow...
Ronny Trommer via opennms-cvs <[email protected]>
| Newsgroups | gmane.network.opennms.cvs |
|---|---|
| Message-ID | <OpenNMS/opennms/push/refs/heads/ronny-poc/victorialogs-flows/[email protected]> |
Branch: refs/heads/ronny-poc/victorialogs-flows
Home: https://github.com/OpenNMS/opennms
Commit: df50b3e534c5a850f1ea98539ccc77c23fda2389
https://github.com/OpenNMS/opennms/commit/df50b3e534c5a850f1ea98539ccc77c23fda2389
Author: Ronny Trommer <[email protected]>
Date: 2026-08-06 (Thu, 06 Aug 2026)
Changed paths:
M features/flows/victorialogs/src/main/java/org/opennms/netmgt/flows/victorialogs/FlowJsonSerializer.java
M features/flows/victorialogs/src/test/java/org/opennms/netmgt/flows/victorialogs/FlowJsonSerializerTest.java
Log Message:
-----------
fix(flows): emit a _msg field on VictoriaLogs flow documents
VictoriaLogs requires a message field on every log entry; a document
without one is stored with the literal placeholder "missing _msg
field; see ..." as its message, which is what every flow showed as
in Grafana Explore.
Render a compact human-readable summary per flow, e.g. "Netflow v9
ingress tcp 192.168.1.1:51000 -> 10.0.0.1:443 https 1000 bytes 10
packets". Every part is optional but the result is never empty. No
query reads the field; it exists purely for humans browsing raw
logs. Together with _time it is one of the two deliberate additions
on top of the Elasticsearch-parity document shape.
Assisted-by: ClaudeCode:claude-fable-5
Signed-off-by: Ronny Trommer <[email protected]>
To unsubscribe from these emails, change your notification settings at https://github.com/OpenNMS/opennms/settings/notifications
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/wiki/index.php?page=MailingListFaq
opennms-cvs mailing list
To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-cvs