@catmanyau Also, in Trace0, a Transaction contains the full trace along with all logs correlated with that trace.
Full details here: https://t.co/jh7tojnQpP
During production incidents, it is important to quickly understand who was affected and which requests were involved.
Trace0's new Triggered Alerts section brings this context together for each alert, and makes it available to agents through our MCP server.
When an alert is triggered, you need to quickly understand what happened and who was affected.
Our new Triggered Alerts section shows you the affected users and requests that contributed to the alert.
Full details here: https://t.co/Tu9IJXvSSs
@catmanyau The get_triggered_alert_detail tool returns a summary of each trace involved (ID, timestamp, endpoint name, status code), along with the tags involved (e.g. user ID). Your agent can then use get_transaction_detail to retrieve the full details of any of those transactions.
Trace0 is built around a decade of experience working with observability in production systems and seeing what worked well and what didn't.
One of Trace0โs design principles is to make it easy for engineering teams to adopt observability best practices by default!
More telemetry doesn't necessarily mean better observability.
In our latest post, we look at some of the most common observability mistakes we've seen and how to avoid them.
https://t.co/gb7TCb1Rn8
When debugging an issue, knowing which service, region or host was involved is useful.
But often you need to know who or what was affected, such as a customer, order or tenant.
That's why we've added Tags to Trace0, letting you attach business context directly to transactions!
Infrastructure info tells you where something happened. Business context tells you what was affected.
You can now add tags to Trace0 transactions.
Tags let you attach important business context to transactions, such as a customer ID, order ID, etc.
https://t.co/pv58T1gUlp
One of the biggest challenges with AI-assisted debugging isn't the modelโit's the context.
In Trace0, every log entry links to its corresponding Transaction, giving your AI the full request context instead of just a single log line.
That's the idea behind the Trace0 MCP server.
Connect @claudeai, @cursor_ai, and other AI agents directly to Trace0.
We've released the Trace0 MCP server.
Your AI agents can now query your traces, logs and metrics to investigate errors, analyse performance, and troubleshoot issues faster.
https://t.co/kzC8ZJXMp1
Asynchronous messaging doesn't fit neatly into a trace tree.
Consumers can run later. They can process batches. They can have multiple upstream producers.
That's why Trace0 takes a different approach.
Where did this message come from?
Did any downstream consumers fail?
Trace0 makes it easy to answer both with Produced By and Consumed By sections for asynchronous messaging.
Perfect for Amazon SQS and other message-driven architectures.
https://t.co/5nBC6Plpzt
I've used a lot of observability tools over the years, but I always felt they were too complex, too expensive, or both.
So I built Trace0.
OpenTelemetry-native. Simple to use. Affordable.
I'd love to hear what you think!
๐ We're live!
Observability shouldn't be complex or expensive.
Trace0 brings traces, logs, metrics and alerting together in a single platform, without the complexity or cost of traditional observability tools.
7-day free trial:
https://t.co/eRH5voMsmt
๐ We're live!
Observability shouldn't be complex or expensive.
Trace0 brings traces, logs, metrics and alerting together in a single platform, without the complexity or cost of traditional observability tools.
7-day free trial:
https://t.co/eRH5voMsmt
We are excited to share our latest blog post about the new addition to our assessment library - a specialized @reactjs Redux assessment! This assessment enhances your ability to spot the perfect match for your React developer roles.
https://t.co/96xuRoB2qi
We now support custom assessments in @elmlang with automated grading!
With this update, you can now create tailored Elm assessments to identify the best Elm developers applying to your company.
https://t.co/HLbXjBeAIH
We are excited to announce the addition of a new QA assessment to our library. With this update, you can now use our QA assessment to identify the best candidates for your QA Engineer and SDET positions.
https://t.co/6nILrTcI4S
We now support custom assessments in @sveltejs with automated grading!
With this update, you can now create tailored Svelte assessments to identify the best Svelte developers applying to your company.
https://t.co/jXdQpdslCG
#FrontEndDeveloper#frontend#hiring
I have participated, and struggled, in many live coding interviews down through the years when applying for roles.
I never felt my performance in them accurately represented how I would perform on the job, so I'm excited for @code_screen's latest feature!
Live Coding interviews are stressful experiences for candidates, especially for people who struggle with severeย Interview Anxiety.
Click below to see how our new Live Coding with Context feature makes live interviews fairer for candidates. ๐
https://t.co/yOe2PPh74Z
It's been awesome working with the team at @codeablehq over the last 18 months.
Proud to see @code_screen contributing to their fair & inclusive hiring process!
Another happy customer! ๐ @codeablehq , an exclusive marketplace to hire vetted WordPress developers, reduces unconscious bias while saving up to 40 hours per month when screening candidates with CodeScreen.
Click the link below to see how!๐
https://t.co/ggw8FfZz4q