Pranav Marla
Pranav Marla
**Describe the bug** The bug is that Fluentd appears to try and open all existing buffer files simultaneously before attempting to flush existing logs / accept new logs (create new...
# Description Fixes #2584 **Motivation:** Align `LogEmitter` implementation with OTel Log spec **Summary:** - Remove `LogEmitter.flush()` - Modify `LoggingHandler.__init__()`: - Replace `log_emitter` arg with `log_emitter_provider` - Obtain `log_emitter` via `log_emitter_provider`...
**Describe the solution you'd like:** I think it would be helpful to have a way to display the alias details (such as what cluster they refer to). **Why do you...
**Rationale** I know that `default_log_group_name` and `default_log_stream_name` were introduced specifically as fallbacks in case the variables in `log_group_name` and `log_stream_name` failed to parse, so I can understand the logic behind...
Relatively minor issue, but I noticed that there seems to be conflicting default values mentioned for the `flush_timeout` multiline parser parameter. Specifically: - As per the [multiline parsing doc](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/multiline-parsing), the...
Hi, I noticed that there don't appear to be any tests for the following OSs: - `Ubuntu 18` - `Ubuntu 20` - `Ubuntu 22` - `RHEL 8` - `Amazon Linux...
**Describe the bug** I have instrumented a simple Python lambda function with the [new OTEL collector lambda layer](https://github.com/open-telemetry/opentelemetry-lambda/releases/tag/layer-collector%2F0.1.0) and the [new Python instrumentation layer](https://github.com/open-telemetry/opentelemetry-lambda/releases/tag/layer-python%2F0.1.0). The collector is configured to export...
**Describe the bug** The current documentation contains contradictory information regarding which lambda layer (auto-instrumentation vs collector) should be merged/added to the lambda first. Specifically: 1. The [auto-instrumentation doc](https://opentelemetry.io/docs/faas/lambda-auto-instrument/) says you...
**Describe the bug** The release notes for v0.1.0 of the [nodejs lambda layer](https://github.com/open-telemetry/opentelemetry-lambda/releases/tag/layer-nodejs%2F0.1.0) are wrong -- they appear to reference the Python lambda layer instead 
Due to the way that timestamps are currently formatted in the screenshot names, the order of the screenshots is not preserved for videos greater than 1 hour. For example, let's...