Logfire ACTION
Record Log Entry
Records a single log entry or event in Logfire as a zero-duration span, via OTLP ingestion. Use this whenever the user wants to log, record, or note an event, deployment, incident, or error — this is Logfire's equivalent of calling
logfire.info()/logfire.error() from the SDK. This creates a single point-in-time entry, not a full distributed trace with parent/child spans. Setting exceptionType/exceptionMessage marks the entry as an exception (is_exception = true when later queried). After recording, use Run SQL Query to confirm what was written (e.g. SELECT * FROM records WHERE message LIKE '%...%' ORDER BY start_timestamp DESC LIMIT 1). See the documentation- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Logfire account once, then configure and run Record Log Entry from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "logfire-record-log-entry",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
logfire: { authProvisionId: "apn_xxxxxxx" },
message: "Message",
level: "Level",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "logfire-record-log-entry",
"configured_props": {
"logfire": { "authProvisionId": "apn_xxxxxxx" },
"message": "Message",
"level": "Level"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "logfire",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "logfire-record-log-entry",
arguments: {
message: "Message",
level: "Level",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
message Message | string | The log message to record, e.g. Deployment v2.4.1 went out successfully. Required |
level Level | string | The severity level of the log entry. Optional |
spanName Span Name | string | A short name for the span, used to group similar entries. Defaults to the message if not provided. Optional |
serviceName Service Name | string | The name of the service this log entry is attributed to. Optional |
attributes Attributes | string | Optional JSON object of additional key-value attributes to attach to the entry. Example: {"customer_id": "12345", "region": "us-east"}. Optional |
exceptionType Exception Type | string | If this entry represents an exception, the exception's type/class name, e.g. ValueError. Optional |
exceptionMessage Exception Message | string | If this entry represents an exception, the exception's message. Setting this (with exceptionType) marks the span as an exception in Logfire. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- logfire-record-log-entry
- Version
- 0.0.2
- App
- Logfire
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗