Earlier quoted context omitted.
Scientific Atlanta… there’s a name I haven’t heard in a long time. Didn’t they use to make crappy cable boxes, back when cable TV meant a box that connected to the antenna input via coax.
SA made set top boxes along with a bunch of back-end infrastructure to make them work. It was an acquisition that made sense on paper -- Cisco did (does) a lot of business with service providers, they make cable modem termination systems (the headend devices that handle cable modem connectivity,) had dabbled in IP video, so it was a natural evolution to make and sell the rest of the gear you'd need to operate a cable…
Cisco Acquires Splunk
221–230 of 525 posts
Re: Cisco Acquires Splunk
#222Earlier quoted context omitted.
SA made set top boxes along with a bunch of back-end infrastructure to make them work. It was an acquisition that made sense on paper -- Cisco did (does) a lot of business with service providers, they make cable modem termination systems (the headend devices that handle cable modem connectivity,) had dabbled in IP video, so it was a natural evolution to make and sell the rest of the gear you'd need to operate a cable…
I was thinking way earlier than that. My grandparents had a Scientific Atlanta box connected to their giant piece-of-furtniture Hughs and Mathis TV. This was late 80s, early 90s, long before digital TV, or cable having more than 30 or 40 channels.
Re: Cisco Acquires Splunk
#223Earlier quoted context omitted.
For how many data sources? The whole reason everyone goes to Splunk is that it scales, and scales incredibly well. Large enterprises can generate hundreds of terabytes to petabytes every day. Splunk has all sorts of issues, but to pretend as if you can replace them in any large shop with a 1200 line python script and SQLite is just being disingenuous. This acquisition falls right into Cisco's sweet spot, they aren't…
Splunk does not scale to large data sources. It fucks out at a few TB and then you have to spend hours on the phone trying to work out which combination of licenses and sales reps you need to get going again. By which time you can just suck the damn log file and grep it on the box.
Re: Cisco Acquires Splunk
#224Re: Cisco Acquires Splunk
#225To pile onto the Splunk "love" going on here. Splunk is one of those systems that's too "powerful" for small use-cases, but too expensive for the ones it's really designed for. Anecdote, I once worked with a client that really wanted to get Splunk, but produced so much network traffic that the discounted annual costs were more than the entire budget for the rest of the organization combined. That's staff, the buildin…
That's what I was wondering about when it comes to this acquisition. Can Cisco make Splunk even more expensive? I have faith they can, I know for many folks, Splunk tops the leaderboards when it comes to spend.
Re: Cisco Acquires Splunk
#226Earlier quoted context omitted.
It's around 6 data sources on ~25 machines, but it could be easily scaled to way more than that with a bit of work. And I mean less work than it takes to do even trivially simple things using the horrible Splunk API. There are many thousands of small companies using Splunk and getting totally ripped off for a very mediocre product with a rapacious and annoyingly aggressive salesforce.
> it could be easily scaled to way more than that with a bit of work. I guess you'd appreciate the words easily and bit are doing a lot of heavy lifting there.
This goes with the previous comment:
> And oh yeah, it's totally free instead of costing my company thousands of dollars a year
Unless you work for free, then something you make and maintain is not "totally free".
Re: Cisco Acquires Splunk
#227Earlier quoted context omitted.
For how many data sources? The whole reason everyone goes to Splunk is that it scales, and scales incredibly well. Large enterprises can generate hundreds of terabytes to petabytes every day. Splunk has all sorts of issues, but to pretend as if you can replace them in any large shop with a 1200 line python script and SQLite is just being disingenuous. This acquisition falls right into Cisco's sweet spot, they aren't…
Splunk does not scale to large data sources. It fucks out at a few TB and then you have to spend hours on the phone trying to work out which combination of licenses and sales reps you need to get going again. By which time you can just suck the damn log file and grep it on the box.
Re: Cisco Acquires Splunk
#228To pile onto the Splunk "love" going on here. Splunk is one of those systems that's too "powerful" for small use-cases, but too expensive for the ones it's really designed for. Anecdote, I once worked with a client that really wanted to get Splunk, but produced so much network traffic that the discounted annual costs were more than the entire budget for the rest of the organization combined. That's staff, the buildin…
I remember this talk about pricing strategy by one of their employees in a conference many years back (2017) - https://www.heavybit.com/library/video/value-based-pricing-s... . What I took away from that talk was that pricing can be unintuitive, for both the people setting it and buying it.
Re: Cisco Acquires Splunk
#229Genuinely surprised anybody would acquire Splunk in 2023. Whenever you hear about Splunk from security engineers, they're actively trying to get off it (edit: yes, primarily because of cost). Better, next-gen SIEMs are either here or around the corner.
Re: Cisco Acquires Splunk
#230Earlier quoted context omitted.
stripe, cloudflare (ish), github
Cloudflare's verify human challenge screen is so intrusive and frustrating that it will cost them their credibility IMHO, if it hasn't already. Some part of me feels that a properly designed cache should be able to handle any level of abusive traffic like a p2p cache would, and if it can't, then what are we all doing?