Download the PHP package pushinbr/pam-native-observability without Composer
On this page you can find all versions of the php package pushinbr/pam-native-observability. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download pushinbr/pam-native-observability
More information about pushinbr/pam-native-observability
Files in pushinbr/pam-native-observability
Package pam-native-observability
Short Description Vendor-neutral traces, metrics, logs and crash context for PAM Native.
License Apache-2.0
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package pam-native-observability
Why PAM Native Observability
Instrument PHP, Rust, and native boundaries with redacted, bounded telemetry that can be exported to the backend of your choice. The public API is strictly typed for PHP 8.5; expensive or frame-sensitive work stays in Rust or the platform SDK instead of crossing the application boundary every frame.
| Best for | A focused capability you can add to any PAM Native application |
| Native path | OpenTelemetry-compatible native pipeline |
| Application model | Composer package + generated native integration |
| Design rule | Independent module; no feed, vertical, or application template bundled |
What you can build
- Cross-layer performance tracing
- Crash and error correlation
- Production health dashboards and SLO evidence
Quick start
Already have a PAM Native project? Add only this capability:
New to PAM? Follow the five-minute PAM Native setup once, then return here. Your application stays a normal Composer project with a committed lockfile.
See it in action
Vendor-neutral, dependency-light spans, structured logs, counters, gauges, crash context, deterministic sampling, bounded batching, and pluggable export for PAM Native apps. The default HTTPS transport works with a collector or ingestion gateway; implement TelemetryTransport for Sentry, Datadog, Honeycomb, New Relic, or an offline spool.
Continue a PAM Server trace from its validated response header without inventing a new root:
Only lowercase W3C version 00 contexts with nonzero trace/span identifiers
are accepted. Native creates a distinct child span, preserves trace flags and
does not enqueue children of an unsampled remote context. tracestate remains
unsupported until a vendor allowlist and bounded forwarding policy exist.
The queue is bounded and drops the oldest signals under backpressure. Failed exports are restored to the front of the queue. Secrets and personal data are never collected automatically; applications explicitly choose context and attributes.
Certified OTLP export
WireProtocol::OtlpHttpJson maps each signal to the matching OpenTelemetry
Protocol endpoint instead of relabeling PAM's original envelope:
| PAM signal | OTLP payload | Endpoint |
|---|---|---|
| Span | resourceSpans |
/v1/traces |
| Log and crash context | resourceLogs |
/v1/logs |
| Counter and gauge | resourceMetrics |
/v1/metrics |
Counters use delta temporality; integer and floating-point points keep their
wire types. Log severity and span status are translated at the external OTLP
boundary, while PAM's public enums remain sequential integers beginning at
1. Batches never mix signal families, and any transport or encoding failure
restores the complete batch to the bounded queue.
Remote endpoints require HTTPS. Loopback HTTP is accepted only for local
Collector development and certification. The cURL transport refuses redirects
to HTTP, limits response bodies to 64 KiB, and treats OTLP partialSuccess
rejections as failed delivery.
The official-Collector contract is reproducible:
CI verifies the Collector's Sigstore identity and immutable image digest before testing traces, logs, counters, gauges, parent span lineage, and exception-data redaction.
What installation does
pam add observability resolves the official compatible package, performs a non-mutating Composer preflight, updates the normal composer.json and composer.lock, refreshes generated native integration when required, and leaves the project ready for pam doctor validation.
Use pam packages to inspect availability and pam remove observability to uninstall the capability safely. Direct Composer commands are an advanced interoperability path; PAM is the supported application workflow.
API guide
| API | Responsibility |
|---|---|
Observability |
Create spans, logs, counters, gauges, crash context, and flush batches. |
ObservabilityConfig |
Set endpoint, service identity, sampling, queue, and batch policy. |
WireProtocol |
Select compatible PAM JSON (1) or OTLP/HTTP JSON (2). |
Span / SpanStatus |
Capture timed operations, status, attributes, and exceptions. |
TraceContext |
Validate a W3C version 00 parent and continue its sampling/lineage. |
TelemetryTransport |
Implement vendor, collector, gateway, or offline delivery. |
CurlTelemetryTransport |
Send batches through the dependency-light default HTTPS transport. |
Severity / SignalKind |
Typed log severity and signal categories. |
All coded states, kinds, and variants are sequential integer-backed enums. Use enum cases in application code; do not depend on raw wire numbers.
Production checklist
- Send remote telemetry only to HTTPS endpoints you control or explicitly trust.
- Define an attribute allowlist and never attach secrets or personal data by default.
- Keep
captureExceptionDetailsdisabled unless users consent to messages, source paths, line numbers, and stack traces leaving the device. - Flush on lifecycle transitions without blocking the UI indefinitely.
- Monitor dropped-signal counters and tune bounded queues from evidence.
- Run
pam doctor,pam test, and a signed release build on every supported platform. - Exercise denial, cancellation, backgrounding, process restart, and offline behavior before release.
Troubleshooting
- Nothing is exported: verify endpoint, sampling decision, and explicit
flush(). - Batches retry forever: make the transport surface permanent versus transient failures.
- Signals disappear under load: inspect queue capacity and dropped-signal diagnostics.
- Native integration is stale: run
pam doctor --fix, rebuild the native host, and inspect the first reported diagnostic.
Compatibility and support
This package targets PAM Native 0.8.x, Android API 26+, and iOS 15+ unless a platform-specific section above states a stricter requirement. Platform SDKs, credentials, entitlements, physical hardware, and store configuration remain application responsibilities.
Security vulnerabilities should be reported through the repository security policy or GitHub private vulnerability reporting, not a public issue.
