Znaleziono ~30 ofert w 0.198s, strona 1 z 1
Aplikuj
-

Observability DevOps Engineer

@Billennium CI/CD pipelines IaC Grafana ELK Stack Datadog
Aplikuj
15 800 - 21 600 zł

Observability Engineer

@Hyland Microsoft Windows macOS Cloud Solutions
-

Observability Engineer

@Akamai Technologies
-

Observability Engineering Manager

@Canonical Grafana Kubernetes Python Linux
Aplikuj
18 480 - 24 360 zł

Storage Observability Engineer

@ITDS Polska Sp. z o.o. Python Java Node.js Go Grafana Prometheus Splunk Jenkins Ansible GitHub PostgreSQL MySQL Windows
Aplikuj
19 000 - 27 000 zł

Engineering Manager with Observability expertise

@CODILIME SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ AWS
Aplikuj
-

Monitoring & Observability Senior Specialist

@Brown Brothers Harriman Python Microsoft Azure SQL
Aplikuj
-

DevOps Observability Engineer

@PKO Bank Polski SA Bash Python Ansible
Aplikuj
-

DevOps Engineer (EKS / Cloud Foundry / Observability)

@BSH SPRZĘT GOSPODARSTWA DOMOWEGO sp. z o.o. EKS Kubernetes Kafka MongoDB ArgoCD DataDog Terraform CloudFoundry OpenSearch macOS Linux
Aplikuj
-

DevOps Engineer (EKS / Cloud Foundry / Observability)

@BSH SPRZĘT GOSPODARSTWA DOMOWEGO sp. z o.o. EKS Kubernetes Kafka MongoDB ArgoCD DataDog Terraform CloudFoundry OpenSearch macOS Linux
Aplikuj
-

DevOps Engineer (EKS / Cloud Foundry / Observability)

@BSH SPRZĘT GOSPODARSTWA DOMOWEGO sp. z o.o. EKS Kubernetes Kafka MongoDB ArgoCD DataDog Terraform CloudFoundry OpenSearch macOS Linux
Aplikuj
18 480 - 24 360 zł

Storage Observability Engineer

@ITDS Python Java Node.js
Aplikuj
18 480 - 24 360 zł

Storage Observability Developer - banking

@ITDS OpenTelemetry Python Ansible Splunk Jenkins Prometheus Grafana Node.js Java Golang
Aplikuj
-

Storage Observability Developer

@ALTEN Polska Python Ansible Kubernetes Jenkins Open Telemetry Grafana Splunk
Aplikuj
20 000 - 25 000 zł

DevOps-Observability

@ista Technologies Poland Ansible Grafana Cloud Prometheus
Aplikuj
-

DevOps Observability Engineer

@PKO Bank Polski Loki Elasticsearch Monitoring Tools CI/CD
Aplikuj
-

Senior Software Engineer, Tools & Observability - Hybrid

@Clari JavaScript SQL NoSQL MongoDB
Aplikuj
-

DevOps Engineer (Observability Focus)

@KUBO DevOps AWS Prometheus Grafana Loki Terraform CloudFormation
Aplikuj
-

Software Engineer, Performance, Reliability, Observability, PhD, Early Career

@Google Python C++ C JavaScript Java Go
Aplikuj
19 000 - 27 000 zł

Engineering Manager with Observability expertise

@CodiLime Networking infrastructure Cloud CI/CD
Aplikuj
-

DevOps Engineer (EKS / Cloud Foundry / Observability)

@BSH Sprzęt Gospodarstwa Domowego Kubernetes Cloud Foundry Kafka MongoDB YAML Helm Datadog OpenSearch GitOPS ArgoCD
Aplikuj
-

Solution Architect (Observability)

@ERGO Technology & Services Datadog Terraform IaC
Aplikuj
-

Senior Platform Engineer, SRE, Foundations Alliance (m/f/x)

@HelloFresh Kubernetes AWS Prometheus Observability OpenTelemetry Honeycomb Grafana
-

Senior Observability Platform Developer - Python/Go

@Canonical Go Observability Kubernetes Prometheus
-

Solution Architect (Observability​)

@ERGO Technology & Services S.A. Datadog Terraform Azure Kubernetes
-

DevOps Engineer (Observability Focus)

@KUBO DevOps AWS Prometheus Loki', 'Grafana', 'Tempo', 'Mimir' (LGTM stack) - Note: This is a common grouping but not a single tool, so listed as a descriptive string for clarity within tags if needed, or individual tags if preferred for strictness. For this schema, a descriptive string is used as it represents a suite of tools often used together for observability. If strict adherence to single tools is required, 'Grafana', 'Loki', 'Prometheus', 'Tempo', 'Mimir' would be separate tags. Given the prompt's phrasing, this combined tag reflects the intent. If individual tools are preferred, please specify. For now, using the prompt's phrasing as a tag for context. Let's refine this to individual tags for better machine readability as per typical schema practices. Re-evaluating: The prompt lists 'LGTM stack (Loki, Grafana, Tempo, Mimir)'. It's best to tag the individual components if the schema allows for multiple tags, which it does. So, individual tags are better. Let's list them individually. However, the prompt also mentions Prometheus separately. So, the list should be: Prometheus, Loki, Grafana, Tempo, Mimir, OpenTelemetry, AWS X-Ray, CloudWatch, ADOT. Let's ensure all mentioned technologies are captured. The prompt also mentions IaC tools like Terraform or CloudFormation, and CI/CD tools like GitHub Actions, GitLab CI, or Azure DevOps, Docker, Kubernetes. These should also be included as technology tags. The main focus is Observability, so that's the main_technology. The rest are supporting technologies. Let's compile the full list of relevant technologies from the job description for the tags. Technologies mentioned: Prometheus, LGTM stack (Loki, Grafana, Tempo, Mimir), OpenTelemetry, AWS X-Ray, CloudWatch, ADOT, Terraform, CloudFormation, GitHub Actions, GitLab CI, Azure DevOps, Docker, Kubernetes. The core focus is Observability, so that's the main_technology. The tags should encompass the specific tools and concepts. Let's refine the tags to be specific and actionable. The prompt asks for 'technology_tags'. It's best to list the specific tools and concepts. Let's re-evaluate the 'LGTM stack' part. Since it's a collection, it's better to list the individual components if the schema allows for multiple tags, which it does. So, 'Grafana', 'Loki', 'Tempo', 'Mimir' should be separate tags. Prometheus is also mentioned. OpenTelemetry, AWS X-Ray, CloudWatch, ADOT are also mentioned. IaC tools: Terraform, CloudFormation. CI/CD tools: GitHub Actions, GitLab CI, Azure DevOps. Containerization: Docker, Kubernetes. The main_technology is clearly 'Observability'. The tags should cover the specific technologies. Let's make sure the tags are concise and representative. The prompt mentions
-

APM/Observability Engineer (Inżynier Presales)

@TeamQuest ci/cd cloud code review dynatrace java
-

APM/Observability Engineer - Presales

@TeamQuest c# ci/cd cloud code review java .net
-

Software Engineer – Infrastructure Automation

@Astreya Automation Infrastructure Observability Telemetry
-

Site Reliability Engineer

@The Dot Collective Cloud Networking Python Observability