fat-apple

4 ms·

1. 1.▲
   by fat-apple 6y ago

   We’re truly sorry that you felt let down! You raise a great point that is worth clarifying though. All logs, metrics and future traces are stored in S3/GCS (and yes metrics are stored in TSDB format). While this does not allow a sing
2. 2.▲
   by fat-apple 6y ago

   Thanks for the great feedback, definitely understand where you're coming from and we'll keep that in mind moving forward! Very much appreciate the constructive criticism!
3. 3.▲
   by fat-apple 6y ago

   Thank you! We like to simplify but not obfuscate!
4. 4.▲
   by fat-apple 6y ago

   Thank you! Yes, design is very near and dear to our hearts! If you’re interested in giving me some early feedback on our UX, email me mat@opstrace.com.
5. 5.▲
   by fat-apple 6y ago

   Thanks for your support! We’re still early in our journey when compared to the featureset Datadog has built over time, but we definitely aspire to bridge the best of Datadog and open source. Based on your experience, what sorts of features
6. 6.▲
   by fat-apple 6y ago

   Thanks for your feedback! As with many in the industry, we are trying our best to figure this out. Our intention is to be really transparent with how we build and price software, which is why our commercial features will also be public in o
7. 7.▲
   by fat-apple 6y ago

   Curious to learn more about the tradeoffs you’ve found between Cortex and Victoria Metrics and why you could be drawn to one more than the other?
8. 8.▲
   by fat-apple 6y ago

   Thanks for that feedback - we've got a lot of work to do to make that more clear! We're still early in our journey so we’re not there yet, but we’re moving fast. We're working on a new collaborative UI for interacting with yo
9. 9.▲
   by fat-apple 6y ago

   We certainly don't want to create an adverse incentive where you would consider limiting the number of devs who had access to the monitoring system. There are trade-offs but we think that per-seat pricing (like GitLab, GitHub) actually
10. 10.▲
    by fat-apple 6y ago

    Yes you can do this today. You cannot send this directly to Opstrace via grpc yet, so you would need to use the Prometheus remote write exporter ( https://github.com/open-telemetry/opentelemetry-collector/bl... ) wi
11. 11.▲
    by fat-apple 6y ago

    :-) I have talked about the subject in this comment thread: https://news.ycombinator.com/item?id=25991764
12. 12.▲
    by fat-apple 6y ago

    We’re about to release a Datadog compatible API so you can point your Datadog agent at Opstrace instead (stay tuned for the blog post). Our goal is to be able to tell you exactly how much data the agent is sending and how much that is costi
13. 13.▲
    by fat-apple 6y ago

    Currently you can only deploy to AWS and GCP, but we do intend to extend support to on-prem/dedicated servers in due course (see https://news.ycombinator.com/item?id=25992237 ). Until now we’ve been focussing completely
14. 14.▲
    by fat-apple 6y ago

    Great questions! (1) As it stands today, you can already use https://vector.dev/docs/reference/sinks/prometheus_remote_wr... to write metrics directly to our Prometheus API. You can also use https:/&#x2
15. 15.▲
    by fat-apple 6y ago

    Mat here (Seb's Cofounder). Great question. We are not only building a piece of infrastructure but a complete product with its own UI and features, rather than a standalone API. Our customer is the end-user more than the person wanting