Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
b
bitter-tailor-6977
03/20/2023, 3:59 PMHi,
I have a scenario,
I have N1 to N10 node and 25 microservices are running,
so i need to logg ecah 25 microservices log which going to deploy in different node….
the question is, suppose MicroService-1 (MS1) deployed to N1 and the pod restarted and deployed to N10) (conti)
so in above situation, how kube-logging operator Daemonset will be a solution…
i need log lifecycle to continued in any dashboard like kibana or loki
so if the pod is recreated in N10 , how i can see the entire logs in kibana or loki dashboard (because now the logs will be taken from N10 Daemonset right)
any solution do we have in rancher logging for this ?