Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove syslog dependency #3563

Closed
derekperkins opened this issue Jan 18, 2018 · 6 comments
Closed

remove syslog dependency #3563

derekperkins opened this issue Jan 18, 2018 · 6 comments
Milestone

Comments

@derekperkins
Copy link
Member

derekperkins commented Jan 18, 2018

When not mounting the syslog as discussed with @enisoc, I see errors like these, but it appears that we're getting the information that needed to hit the syslog anyways, so I think we're ok.

cannot connect to syslog: Unix syslog delivery error
no connection, dropping syslog event: &events.TabletChange{Tablet:topodata.Tablet{Alias:(*topodata.TabletAlias)(0xc4201953c0), Hostname:"", PortMap:map[string]int32(nil), Keyspace:"urlslookup", Shard:"0", KeyRange:(*topodata.KeyRange)(nil), Type:2, DbNameOverride:"", Tags:map[string]string(nil), MysqlHostname:"", MysqlPort:3306}, Status:"updated"}
@enisoc
Copy link
Member

enisoc commented Jan 19, 2018

@alainjobart What do you think about just deleting the syslogger plugin?

To be honest, the syslogger plugin was only added as an example of "what you could do with the event package". I don't think anyone really wants this info piped to syslog.

Internally we had a plugin that piped these events to a remote "global event logging" service. Ideally we should make an example plugin for something more analogous like fluentd.

@alainjobart
Copy link
Contributor

I'd be fine removing it, it no one uses it.

For a sample one, we could just log into the regular logs with a prefix. And enable that by default, instead of syslog.

Well if we do that, we could keep the syslog one, just disabled by default...

@enisoc
Copy link
Member

enisoc commented Jan 19, 2018

If you still want to make sure there's at least one example plugin, I'm fine leaving it disabled by default.

@derekperkins
Copy link
Member Author

I would want to export those logs by default in kubernetes for an audit trail

@aquarapid
Copy link
Contributor

As running Vitess in k8s has been become more common, we are still logging this type of error for all events generated, since k8s pods almost never run syslog:

0730 23:10:58.958682       1 syslogger.go:84] no connection, dropping syslog event: &events........

Which just makes it hard to read. Can we just convert all events to normal log.* messages if the syslogger cannot be contacted? That way we only log a syslog-related error once (on startup), and that is it.

@aquarapid aquarapid added P2 and removed P3 labels Jul 30, 2020
aquarapid added a commit to planetscale/vitess that referenced this issue Jul 31, 2020
…s if the

syslog daemon cannot be contacted.

Signed-off-by: Jacques Grove <[email protected]>
@aquarapid
Copy link
Contributor

Should be addressed by #6511

@askdba askdba added this to the v8.0 milestone Oct 6, 2020
frouioui pushed a commit to planetscale/vitess that referenced this issue Nov 21, 2023
…r: remove unused topology watchers (vitessio#3578)

* backport of 3563

* fix conflicts

Signed-off-by: deepthi <[email protected]>

---------

Signed-off-by: deepthi <[email protected]>
Co-authored-by: deepthi <[email protected]>
systay pushed a commit that referenced this issue Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants