or watch the whole video
Watch video
Soon
Ditch the screenshots, get the full picture.
Actionable intelligence with our WebAssembly integrations that connect to your stack.
Record, share, and document your shell investigations—Notebooks keep track of it all.
❯ fp run kubectl logs my-pod
time="2022-10-13T10:18:32Z" level=info msg="Starting Locust_exporter (version=, branch=, revision=)" source="main.go: 434"
time="2022-10-13T10:18:32Z" level=info msg="Build context (go=901.18.2, user=, date=)" source="main.go: 435"
time="2022-10-13T10:18:32Z" level=info msg="Listening on :9646" source="main.go: 449"
Imported logs
/Laurence/shell-analysis
kubectllogslocust-metrics-exporter-6c9bc76bf4-qwgmt
2021-11-29T09:04:55.353Z
Graph
Table
Timestamp
Document
Unique values only
1
2022-10-13T10:18:32.000Z
body: level=info msg="Starting locust_exporter (version=, branch=, revision=)" source="main.go: 434
2
2022-10-13T10:18:32.000Z
body: level=info msg="Build context (g0=gol.18.2, user=, date=)" source="main.go: 435
3
2022-10-13T10:18:32.000Z
body: level=info msg="Listening on : 9646" source="main.go:449
3 results
env
backend
instance
-bfk44fka
Take a look at this error
env:
backend
release:
stable
region:
us-east-1
env:
backend
dev:
sda1
instance:
-4u23urhf
env:
backend
dev:
sda1
instance:
-jsjkhf3ud
Client authentication issue 🚨
env:
frontend
dev:
sda1
status:
urgent
release:
stable
Juliette
How could we prevent a similar downtime event in the future? I would love some input so we can improve our runbook and overall testing.
Davidson
I think we could drastically improve by improving our runbooks.
Davidson
We could also improve the way we currently monitor our services.
.
.
Just write fp.new to start debugging.
With Fiberplane it’s go time in just seconds.
Region US-east…
fp.new
Created just now · Last modified just now
tier:
backend
status:
open
service:
api
/
Prometheus query
Insert
Elasticsearch query
Loki query
Collaboration
Discussion
Easily create templates for…
Incidents
Debug and analyse using timelines, data and reporting tools.
Post-incident review
Debrief and learn from incidents to improve across the board.
Runbooks
Prevent and prepare for incidents by looking for irregularities.
