Log Events

Sending Events

Events can be emitted using the OTel logging SDKs, much like any other log record. As long as a value for the eventNameCopy property is provided, the log record will be treated as an event.

Using Javascript as an example, this would look like this:

1234567891011121314
import { logs } from '@opentelemetry/api-logs';

const logger = logs.getLogger('my-application', '1.0.0');

logger.emit({
  severityText: 'INFO',
  body: 'User login successful',
  eventName: 'user.login'
  attributes: {
    'user.id': '12345',
    'user.email': 'user@example.com',
    'login.method': 'oauth'
  }
});

Kubernetes Events

Dash0 provides enhanced support for Kubernetes events collected via the k8seventsreceiver component of the OpenTelemetry Collector. These events are automatically transformed upon ingestion to match via resource centricity with the rest of Kubernetes resources.

Kubernetes Events can be accessed via a specialised events view and are automatically collected by the Dash0 Operator v0.92.0 and above.

Users of the OpenTelemetry Operator and otel-collector-contrib can enable Kubernetes event collection with the following snippet:

12
receivers:
  k8s_events:

Querying Events

Log events are a special form of log record. All analysis methods that work on logs in Dash0 also work for log events. The distinguishing feature of log events, eventName field, can be filtered and grouped by via otel.event.nameCopy.