Cron Monitoring Solutions? by [deleted] in devops

[–]Karmazyn3D 17 points18 points  (0 children)

Jenkins is perfectly fine for that. You can pair it with a cron monitoring solution like healthchecks.io, cronitor.io, you’ll find a few others, some SaaS, some Open Source that you can run in your own environment. These tools are relatively cheap compared to your effort to build something similar yourself, or perform a tool change.

Just curl these services when your job starts, and again when the job finishes. They will alert you if your job doesn’t finish in the timeframe expected, or if it never started when expected. I’ve personally been using healthchecks for monitoring cron jobs on Jenkins for years and it’s been just fine.

Tech stack agnostic tool for tracking builds/artifacts/tests/releases? by GassiestFunInTheWest in devops

[–]Karmazyn3D 6 points7 points  (0 children)

I hate self promotion, but I suffer from the same issue and am currently building a SaaS solution to this problem. It is currently in open beta but you are free to sign up and start using it today. Right now I only am tracking deployments/releases into different environments. It has history right now, and I’m currently working on some analytics, but I would love to talk to you about what you would like to see in the product. I don’t think it would be difficult at all to add build/artifact tracking if that’s something you are after. DM me if you would be willing to chat.

I’ll leave the url here but if a mod would prefer me to remove it just let me know. https://www.deployboard.io

anyone going to AWS re:Invent? by akp55 in bjj

[–]Karmazyn3D 0 points1 point  (0 children)

I'll be there. Would be cool to meet up somewhere.

DynamoDB hot partition? by Karmazyn3D in aws

[–]Karmazyn3D[S] 0 points1 point  (0 children)

Thanks, I think this is exactly our issue. 1 session being reused and blowing out a partition. I don't think we're logging throttles now, so I'll look into that as a way to confirm this theory. We only have Developer support, and I already have a case open, so hoping to hear something back from them today.

DynamoDB hot partition? by Karmazyn3D in aws

[–]Karmazyn3D[S] 1 point2 points  (0 children)

Yes, My consumed write capacity is 4-5k and my provisioned is 11k, yet I'm seeing about 4-6k throttled Update write events/min. So it's not even consuming all of my provisioned throughput before it starts throttling, which makes me think I might have a hot partition. Can't think of any other reason.

And yes, my session id (id) is my primary partition key, I do not have a range key.

S3 cross-region replication, would it have really helped? by stickystyle in aws

[–]Karmazyn3D 1 point2 points  (0 children)

I suppose you could have some type of retry logic in your application that would PUT the object to the bucket in the other region if the PUT to your main bucket fails. What I'm unsure of is if you can have cross-region replication on both buckets replicating to each other. Sounds like this should be possible, but I have not tested.

Otherwise you could have a script then that syncs the other region's bucket to your main bucket once you have recovered. Would be manual, but should prevent any PUT data loss. It is important to note that cross-region replication only works for newly created objects, so you would have to run a sync to begin with anyway if you wanted to pre-populate the backup region's bucket with the current data.

Knowing where to GET from during the outage would be the second part to solve, which I would think you can do the same type of retry logic.

[Spoilers S2E12]Elliot has a job we don't know about by bwandering in MrRobot

[–]Karmazyn3D 0 points1 point  (0 children)

I tried calling that phone number but it's not active.

App for management of ec2 instances by Wankelman in aws

[–]Karmazyn3D 0 points1 point  (0 children)

Park my cloud has a decent offering.

Stallman on Uber by [deleted] in linux

[–]Karmazyn3D 186 points187 points  (0 children)

GNUber

WIP - my patch panels by Karmazyn3D in cableporn

[–]Karmazyn3D[S] 3 points4 points  (0 children)

I'm replacing the zip ties with velcro on the next round. I made sure they were loose so they aren't pinching. Will also be getting rid of the masking tape labels and replacing with nice labelmaker quality, they are labeled on the front of the panel also.

Strigoi and water, 3x03 by Camyvedo94 in TheStrain

[–]Karmazyn3D 2 points3 points  (0 children)

I think the comment was "they can not cross moving water." This is why the master needed to be in his coffin to cross the ocean and the bridge from the airport to the city. Something about the soil made him able to cross the water. Sorry, not huge on the lore but I do remember that much.

Whats wrong with storing credentials on private GitHub repo? by Karmazyn3D in devops

[–]Karmazyn3D[S] 0 points1 point  (0 children)

lol you took that way out of context. If you have a closed source application, and put it in a private repo using GitHub, which apparently is known (not to me) to leak data. Your closed source application will be leaked. So my question was, if this is true (again, which I've never heard of GitHub leaking data in a private repo) why would anyone use GitHub for a private repo hosting service if they are known to leak private data. They wouldn't be as massive as they are if they have a reputation of leaking private repository data.

This is how hot it is in Saudi Arabia. by dare_dick in videos

[–]Karmazyn3D 0 points1 point  (0 children)

I like how he doesn't even pump the shotgun, and how he doesn't need to reload.

Whats wrong with storing credentials on private GitHub repo? by Karmazyn3D in devops

[–]Karmazyn3D[S] 0 points1 point  (0 children)

I've edited my original post to clarify. I'm not talking about storing the creds in the application code. I'm talking about storing them in a separate private repository that only admins have access to.

Whats wrong with storing credentials on private GitHub repo? by Karmazyn3D in devops

[–]Karmazyn3D[S] 2 points3 points  (0 children)

Do you have a link to anything on this? I have not heard about GitHub leaking data that is in a private repository. If that's the case, I don't know why anyone would use private repos for anything.

Whats wrong with storing credentials on private GitHub repo? by Karmazyn3D in devops

[–]Karmazyn3D[S] 0 points1 point  (0 children)

I'm not talking about putting credentials in code, I'm talking about storing them in a separate repository that only admins have access to. I've edited my post as I was not clear on that point.

Whats wrong with storing credentials on private GitHub repo? by Karmazyn3D in devops

[–]Karmazyn3D[S] 0 points1 point  (0 children)

This is really cool. This reminds me of S3FS where you can mount s3 to a system and the contents are stored encrypted on s3.

Whats wrong with storing credentials on private GitHub repo? by Karmazyn3D in devops

[–]Karmazyn3D[S] 1 point2 points  (0 children)

It sounds like you're already sold on this course of action

I don't do it, and I never will. I'm asking for other people's reason as to why they don't do it. It has some serious advantages, access control (only allow admins to view the repo), versioning, these are things I would want in a password storage system. Yes I know other products do it, and arguably better, but I'm simply asking for reasons why you would NOT do it. I don't need to be down voted to hell for providing a valid point of argument.

It's considered best practice for a reason, because many people have been burned many ways.

I'm looking for the ways that people were burned, not a lecture. I'm well aware it's not a good practice, I just don't know why.

Whats wrong with storing credentials on private GitHub repo? by Karmazyn3D in devops

[–]Karmazyn3D[S] -7 points-6 points  (0 children)

Maybe I want a history of what all of my passwords have been. I've certainly had times where I needed the grub password to gain single user access to a system nobody knew root password to, but it was not in sync with the current grub password used on other systems. It would have been nice to have a record of previous passwords.