-
As it is now, when starting docker, then docker containers, there is no easy way to send logs to a logging daemon running within a container. The container must be started before logs can be sent to i…
-
Currently dagster's containerized deployments run pipelines using a single image (retrieved from the repository location). In some cases, different solids within a pipeline have vastly different depen…
-
Hi @verticacrossman, another issue we found while testing is that at the moment it seems impossible to disable file-based logging. In addition, the location where the log files are written is hard-cod…
-
Added the config map for the AWS EKS Fargate cluster
Kindly find the map below
kind: Namespace
apiVersion: v1
metadata:
name: aws-observability
labels:
aws-observability: enabled
--…
-
**Describe the bug**
As per the [conversation in Slack](https://camunda.slack.com/archives/CRQAL5A1M/p1719913149449599) the IDENTITY_LOG_LEVEL setting does not appear to take effect, this is confir…
-
We use Websphere Liberty Operator to test new release of Instant-On.
We use the WebSphere Liberty Operator (WLO) to test new releases of Instant-On. While testing Instant-On 24.0.0.10, I encounter…
-
```
Logging is currently either not happening, or not going through the servlet
engine's default logging mechanism (e.g., on Tomcat juli).
We should introduce a logging abstraction (similar to slf4j…
-
**Description**
Mounting a loopback device in a container requires `CAP=SYS_ADMIN` or even better `--privileged`. However, the `/dev/loop*` do not appear in the container when created dynamically.
…
-
### Issue Description
I ran into an odd issue, where on a system using both the podman-restart.service and multiple podman-kube@.service files, the normally running container (just using --restart=al…
-
### Bug category:
**Missing information**
### Request:
The [Azure CLI reference guidelines](https://github.com/Azure/azure-cli/blob/dev/doc/reference_doc_guidelines.md#examples) specifiy at lea…