Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,646,746
Community Members
 
Community Events
196
Community Groups

not all k8s events are pushed to elasticsearch with the default config from deploy/ directory

not all k8s events are pushed to elasticsearch with the default config from deploy/ directory

https://github.com/opsgenie/kubernetes-event-exporter

Use case:

from a namespace where a container is running, delete the pod so it can generate some events and those events we expect them to be pushed to elasticsearch which doesnt happen with the default config from deploy directory of above link

 

1 comment

Samir
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 17, 2020

Hi @nandu yana  - is this question pertaining to Opsgenie at all? Sounds like the question is kubernetes related but just wondering if Opsgenie is involved in this question.

 

Thanks,

Samir

Hi Samir,

thanks for your response

we are using Opsgenie for exporting all the events of the cluster to elasticsearch 

when we delete a pod - kubectl delete po podName -n namespace

i see the below events 

 

21s Normal Killing pod/qabnwclient-5dc94494d5-p2ff4 Stopping container bnwclient
21s Normal Scheduled pod/qabnwclient-5dc94494d5-s9msj Successfully assigned monitoring-system/qabnwclient-5dc94494d5-s9msj to ip-10-48-8-87.corp.ybusa.net
20s Normal Pulling pod/qabnwclient-5dc94494d5-s9msj Pulling image "511296683960.dkr.ecr.us-east-1.amazonaws.com/bnw-apps:bnwclient-1.0.6"
20s Normal Pulled pod/qabnwclient-5dc94494d5-s9msj Successfully pulled image "511296683960.dkr.ecr.us-east-1.amazonaws.com/bnw-apps:bnwclient-1.0.6"
20s Normal Created pod/qabnwclient-5dc94494d5-s9msj Created container bnwclient
20s Normal Started pod/qabnwclient-5dc94494d5-s9msj Started container bnwclient
16m Normal SuccessfulCreate replicaset/qabnwclient-5dc94494d5 Created pod: qabnwclient-5dc94494d5-p2ff4
21s Normal SuccessfulCreate replicaset/qabnwclient-5dc94494d5 Created pod: qabnwclient-5dc94494d5-s9msj

 

i expected them to be delivered to elasticsearch(ES) but i do not see them being sent to ES

 

the config i used is 

apiVersion: v1
kind: ConfigMap
metadata:
name: event-exporter-cfg
namespace: {{ .Release.Namespace }}
data:
config.yaml: |
logLevel: debug
route:
match:
- kind: Pod|Deployment|ReplicaSet
receiver: dump
receivers:
- name: "dump"
elasticsearch:
hosts:
- http://elasticsearch-master.elasticsearch.svc:9200
index: kube-events-ns

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events