Gain operational intelligence by collecting, indexing, and visualizing data using a powerful on-premises engine for actionable insights.
Release NotesCollect, index, and visualize your data in the cloud for better operational intelligence.
Release NotesDiscover, share, and install apps and add-ons with the Splunk community on Splunkbase. Publish your own or add others to your Splunk platform instance.
Gain operational intelligence by collecting, indexing, and visualizing data using a powerful on-premises engine for actionable insights.
Release NotesStreamline your security operations with a SOAR system that integrates orchestration, playbook automation, and case management to enhance threat response.
Prevent disruptions and optimize operations when you monitor and analyze your IT service with predictive analytics and machine learning.
Release NotesCollect, index, and visualize your data in the cloud for better operational intelligence.
Release NotesGain end-to-end visibility, troubleshoot in real-time, and optimize performance across infrastructure, applications, and user interfaces.
Release NotesCloud-based application performance monitoring with AI-powered insights for hybrid and multi-cloud environments.
Release NotesSelf-hosted application observability for regulated and sensitive environments.
Release NotesPre-packaged, self-contained application monitoring solution based on modern Kubernetes architecture.
Release NotesBuild and deliver apps and integrations with SDKs, APIs and tools.
Access and share apps and add-ons with the Splunk community on Splunkbase. Publish your own apps, or download and install others on your Splunk platform instance.
Explore information on best practices, connect with community, or contact support.
Run a Collector on a standalone host under the OpAMP Supervisor to use additional Fleet Management remote configuration capabilities.
This setting associates OpAMP data with the same environment as your APM data. In the Collector configuration file, add deployment.environment.name under service::telemetry::resource::attributes
For example, if you use the default agent Collector configuration on Linux at /etc/otel/collector/agent_config.yaml, enable this by following the comments for deployment.environment.name as mentioned in the following configuration snippet:
service:
telemetry:
resource:
attributes:
- name: otelcol.service.mode
value: agent
# Optional: Add a deployment environment to the Collector's internal telemetry.
# To use the deprecated attribute, change the key to "deployment.environment".
- name: deployment.environment.name
value: staging