search

operate-first / support

This repo should serve as a central source for users to raise issues/questions/requests for Operate First.
GNU General Public License v3.0
15 stars 25 forks source link

Centralized logging #463

Closed billburnseh closed 2 years ago

billburnseh commented 3 years ago

Is your feature request related to a problem? Please describe. NERC requires a centralized log to manage their large deployment

Describe the solution you'd like Ideally a common solution that meets NERC's needs as well as the needs from telemetry and AIOPs efforts.

Describe alternatives you've considered Part of this issue is vet various alternatives to choose the best.

Additional context Original description Given the size the NERC deployment is expected to grow to, we will likely need an independent ELK stack for various logs. We have not started this yet. Goal: Design and deploy Elasticsearch engine and configure Kibana with meaningful dashboards.

Suggested action This is a large project, and also overlaps with the centralized logging needed in Operate First for AIOps and Telemetry sharing. We will probably tackle this one when we have better capability to store Operate First logs in NESE with proper policy in place. We will create an issue to track this in Operate First.

4n4nd commented 3 years ago

@billburnseh we recently set up an instance of Loki on Smaug to which we are pushing cluster logs. Instead of setting up a whole new instance of ES and Kibana, maybe this Loki and Grafana setup could be used?

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

sesheta commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

sesheta commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/operate-first/support/issues/463#issuecomment-1088195765): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.