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
"""
Suppose it depends on what business wants to do with the logs, but we wanted to get alerted about any errors or unusual spikes in logging activity. We ended up implementing a small python agent running in our Tools namespace that runs aggregation queries periodically (~ every 5 mins) against Elasticsearch and then making the counts available on a Prometheus /metrics endpoint. With annotations on this Pod, this can automatically be scraped by SysdigCloud and then be used to generate Alerts.
The advantage is that we get metrics about log activity across all our Pods without having to individually deal with sidecars. One drawback is that there can be a lag in getting logs into Elasticsearch. You also have to be mindful about how frequent you are querying Elasticsearch. This drawback is w... Read more
"""
"""
Suppose it depends on what business wants to do with the logs, but we wanted to get alerted about any errors or unusual spikes in logging activity. We ended up implementing a small python agent running in our Tools namespace that runs aggregation queries periodically (~ every 5 mins) against Elasticsearch and then making the counts available on a Prometheus /metrics endpoint. With annotations on this Pod, this can automatically be scraped by SysdigCloud and then be used to generate Alerts.
The advantage is that we get metrics about log activity across all our Pods without having to individually deal with sidecars. One drawback is that there can be a lag in getting logs into Elasticsearch. You also have to be mindful about how frequent you are querying Elasticsearch. This drawback is w... Read more
"""
https://stackoverflow.developer.gov.bc.ca/questions/147
The text was updated successfully, but these errors were encountered: