You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are not able to view the Prometheus metrics for medusa container in the cluster. Looks like it is enabled only for cassandra and reaper containers.
Our need is to enable grafana or kibana notifications on unfinished Cassandra backup everyday. Since Prometheus enablement is not available for medusa container, we are not able to take the output of it and send notifications.
And on elk stack, elastic search is not receiving logs of medusa container and below is the few lines of configuration.
type tail
id in_tail_container_logs
path /var/log/containers/*.log
exclude_path ["/var/log/containers/istio.log", "/var/log/containers/fluentd.log"]
pos_file /opt/bitnami/fluentd/logs/buffers/fluentd-docker.pos
Kindly help us on this or suggest us how to enable notification for unfinished Cassandra backups.
Thanks.
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-260
The text was updated successfully, but these errors were encountered:
Hi Team,
We are not able to view the Prometheus metrics for medusa container in the cluster. Looks like it is enabled only for cassandra and reaper containers.
Our need is to enable grafana or kibana notifications on unfinished Cassandra backup everyday. Since Prometheus enablement is not available for medusa container, we are not able to take the output of it and send notifications.
And on elk stack, elastic search is not receiving logs of medusa container and below is the few lines of configuration.
type tail
id in_tail_container_logs
path /var/log/containers/*.log
exclude_path ["/var/log/containers/istio.log", "/var/log/containers/fluentd.log"]
pos_file /opt/bitnami/fluentd/logs/buffers/fluentd-docker.pos
Kindly help us on this or suggest us how to enable notification for unfinished Cassandra backups.
Thanks.
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-260
The text was updated successfully, but these errors were encountered: