Which Bitbucket metrics should be monitored using Grafana and Prometheus, and why?
FYI: Our Bitbucket server is up in a dockerised infra
Related
I am working on deploying an Airflow instance to production in Microsoft Azure, but one of the premises of the project is to develop an agnostic solution when it comes about the Cloud provider. My first idea was to deploy Airflow to production using Docker, so I could run the containers regardless the Cloud provider.
Is that a recommended way to achieve the goal?
Airflow provides a Helm chart that allows you to install Airflow on a Kubernetes cluster. All cloud providers offer a Kubernetes service (Azure AKS, AWS EKS, GCP GKE).
Here's the bare minimum Helm command to install the chart (from the docs: https://airflow.apache.org/docs/helm-chart/stable/index.html#installing-the-chart):
helm repo add apache-airflow https://airflow.apache.org
helm upgrade --install airflow apache-airflow/airflow --namespace airflow --create-namespace
I have a unique type of Kubernetes cluster that cannot install the Kubernetes Datadog agent. I would like to collect the logs of individual docker containers in my Kubernetes pods similar to how the Docker agent works.
I am currently collecting docker logs from Kubernetes and then using a script with the Datadog custom log forwarder to upload them to Datadog. I was curious if there is a better way to achieve this serverless collection of docker logs from Kubernetes clusters in datadog? The ideal situation I want is to plug my kubeconfig somewhere and then let Datadog take care of the rest without deploying anything onto my Kubernetes cluster.
Is there an option for that outside of creating a custom script?
A better way would be to use a sidecar container with a logging agent, it won't increase the load on the API server.
Reference: https://kubernetes.io/docs/concepts/cluster-administration/logging/#sidecar-container-with-a-logging-agent
Datadog agent looks like doesn't support /suggest running as a sidecar (https://github.com/DataDog/datadog-agent/issues/2203#issuecomment-416180642)
I suggest looking at using other logging agent and pointing the backend to datadog.
Some options are:
fluentd: https://blog.powerupcloud.com/kubernetes-pod-management-using-fluentd-as-a-sidecar-container-and-prestop-lifecycle-hook-part-iv-428b5f4f7fc7
fluentd-bit: https://github.com/leahnp/fluentbit-sidecar
filebeat: https://www.elastic.co/beats/filebeat
Datadog supports them
https://docs.datadoghq.com/integrations/fluentd/
https://docs.datadoghq.com/integrations/filebeat/
i'm trying to monitor my Freeipa server using prometheus.
can i use LDAP exporter with telegraf plugin to collect freeipa metrics and then send them to prometheus?
Thanks in advance.
I want to integrate my Jira, Jenkins, and confluence. I have configured all the software with the help of a docker image. i.e., Jenkins -- Port 8082, Jira -- Port 8081, confluence -- Port 8090.
For Jira – Jenkins Integration, I used "Jira Issue Updater," but Jenkins console is troughing an error –
Unable to connect to REST service
java.net.ConnectException: Connection refused (Connection refused)Finished: SUCCESS
My fundamental question — Is it possible to connect two docker images because, by default, Jenkins and Jira's opening port are 8080. Still, I configured it as per my convenience (All docker images are in one docker network, and I could able to ping Jira's IP from Jenkins instance means Jira is reachable to Jenkins).
I am a bit confused about this integration. I need some support from community members.
I'm using Amazon Elastic Container Service plugin which allows running Jenkins slaves on AWS ECS. Functionality which allows running slaves on EC2 type of ECS works perfectly, but I can't run slaves on Fargate. Tasks in the cluster are not created and no any activity in the ECS cluster at all. Can anyone share configurations of Amazon Elastic Container Service plugin which successfully works with Fargate, or help with an issue?