4 ms·

Is there currently a big market for new logging solutions? It has been years since I worked much with logs, so I don't know much about the current frustrations

Is there currently a big market for new logging solutions? It has been years since I worked much with logs, so I don't know much about the current frustrations of those who work with them on a daily basis. There will always be potential for a 'better mousetrap' to take some market share from existing solutions, but are current ones bad enough that a great solution could come in an capture significant market share? Or are today's systems 'good enough' that any new solution would face huge headwinds, even if it has some cool features? The reason I ask is because I am building a new kind of general-purpose data management system (https://www.Didgets.com https://www.Didgets.com) that can handle all kinds of data. It does file data, relational tables, Key-Value stores and other kinds of NoSql data. I did a little proto-typing of it managing some simple logging data and it seemed to work really well (in my opinion). But I would need to do a bit more work to get a good demo going. I have limited resources, so I would only want to do that if there is a significant demand in the logging space for something new. What is the biggest 'pain point' for people working with log data today?

tofuahdude 4y ago
For these kinds of established markets, you basically have to be 5x+ better or 5x+ cheaper. Then it's fine if the product is effectively the same.
- didgetmaster 4y ago
  5x+ better but effectively the same?? What does that mean?
  - baq 4y ago
    say you build splunk but instead of $500k you only charge $100k for the same featureset. not sure how to make a 5x better splunk...
    - didgetmaster 4y ago
      I know what 5x cheaper means but that was not what I was asking.
    - mdaniel 4y ago
      > not sure how to make a 5x better splunk... Oh, I can help you with that one: don't make it require 5 separate Ph.Ds in everythingology to deploy and run the PoS Then, for an extra $100k, have the new mythical company actually be responsive to bugs reported instead of "well, sucks to be you"
  - tofuahdude 4y ago
    What I meant by "product effectively the same" would be better said more like "solves the same problem". Then better is faster, less annoying, easier to integrate, better UX, etc., even if it sits in the same spot in the workflow.
macspoofing 4y ago
>Is there currently a big market for new logging solutions? There is a market, but it's saturated with offerings. There are so many solutions out there right now for metrics and log aggregation. >There will always be potential for a 'better mousetrap' to take some market share from existing solutions, but are current ones bad enough that a great solution could come in an capture significant market share? Or are today's systems 'good enough' that any new solution would face huge headwinds, even if it has some cool features? I'm going to take a guess and say the latter. There are a lot good(enough) off-the-shelf and managed services, that another offering is going to have a very hard time breaking through. >What is the biggest 'pain point' for people working with log data today? Ingestion, transformation, indexing, querying, visualization - those are all pretty much solved problems and everyone has a good enough solution. For me, it's specialized/niche use-cases and workflow, where the gaps are. For example, is your logging managed service able to be a drop-in HIPAA compliant solution (are individual customer logs physically segregated at the host level? Do you support automatic detection of Personal Health Information? Do you have an audited workflow to remove or deidentify, in batch, the offending logs. Do you support specialized access and dashboards to my customers so that they can see metrics and logs for their site? Do you support air-gapped, enterprise, on-prem deployments?).

tofuahdude 4y ago

For these kinds of established markets, you basically have to be 5x+ better or 5x+ cheaper. Then it's fine if the product is effectively the same.

didgetmaster 4y ago
5x+ better but effectively the same?? What does that mean?
- baq 4y ago
  say you build splunk but instead of $500k you only charge $100k for the same featureset. not sure how to make a 5x better splunk...
  - didgetmaster 4y ago
    I know what 5x cheaper means but that was not what I was asking.
  - mdaniel 4y ago
    > not sure how to make a 5x better splunk... Oh, I can help you with that one: don't make it require 5 separate Ph.Ds in everythingology to deploy and run the PoS Then, for an extra $100k, have the new mythical company actually be responsive to bugs reported instead of "well, sucks to be you"
- tofuahdude 4y ago
  What I meant by "product effectively the same" would be better said more like "solves the same problem". Then better is faster, less annoying, easier to integrate, better UX, etc., even if it sits in the same spot in the workflow.

macspoofing 4y ago

>Is there currently a big market for new logging solutions? There is a market, but it's saturated with offerings. There are so many solutions out there right now for metrics and log aggregation. >There will always be potential for a 'better mousetrap' to take some market share from existing solutions, but are current ones bad enough that a great solution could come in an capture significant market share? Or are today's systems 'good enough' that any new solution would face huge headwinds, even if it has some cool features? I'm going to take a guess and say the latter. There are a lot good(enough) off-the-shelf and managed services, that another offering is going to have a very hard time breaking through. >What is the biggest 'pain point' for people working with log data today? Ingestion, transformation, indexing, querying, visualization - those are all pretty much solved problems and everyone has a good enough solution. For me, it's specialized/niche use-cases and workflow, where the gaps are. For example, is your logging managed service able to be a drop-in HIPAA compliant solution (are individual customer logs physically segregated at the host level? Do you support automatic detection of Personal Health Information? Do you have an audited workflow to remove or deidentify, in batch, the offending logs. Do you support specialized access and dashboards to my customers so that they can see metrics and logs for their site? Do you support air-gapped, enterprise, on-prem deployments?).