Files
nexus/sreweekly/markdown/81/04-from-scala-unified-logging-to-full-system-observability-part-1-of-3-ou.md
2026-09-12 17:23:01 +08:00

16 lines
1.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# From Scala Unified Logging to Full System Observability — Part 1 of 3: Our Original State of Logging
- **期号**: SRE Weekly Issue #81(2017-07-16)
- **作者**: This article is published by my sponsor, VictorOps, but their sponsorship did not influence its inclusion in this issue.
- **链接**: https://victorops.com/blog/from-scala-unified-logging-to-full-system-observabilitypart-1-our-original-state-of-logging/
## 简介
> Jonathan is a platform engineer at VictorOps, responsible for system scalability and performance. This is Part 1 in a 3-part series on system visibility, the detection part of incident management.
## 正文
VictorOps is now Splunk On-Call — new name, updated product. With Splunk On-Call, developers, devops and operations teams make on-call suck less while reducing mean time to acknowledge and restore outages. Teams receive context-rich notifications and collaborate cross-functionally to empower fast, efficient incident resolution with reduced downtime. Stakeholders can gain visibility to critical incidents and steps taken to resolve incidents.
Sign into your Splunk On-Call account, get user support or explore our other resources to learn more.