The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

What a local Apex runtime sends off the machine, and what it keeps (opens in a new tab)

You will know where Apex source, test data and licence details go when renmy runtime runs, which settings turn telemetry off, and how it works offline and air-gapped.

Why read this

It is the questionnaire answers a security or procurement team will ask for.

Org-based test runs

  • Each test run deploys to a Salesforce org
  • Test data sits in the org sandbox
  • Each developer needs an org credential

Local runtime

  • Tests run on the developer's machine
  • Test data lives in an in-process database
  • Test runs need no org or credential
Where Apex runs and where data lives, before and after a local runtime

This vendor-written piece, published by Renmy UG of Berlin, gives security and procurement teams the answers they need for a questionnaire about renmy runtime, a local Apex runtime formerly called Nimbus. It executes Apex, SOQL, DML and Salesforce Flows on a developer’s machine against an embedded PostgreSQL, without an org, Docker or a JVM. Apex source is read locally and sent to no one. Tests run against schema read from the project’s metadata, so they need no connected org, and test data sits in an in-process database with no open network port, rolled back after each test.

The article then sets out what leaves the machine. The Free tier needs no network access. By default the runtime sends one privacy-minimal activation event to an EU-hosted service, which excludes code, paths, test names and record data. Pro licences also record one de-duplicated activation from headless CI. Either can be switched off with a single setting or environment variable. Pro and Team licence checks send the licence key to the Keygen licensing API, at most once a day. Activating a machine with renmy login also sends a hashed installation ID, hostname, display name, OS, architecture, CPU core count and account ID. Licences are cached for offline use for up to seven days.

For disconnected networks, the article says the binary can be copied into place without internet access, since the database engine is embedded, and the daily update check can be disabled. Enterprise customers can have licence validation on premises, with pricing from $20,000 a year. A command-by-command table lists what each command contacts. The Salesforce org remains the system of record and deployment target. The deploy flow validates the same payload in the org before deploying, and Pro release commands produce signed receipts for auditors.

The piece closes with a list of documents to attach to the questionnaire, including the security page, data processing addendum, subprocessor list and licence terms. It also gives pricing: Free at $0, Pro and Team free during the public beta with listed prices of $19 and $49 per month, and Enterprise on a custom contract.

Read the original at dev.to (opens in a new tab)

Worth reading?

Optimizing Apache Spark workloads at scale using telemetry and evidence-based tuning (opens in a new tab)

You will learn how to collect execution telemetry without modifying application code and validate resource sizing changes against runtime and reliability metrics before production rollout.

The Salesforce engineering team addressed inefficient compute allocation across millions of daily Apache Spark jobs by shifting from success-based metrics to evidence-driven resource sizing. They identified that successful job completion often masks unused capacity, pod churn, and unnecessary executor allocations.

To gather comparable measurements without altering customer applications, the team instrumented a shared submission gateway using open-source listener hooks. These listeners exported structured telemetry through Kafka into a curated analytical layer, which standardized metrics for applications, jobs, stages, and executors while explicitly tracking missing data and retry semantics.

The team used the modeled data to distinguish between genuine waste and underlying bottlenecks like shuffle failures or memory pressure. By testing targeted reductions in initial executors and maximum limits, they validated changes against p95 runtime, spill rates, and platform health indicators. The adjustments yielded a thirty-one percent weekly compute cost reduction without degrading performance or increasing failures.

Read the original at Salesforce Engineering (opens in a new tab)

Worth reading?

Recommended

How Agentforce Health Monitoring detects silent failures and reduces alert latency (opens in a new tab)

You will learn how Agentforce Health Monitoring unifies fragmented telemetry to detect silent availability failures and reduce alert latency to under two minutes.

Why read this

The piece explains the current debugging workflow and outlines upcoming capabilities for automated root cause analysis and remediation.

Agentforce Health Monitoring addresses the gap where traditional dashboards show healthy status while users actually receive no end-to-end response. The system tracks over sixteen built-in metrics including error rates, escalation rates, engagement, and latency, with plans to add cost, time-to-first-token, and RAG quality signals. Its primary goal is proactive visibility that connects alerts directly to the relevant session context.

The engineering team solved a major fragmentation problem by consolidating signals scattered across five or six separate systems. By converting data ingestion to streaming and simplifying query complexity, they accelerated metric evaluation. This optimization reduced the time from a threshold breach to administrator notification from approximately twenty minutes to several minutes, targeting an investigation start time under two minutes.

Operational workflows now emphasize actionable debugging rather than simple detection. Administrators can drill down from an alert to examine specific reasoning steps, tool calls, or flow configurations that caused a failure, and they can define custom thresholds like token usage limits. Looking ahead, the roadmap includes runtime insight agents to suggest fixes and fully automated remediation pipelines that apply approved solutions without manual intervention.

Read the original at Salesforce Engineering (opens in a new tab)

Worth reading?

Recommended

Connecting metadata and runtime telemetry to prioritize enterprise org remediation (opens in a new tab)

Readers will learn how Salesforce Engineering correlates configuration metadata with production telemetry to identify and prioritize implementation anti-patterns.

Why read this

The piece outlines the architectural patterns used to standardize hundreds of health signals and expose them through headless APIs.

Salesforce Engineering addressed the challenge of monitoring enterprise org health at scale by moving beyond static reports to an in-app experience called Salesforce Health Insights. The team needed to correlate point-in-time configuration metadata with continuously changing runtime telemetry across systems that lack shared identity models.

To solve this, they built a harmonization layer that reconciles fragmented datasets and maps runtime activity to individual metadata components while accounting for traffic volume and seasonality. This architecture maintains clear boundaries between deterministic findings and external operational context, preserving data origin and freshness information.

The initiative expanded from roughly one hundred initial security signals to over four hundred covering process automation, customization, and agentic readiness. Each signal follows standardized metadata rules and remediation guidance derived from the Salesforce Well-Architected Framework and known system hotspots.

Findings are prioritized using operational context such as application CPU usage and peak business hour traffic to determine criticality and required effort. The system uses a headless schema that emits raw JSON for any user interface or agent, supports an MCP interface, and can deliver summaries directly to Slack channels.

Read the original at Salesforce Engineering (opens in a new tab)

Worth reading?