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

Alternative logging/monitoring #31

Open
altvnk opened this issue Aug 8, 2015 · 2 comments
Open

Alternative logging/monitoring #31

altvnk opened this issue Aug 8, 2015 · 2 comments

Comments

@altvnk
Copy link
Contributor

altvnk commented Aug 8, 2015

Make possible to forward logs and metrics in customer specific location

@chrholme
Copy link

chrholme commented Sep 8, 2015

I've been doing some thinking regarding this requirement and the requirements outlined at https://github.com/CiscoCloud/cis-paas/blob/master/docs/design/mantl/logging.md
I think the simplest approach would be to pass messages through a queue such that they can be easily fanned out to customer specific locations.
I would think Kafka would be a good choice as it aligns with the plans in MI. I'm just a little concerned with some of the reading I've been doing regarding Zookeeper stability in K8S. Specifically: kubernetes/kubernetes#5017
There's also a lack of TLS for Kafka which might raise Infosec concerns.
I noticed we're looking at bring Sensu in for Monitoring; which would bring RabbitMQ for its transport layer. Rabbit has native support for TLS and no requirement for ZK. I would be interested in opinions on its suitability as a log message queue.

@rramchan55
Copy link

Seems like there has been done SSL support implemented recently in Kafka

https://issues.apache.org/jira/plugins/servlet/mobile#issue/KAFKA-1690

If there is a work around to the issues with running kakfa on kubernetes,
we could go ahead with Kafka instead of RabbitMQ.

I've been doing some thinking regarding this requirement and the
requirements outlined at
https://github.com/CiscoCloud/cis-paas/blob/master/docs/design/mantl/logging.md
I think the simplest approach would be to pass messages through a queue
such that they can be easily fanned out to customer specific locations.

I would think Kafka would be a good choice as it aligns with the plans in
MI. I'm just a little concerned with some of the reading I've been doing
regarding Zookeeper stability in K8S. Specifically:
kubernetes/kubernetes#5017
kubernetes/kubernetes#5017
There's also a lack of TLS for Kafka which might raise Infosec concerns.

I noticed we're looking at bring Sensu in for Monitoring; which would bring
RabbitMQ for its transport layer. Rabbit has native support for TLS and no
requirement for ZK. I would be interested in opinions on its suitability as
a log message queue.


Reply to this email directly or view it on GitHub
#31 (comment)
.

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

4 participants