Skip to content
This repository has been archived by the owner on Jul 29, 2018. It is now read-only.

ELK logging or metrics #86

Open
praveenkumar opened this issue Mar 22, 2016 · 5 comments
Open

ELK logging or metrics #86

praveenkumar opened this issue Mar 22, 2016 · 5 comments

Comments

@praveenkumar
Copy link
Contributor

Currently we don't have any ELK (ElasticSearch Logging) or metrics (like hawkular) enabled which will be good for developer experience.

@LalatenduMohanty
Copy link
Contributor

@praveenkumar @hferentschik sorry I am still not able to get context of the use case. Not sure how it is useful from CDK/ADB point of view.

@hferentschik
Copy link
Contributor

It is useful for the OpenShift user. The whole idea is to give a developer the chance to experience a as broad as possible functionality range of OpenShift out of the box. Configuring persistence volumes falls into the same category. When giving presentations, one of the questions which comes up is: "How do you do monitoring? Are there centralized logs? ..."

Personally, I am provisioning my CDK instance with Hawkular for demos. Partly to show the metrics in the console and partly it is a requirement for pod auto scaling which I like to demo.

So if possible I would love to see unified logging and metrics part as out of the box experience. However, I am a bit concerned about startup times (more containers need to come up, starting Hawkular takes quite some time on my machine) and resource usage. Especially the latter is important. Running the all-in-one OpenShift on a developer machine is quite a stretch to begin with. By adding all these other things we are even putting more load onto the VM. For that reason I think it would be great if things like metrics and logging are tested and optionally available. That would be the best imo. The provision scripts for these things are all there, but don't run per default. By setting and option you can then enable metrics resp. logging. I think any user who wants to experiment with these things would appreciate it, since working out the right provisioning sequence is sometimes quite tricky.

Last but not least, another reason to not enable Hawkular per default is that it works very flaky. At least on our all-in-on setup. I am not sure whether this is related to the all-in-one approach or maybe due to resource problems, but before I'd enable it out of the box, it would need more testing imo.

Bottom line, definitely a +1 for enabling (centralized) logging and metrics, but it should be optionally via flag or so (maybe this is the right use for the OPENSHIFT_OPTIONS variable we had in the startup script).

@alberttwong
Copy link

Just wanted to post that I was the one that asked for this originally on the container-tools mailing list.

praveenkumar added a commit to praveenkumar/adb-utils that referenced this issue Jun 20, 2016
@jorgemoralespou
Copy link

This is how we install logging and it works

@praveenkumar
Copy link
Contributor Author

Thanks @jorgemoralespou to point out, we are currently have some base code refactoring to add those capabilities as addons.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants