Graylog2 / collector-sidecar

Manage log collectors through Graylog
https://www.graylog.org/
Other
268 stars 56 forks source link

Include failure reason in Sidecar Collectors UI, improve failure tracking for large deployments #433

Closed ghost closed 1 year ago

ghost commented 2 years ago

Problem description

example

Environment

ref: [HS-974805117]

mpfz0r commented 2 years ago

@will-graylog if you are looking under the collector overview, and click on the collector name,

you can see the details here: image

Refs https://github.com/Graylog2/graylog2-server/pull/5208

mpfz0r commented 2 years ago

@will-graylog @mikedklein did you see my comment above? Can we close this?

ghost commented 2 years ago

@mpfz0r Let me check with my customer and I'll let you know if this is sufficient.

ghost commented 1 year ago

Hey @mpfz0r so sorry about the delay in response, but I just got back with the customer who says this is insufficient at the scale they are using sidecars (over 3,000 collectors in 1,500+ sidecar agents).

Is there a way we can create a table with all sidecars' statuses, error messages, and verbose debug info if applicable? Because I do agree with out customer that having to click through each sidecar to get to the specific collector's error message is quite tedious when using as many collectors as they are.

mpfz0r commented 1 year ago

@will-graylog I agree we should improve that. I'll pitch that to product