Vellox Group Ideas Portal
Hi Folks! Not sure if we dug into the APM Instrumentation conversation during the visit, but I wanted to give some more specifics on what we were looking for. Specifically, we're reading them with New Relic, but I think if y'all want to try something a bit more vendor-agnostic, then OpenTelemetry is vendor agnostic. But frankly, we'll have happy with anything as long as we can trace user sessions in New Relic.
Need to practice making user stories, so I hope this helps :) but seriously, please LMK if there are any questions.
**User Story: Trace Individual Session on DB Change**
As an application admin I want to trace individual user sessions starting from the moment they make any change to the database (e.g. insert, update, delete), so that we can monitor, debug, and analyze performance or behavior issues tied to specific actions.
---
**Acceptance Criteria:**
- Please generate a trace when a user-triggered event causes a database write (insert/update/delete)
- Please include:
* The user/session ID
* The operation type (insert, update, delete).
* The table or entity affected.
* A timestamp for when the change occurred.
---
**Example:**
When a user submits a form to update a flight request, a trace should start at the API handler, include the logic validating the form, the DB "UPDATE RequestsAndTemplates SET ..." call, and any downstream services called during the update.
---
Also, please le me know if this needs to be submitted as an enhancement request instead of ticket. I thought it should, but having trouble finding the ‘enhancement request’ dialog on the vellox ticketing site. Please advise :)
THANK YOU!!!
This was shipped in version 8.0.0 via task CAD-6023 Enable Optional Enhanced Observability Logging for External Tools Using OTLP
This will be released in version 8.0.0 as CAD-6023.
Enable Optional Enhanced Observability Logging for External Tools Using OTLP
Front-End Setting Names (Visible in UI)
Enable Observability and Security Platform Enhanced Telemetry (OTLP)
OTLP Endpoint
Database / Internal Setting Names
Front-End Name
Database / Internal Name
Enable Observability and Security Platform Enhanced Telemetry (OTLP)
EnableEnhancedTelemetryOtlp(recommended naming in write-up; use actual implementation name if different in code/settings store)OTLP Endpoint
OtlpEndpointNew UI Options
Toggle to enable or disable OTLP-based enhanced telemetry
Text field for OTLP endpoint URL
Default Behavior
OTLP telemetry is disabled by default
No OTLP export occurs unless explicitly enabled
Existing observability behavior remains unchanged
Updating the OTLP endpoint takes effect without requiring a Server restart
What’s changing
Dispatch Pro Server can now optionally emit enhanced observability and security-related telemetry using the OpenTelemetry Protocol (OTLP) over HTTP/JSON.
This allows external observability and security platforms to ingest standards-based telemetry directly from the Server without relying on vendor-specific SDKs, file scraping, or custom log parsing.
A new setting, Enable Observability and Security Platform Enhanced Telemetry (OTLP), controls whether this functionality is enabled.
Why it matters
Different customers and internal teams use different observability, monitoring, and security platforms.
This update provides a modern, standards-based way to integrate Dispatch Pro Server activity with OTLP-compatible tools by sending telemetry directly to a configured HTTP endpoint.
Benefits include:
Vendor-agnostic integration
No dependency on custom log parsers
No file-based ingestion pipeline required
Easier integration with observability and security platforms
Correlation between requests, processing, and database activity
Because this can generate high event volume, the feature is disabled by default and only runs when explicitly enabled.
What users will notice
A new setting to enable OTLP-based enhanced telemetry
A configurable OTLP endpoint URL
When enabled, the Server sends observability-related events in OTLP JSON/HTTP format
No visible workflow changes when disabled
No restart required when the OTLP endpoint is changed
Availability and setup
Disabled by default
Must be explicitly enabled in Server settings
Requires configuration of an OTLP endpoint
Can be used with any compatible observability or security platform
Will,
Thank you for submitting a feature request ticket. Do you have a contact at New Relic for future discussions about an integration? We will need to have internal discussions about the effort once we have documentation and then potentially work with the Professional Services department for a Statement of Work if we are able to add it to our future roadmap.