skills.rest
rcmaples
rcmaplesCOMMUNITY
Explore all skills by this author →
GitHub

fullstory-logging

Emit string messages to Fullstory session replay via FS('log', { level, msg }).

Updated Dec 20, 2025
Search Tags:#debugging#web development#logging#session replay#Fullstory#logging best practices
One-click install
npx skills add https://github.com/rcmaples/btx --skill fullstory-logging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fullstory-logging
Source: https://github.com/rcmaples/btx/tree/main/.claude/skills/fullstory-logging
Command: npx skills add https://github.com/rcmaples/btx --skill fullstory-logging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured logging approach by sending messages to Fullstory's session replay, enabling developers to view contextual information alongside user sessions.

Core Features & Use Cases

  • In-session debugging: Add log messages that appear in Fullstory session replay without polluting the browser console.
  • Error and event context: Attach error details, user actions, and state context to aid troubleshooting.
  • Operational visibility: Use logs for auditing and monitoring important workflows in production and development.

Quick Start

Example: Load the Fullstory SDK on your site and emit logs with FS('log', { level: 'info', msg: 'User action observed' }). For instance, log an API response time or a user interaction to enrich session replay.

Frequently Asked Questions about fullstory-logging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I attach contextual logs to Fullstory session replays?▼

You can capture errors and user actions for in-session debugging by emitting log messages directly via the Fullstory API using FS('log', { level: 'error', msg: '...' }). This attaches contextual details to session replays to aid troubleshooting.

Can I add logs to session replays without polluting the browser console?▼

Yes, you can log API response times or user interactions to enrich session replay by emitting messages through the Fullstory API. This provides operational visibility and auditing capabilities for important workflows in both development and production environments.

Does Fullstory logging work for production monitoring and development?▼

Fullstory logging works for both production monitoring and development environments. It captures contextual logs, errors, and user actions by applying the FS('log', { level, msg }) API to web applications, providing operational visibility across different stages.

What is the best way to capture user action context in session replay?▼

The best way to capture user action context in session replay is to emit structured string messages via the Fullstory API. Using FS('log', { level, msg }) attaches specific error details and state context directly to the user's session for troubleshooting.

Do I need console logging to use Fullstory session replay logs?▼

No, you do not need console logging to use Fullstory session replay logs. The integration satisfies logging requirements by emitting string messages directly via the FS('log', { level, msg }) API, keeping the browser console clean while maintaining operational visibility.

Related Skills

Explore More Software Engineering Skills→
PostHogPostHog
58

logs-python

Send structured Python logs to PostHog via OpenTelemetry OTLP exporter.

Official
Intermediate
jiten-singh-shahijiten-singh-shahi
13

sf-debugging

Diagnose Salesforce runtime errors and analyze debug logs.

Community
Intermediate
anouar1991anouar1991
1

console-intelligence

Capture and categorize console output with source attribution and deduplication.

Community
Advanced
mgd34msumgd34msu
4

logrocket

Implement session replay and error tracking for React applications with LogRocket.

Community
Intermediate