BloodKnight9923

I'm only working with logs across 8 servers with a lot of cross talk and ELK covered the logging side brilliantly, but falls over on metrics from what I have seen so far. I'll check out the TICK stack, that sounds like it may be a welcome replacement.

Thanks for the suggestion!

Never heard of Elastalert, I'll have to check that out. By the name I'm guessing it's triggers off an elasticsearch server, which would cover infrastructure I already have - so that's nice.

Thanks for the suggestion!

Hah. I went to college with you. Small world. Will check out your library, I've been doing a lot of work with chatbots over the last year, focused on Slack. I've only really been working with Java solutions though, so a python library is a nice change of pace.

Thanks for the link!

I've been meaning to use grafana for more than homelab server monitoring.

I've always found it so satisfying to sit back after setting up these types of systems and to watch everything churn out metrics / logs. I'll check out the kibana plugin, I'm using that in production at the moment.

Thanks for the reply!

I use slack for a lot of notifications too. We strapped a python chatbot on as an integration and gave the bot access to our product which made asking the bot what's happening really easy.

Chatops are catching on, and I'm intrigued. Thanks for the response!

I'll take a look at it, thanks for the suggestion!

I'll check it out! Thanks for the link

I've been dancing over the line between devops and backend development. It sounds like I am where you were historically, I'm using ansible to deploy docker images to EC2 instances, and a few monitoring scripts in python to do a little more finely tuned orchestration.

Lately I've been using home-brew chatops to manage products so it's nice to hear what other people are using. Operable looks really interesting, I'm going to give it a shot. Thanks for the example cog!

My big issue was getting multi-node deployments working well in AWS. I hit walls of configuration issues, DNS issues, poor documentation on fields, and generally could not make much forward progress. Running locally or on a single node OpenShift was fantastic, the haproxies for ingress were easy to configure and launching new services was impressively easy.

I was leveraging EFS as NFS mounts for my persistent volumes and had good results.

You might check out fabric8 if only for their visualizations of what is going on in your openshift / kubernetes environment.

Thanks for the youtube link! I'll be sure to check it out

Well that's exciting. I've been pushing towards Kubernetes with the company I'm at right now, got half the battle done by dockerizing our services and using Harbor to manage the containers.

Do you have any advice, or gotchas on getting into kubernetes development?

Yes, but for the unique reason that I have worked on web tracking analytics packages and they are terrifying.

From what I have seen working on those packages, the vast majority of users do not care, or do not understand what they are in for and will say "Sure, track me, what's the worst that could happen?"

We used the dreaded zombie-cookies to track when users would hit our pages and to track their passage across content because it gave us a lot more information on how our products were used, and as such gave us a lot of information to hand over to marketing to up our lead gen strategies. From there, we could wow investors.

From a company perspective, we loved that most users would blindly click yes. Enough did so that we never even bothered looking into the minority that opted for do not track.

Very carefully.

I currently work as a self-employed independent contractor in the cloud-engineering and devops automation sector in the greater Boston area. I have a strong focus on minimizing cost while making sure the customer achieves that they intend to, and that has given me an edge over fellow contractors that like to drop a known pattern in place and call it a day.

Here's an example.

I had a meeting a few days ago where I was asked to optimize a section of a product that made no sense to me (eliminating DNS and SSL tunnel start-up times). I have a firm believe in how I operate that I do not want to waste my customer's time, money, or my time in the work that I do.

I came back with a data-driven response showing other areas of the product with low hanging fruit that got seconds of time back instead of milliseconds on the area they wanted. I implemented one solution as an example, and landed several more months of contract work with them as a result.

I don't want to waste my time to get paid, I want to solve interesting problems and get paid solving them. I also want to stand behind my work, and stand proud.

So for me planning my career is as simple as finding companies that have problems I can address, for me that is low level network protocol analysis, distributed systems, cloud deployments, and java optimization. I hit those hard, and then build up quotes from customers I have worked with to show potential leads what I am capable of. Understanding that anyone you are talking to is a potential lead was huge for me. Just because it's some guy you ran into at a bar, some woman talking about her start-up, whatever - they all are potential customers, and you need to hold yourself as a professional.

Don't be an ass, establish credibility, and show that you actually care. Money follows.

I have personally found that anyone taking issue with this is a pain to work with in general. If you understand what the developer is talking about, and you know that this is a pedantic comparison, then what is the issue?

The only times I have seen someone take issue was because of an ego-related response. I don't have time to deal with that in my day to day, so I generally just say "Whatever floats your boat" and fall in with their term, simmilar to how I would document code and fall in place with code style while working on someone's project with existing code.

Unless there is something I see that would actually cause real problems for future development, customers, or myself, I won't take issue with the little things. There are a lot of other hills that I would rather die on than spaces and hyphens.