hi
- User
hi
- Assistant
Hello! How can I help you today?
- User
Im a sales rep at Datadog, and I just took the following notes during a demo with Benjamin Site Reliability Engineer at Trustpair. Can you please help me rewrite the notes in a very clear, organised and professional way: Competition: New Relic, Grafana and prometheus. Lokey New Relic costs went wild and he stopped everything
He puts the overall observability topic on the side of the security topic
The CTO manages the whole costs
The criteria incluse the costs and the simplicity of the platform. They don’t have a security team and they don’t aim to have one So they wish to have a solution that doesn’t require house to be spent on the SIEM solution He wants somehting that integrates well with out of the box rules He wishes to spend a few minutes a weeks maximum on the SIEM solution He doesn’t expect on having many alerts
He aims to reduce the noise of alerts
They have 95% of environment on Kubernetes
They have monolithic architecture
They will aim to move to a micro service architecure
He doesn’t use logs enough. Lokey is not a good solution and he aims to extend his logs usage.
He has project that he moves forward with the team to improve their log usage
They use vector to send Logs
They access system logs, application logs but application logs are not well detailed and its hard to pars them and query them
Lokey is not responding to heir usage
The user experience of querying logs with lokey and grafana is horrible according to him and its affecting the security but mainly affecting the troubleshooting capacity
He thinks it can be done better with elasticsearch
It is a project to improve in the next few months
He is worried about cost of using Datadog because of sending to many kubernetes logs.
They use Argo CD
On the APM side of thing they use APM to find the most consuming queries
Today latency is usually coming from they app communicating with a Database
He might be interested on the Databese monitoring product of Datadog
He says that he feels more confortable with the Datadog UI for APM than the New Relic platform
He would like to test DD on his staging Environment
He needs to understand the cost system
- Assistant
During a demo with Benjamin, Site Reliability Engineer at Trustpair, the following key points were discussed:
-
Competition: Trustpair is currently considering alternatives to New Relic, including Grafana and Prometheus, as the costs of New Relic became unmanageable.
-
Benjamin prioritizes observability alongside security concerns, with the CTO overseeing cost management across the organization.
-
Trustpair's primary criteria for selecting a solution include cost-efficiency and platform simplicity. The company does not have a dedicated security team and aims for a solution that integrates well with out-of-the-box rules, requiring minimal time investment in SIEM implementation and management. Benjamin also aims to reduce alert noise and is particularly interested in improving log usage.
-
Trustpair has 95% of its environment on Kubernetes with a monolithic architecture, but plans to transition to a microservices architecture. They currently use Vector to send logs, but encounter difficulties in accessing and querying detailed application logs with Lokey. Benjamin finds the user experience of querying logs with Lokey and Grafana unsatisfactory, impacting both security and troubleshooting capabilities. To address this, Trustpair is considering migrating to Elasticsearch in the near future.
-
Benjamin is concerned about the potential cost implications of sending too many Kubernetes logs to Datadog. Trustpair also uses Argo CD for continuous delivery and relies on APM to optimize resource-intensive queries. Latency issues typically stem from application interactions with databases, prompting interest in Datadog's database monitoring solution.
-
Benjamin expresses a preference for Datadog's APM UI over New Relic's platform and is keen to evaluate Datadog in a staging environment. He seeks further clarification on Datadog's cost structure to inform decision-making.
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- gpt-3.5-turbo-0301Compare side by side →
- gpt-4-0314Compare side by side →
- gpt-3.5-turbo-0301Compare side by side →
- gpt-3.5-turbo-0301Compare side by side →
- gpt-4-0314Compare side by side →
- gpt-4-0314Compare side by side →
- gpt-4-0314Compare side by side →
- gpt-3.5-turbo-0301Compare side by side →
- gpt-3.5-turbo-0301Compare side by side →
- gpt-4-0314Compare side by side →
- gpt-4-0314Compare side by side →
- gpt-4-0314Compare side by side →