- What is okvpn/datadog-orocrm used for?
- It provides Datadog monitoring integration for OroCRM and OroPlatform applications, adding configuration and instrumentation to forward application metrics, logs, and events to Datadog. Teams use it to track performance, errors, and usage in Datadog dashboards and alerts. It is distributed as a Composer package.
- How do I install okvpn/datadog-orocrm with Composer?
- Install it through Composer using the package name, then review the published configuration before enabling instrumentation. The assessment indicates standard package discovery, route registration, configuration publishing, and storage integration fit a Laravel/PHP stack. Confirm the exact install and setup steps in the README, because the provided context does not include full installation commands.
- Is okvpn/datadog-orocrm compatible with Laravel?
- The package targets OroCRM and OroPlatform rather than being a native Laravel package, but the assessment evaluates it through familiar Laravel routing, middleware, storage, and policy conventions. Confirm Laravel and PHP version constraints, package discovery, route registration, and route-cache behavior before adopting it. Do not assume Laravel support from the package name alone.
- What security issue is in okvpn/datadog-orocrm 0.2.1?
- Release 0.2.1 adds a route that allows artifact download without authorization, which the assessment calls a material security-relevant capability rather than a routine feature. As-is, it shifts the package toward potentially public artifact serving unless the route is opt-in, constrained by signed URLs or opaque identifiers, and isolated from private or tenant storage. Treat 0.2.1 as a security review gate, not a drop-in upgrade.
- Does the unauthenticated download route use signed URLs or UUIDs?
- The provided assessment does not specify whether the route uses signed URLs, random UUIDs, or sequential IDs. It explicitly lists identifier strategy and signing as key questions to verify. Review the package source and route definitions before enabling the route, especially for private or tenant-scoped artifacts.
- Can I disable the public artifact download route?
- The assessment says feasibility depends on whether the route is auto-registered and whether it can be disabled through configuration, middleware, or route guards. It recommends running route:list to identify the route URI pattern, middleware, and name. Do not enable public downloads until you confirm the route can be restricted or disabled for your artifact class.
- How should I test okvpn/datadog-orocrm before production?
- Start in a non-production environment and review the published config and route registration. Run route:list to identify the new route and confirm middleware, route prefixes, and behavior under route:cache. Test enumeration resistance, authorization bypass, cross-tenant access, rate limiting, logging, and storage visibility before gating production enablement on security sign-off.
- Does okvpn/datadog-orocrm support multi-tenant OroCRM setups?
- The assessment says fit is weaker for multi-tenant or regulated environments unless the public route is explicitly scoped and controlled. It flags artifact status, tenant ownership, storage-disk visibility, and cross-tenant access as controls to verify. For private-artifact use cases, do not enable the public route without compensating controls.
- What alternatives exist for Datadog monitoring in OroCRM?
- The context does not name alternative packages, so evaluate Datadog's official agents, APM integrations, and log-forwarding options alongside native OroCRM monitoring. Compare support for your OroCRM and PHP versions, tenancy model, and required metrics, logs, and events. For Laravel-style stacks, also consider framework-native logging and metrics pipelines.
- Is okvpn/datadog-orocrm actively maintained?
- The package is early-stage at 0.2.x, and the assessment says maintenance and upstream support should be treated as risks until release cadence and security responsiveness are proven. Pin the current version and review release notes before upgrading. Confirm PHP and platform compatibility and whether security fixes are published promptly.