________ ________
___ ________ ________ ______ ___ _____________ _________ __ ____ _______ _____ ___ _______ __ ________ __________ ____ __ __ _____ ___ __ _________ ___ __________
___ ________ ________ __ _ ______ ____ _________ ____ ______ ___ _____________ _________ __ ____ _______ ___ ______ __ ________ __________ ___ _________ ________ _____ ___ _______ ________ ___ _____ ___ _______ ____ ____ ____ _________ ___ ____ ____________
_____ ___ ________ _____ _____ ___ _______ ___ __ ________ ____ ______ __________ ____ __ ___ _____ _____ _________ ___ ________ _________ ___ ___ ________ ________ ___ _________ ___ __________ ___ ___________ __ ___ __________ ___ _____ _____ _________ ___ ________ _________
___ _______
__ ________ ___ ______ ____________ __ _____________ _________ ________ ___ ________ ________ __ ___ _______ ________ ___ _____________ __________
______ ______________
___ _________ _______ _____ ___ _______ _____________ __ ________ ________ ___ _______ ___ ______ _______ __ ____ __ _____ ___ _______ ____________
# Metrics + Events
signalfx:
access_token: "${SPLUNK_ACCESS_TOKEN}"
api_url: "${SPLUNK_API_URL}"
ingest_url: "${SPLUNK_INGEST_URL}"
# Use instead when sending to gateway (http forwarder extension ingress endpoint)
#api_url: http://${SPLUNK_GATEWAY_URL}:6060
#ingest_url: http://${SPLUNK_GATEWAY_URL}:9943
sync_host_metadata: true
____ ______ ___ ________ _________ _________ ____ ___ _______ ___ ____ __________ ____ ____ __ ____ ___ ___ ________ ________ __ __ ___ _________ ________
service:
pipelines:
metrics:
receivers: [signalfx]
processors: [memory_limiter, batch, resourcedetection]
exporters: [signalfx]
logs:
receivers: [signalfx]
processors: [memory_limiter, batch, resourcedetection]
exporters: [signalfx]
____ _________ _______ __ ____ ______
___ ______ ____________ __ _____________ _________ ________ ____ _________ _______ ________ ____ _______ ____ ___ _______ ___ ________ ______ __________No Content found for /db/organizations/splunk/repositories/portal-production/content/documents/ObservabilityCloud/metrics-and-metadata/histograms.dita#ddd768514e36c4330973a97f7e4b3d5a0/explicit-bucket-histograms ___ ____ ____________
SignalFx Exporter を使用してヒストグラムデータを Splunk Observability Cloud に送信するには、send_otlp_histograms オプションを true に設定します。例:
exporters:
signalfx:
access_token: "${SPLUNK_ACCESS_TOKEN}"
api_url: "${SPLUNK_API_URL}"
ingest_url: "${SPLUNK_INGEST_URL}"
sync_host_metadata: true
correlation:
send_otlp_histograms: true
_______ ______ _______
__ _______ ________ ______ ________ ___ ________ ________ ________ _ ______ __ _______ __ ________ ___ ____ __ _______ ________ __ _______ ___ ____ ____________
__ ________ _______ __________ ___ _______ _______ _________ ___ ___ _______________ _______ ___ ________
exporters:
signalfx:
include_metrics:
- metric_names: [cpu.interrupt, cpu.user, cpu.system]
- metric_name: system.cpu.time
dimensions:
state: [interrupt, user, system]
___ _________ _______ _________ ___ ________ __ ____ ____ ___ _____________ ______ ____ _ ___ _________ _____ ___ ____ ___ ____ ___ _________ ________ ________
exporters:
signalfx:
include_metrics:
- metric_name: "cpu.idle"
- metric_name: "cpu.interrupt"
dimensions:
cpu: ["*"]
____ __ _______ ________ __ _______
_______ ________ __ _______ __ ___ ________ ________ ___ ______ __ ___ __________________ _____ ___ _________ _______ _____ ___ ______ _______ __ ___ _____
# DefaultExcludeMetricsYaml holds a list of hard coded metrics that's added to the
# exclude list from the config. It includes non-default metrics collected by
# receivers. This list is determined by categorization of metrics in the SignalFx
# Agent. Metrics in the OpenTelemetry convention that have equivalents in the
# SignalFx Agent that are categorized as non-default are also included in this list.
exclude_metrics:
# Metrics in SignalFx Agent Format
- metric_names:
# CPU metrics.
- cpu.interrupt
- cpu.nice
- cpu.softirq
- cpu.steal
- cpu.system
- cpu.user
- cpu.utilization_per_core
- cpu.wait
# Disk-IO metrics
- disk_ops.pending
# Virtual memory metrics
- vmpage_io.memory.in
- vmpage_io.memory.out
# Metrics in OpenTelemetry Convention
# CPU Metrics
- metric_name: system.cpu.time
dimensions:
state: [idle, interrupt, nice, softirq, steal, system, user, wait]
- metric_name: cpu.idle
dimensions:
cpu: ["*"]
# Memory metrics
- metric_name: system.memory.usage
dimensions:
state: [inactive]
# Filesystem metrics
- metric_name: system.filesystem.usage
dimensions:
state: [reserved]
- metric_name: system.filesystem.inodes.usage
# Disk-IO metrics
- metric_names:
- system.disk.merged
- system.disk.io
- system.disk.time
- system.disk.io_time
- system.disk.operation_time
- system.disk.pending_operations
- system.disk.weighted_io_time
# Network-IO metrics
- metric_names:
- system.network.packets
- system.network.dropped
- system.network.tcp_connections
- system.network.connections
# Processes metrics
- metric_names:
- system.processes.count
- system.processes.created
# Virtual memory metrics
- metric_names:
- system.paging.faults
- system.paging.usage
- metric_name: system.paging.operations
dimensions:
type: [minor]
k8s metrics
- metric_names:
- k8s.cronjob.active_jobs
- k8s.job.active_pods
- k8s.job.desired_successful_pods
- k8s.job.failed_pods
- k8s.job.max_parallel_pods
- k8s.job.successful_pods
- k8s.statefulset.desired_pods
- k8s.statefulset.current_pods
- k8s.statefulset.ready_pods
- k8s.statefulset.updated_pods
- k8s.hpa.max_replicas
- k8s.hpa.min_replicas
- k8s.hpa.current_replicas
- k8s.hpa.desired_replicas
# matches all container limit metrics but k8s.container.cpu_limit and k8s.container.memory_limit
- /^k8s\.container\..+_limit$/
- '!k8s.container.memory_limit'
- '!k8s.container.cpu_limit'
# matches all container request metrics but k8s.container.cpu_request and k8s.container.memory_request
- /^k8s\.container\..+_request$/
- '!k8s.container.memory_request'
- '!k8s.container.cpu_request'
# matches any node condition but k8s.node.condition_ready
- /^k8s\.node\.condition_.+$/
- '!k8s.node.condition_ready'
# kubelet metrics
# matches (container|k8s.node|k8s.pod).memory...
- /^(?i:(container)|(k8s\.node)|(k8s\.pod))\.memory\.available$/
- /^(?i:(container)|(k8s\.node)|(k8s\.pod))\.memory\.major_page_faults$/
- /^(?i:(container)|(k8s\.node)|(k8s\.pod))\.memory\.page_faults$/
- /^(?i:(container)|(k8s\.node)|(k8s\.pod))\.memory\.rss$/
- /^(?i:(k8s\.node)|(k8s\.pod))\.memory\.usage$/
- /^(?i:(container)|(k8s\.node)|(k8s\.pod))\.memory\.working_set$/
# matches (k8s.node|k8s.pod).filesystem...
- /^k8s\.(?i:(node)|(pod))\.filesystem\.available$/
- /^k8s\.(?i:(node)|(pod))\.filesystem\.capacity$/
- /^k8s\.(?i:(node)|(pod))\.filesystem\.usage$/
# matches (k8s.node|k8s.pod).cpu.time
- /^k8s\.(?i:(node)|(pod))\.cpu\.time$/
# matches (container|k8s.node|k8s.pod).cpu.utilization
- /^(?i:(container)|(k8s\.node)|(k8s\.pod))\.cpu\.utilization$/
# matches k8s.node.network.io and k8s.node.network.errors
- /^k8s\.node\.network\.(?:(io)|(errors))$/
# matches k8s.volume.inodes, k8s.volume.inodes and k8s.volume.inodes.used
- /^k8s\.volume\.inodes(\.free|\.used)*$/
______ _______ _____ _______ __ ___________
___ ________ ________ __________ ___ ______ __ ________ __ ________ ____ ___ ________ _______ _ ___ _______ __ ____________ __ __________ ___ ______ ____ ________ _ ____ __ _ ____ __ ____ _______ __ ___________ __ ______ _____________ ______ ___ __________ ____ _____ __________ ___ _______________ ___ ___ ____ ______ _____ _______ _____ __ ___ _____ _______ ___ ____________
___ ___ ___________ _______ __ _______ ___ _______ __ _______ ___ ___________ __________ ____ ___________ __ ___ ___ _________ ________
-
_________ _________ ___ ____ ___ ___ ___ _________ ____ __ _____________________________ ________ __ _______ __ __________________________________ -
________ _______ ___ _____ _______ __ ____ ____ __ ___ ________ _ _______ __ ________ -
______________________ ___ ____ __ ____ _____ _ ______ _______ ____ __ ____ ____ ______ _____________ ___ _ _______ __ ________ -
_____________ _______ ____ ________ __ __ ____ __ _________ __ __ ________ -
_____________ _______ ______ __ ___________ _______ ____ ___ __ ________ ______ _______ ___ ________ ______ __ ________ -
____________ _______ ______ __ _______ ____ ____ __ ____ ___ ______ ___________ ________ _ __ ________ -
____________ _______ __ ___ __ ___ ___________ _______ __ ___________ __ _____ _____________ ________ -
____________ ___ ____ __ ____ _______ ________ __ _______ __ ________ -
_________________ ___ __________ __ _____ _________ _________ _ ______ __ ________ -
________________ ___ __________ ___ __ ___ _________ __ ____ ____ _____ __ ____ __ __________ _________ __ ___ ______ ________ _________________ ______________ _______________ ________________
___ ____ _______ __ ___ ________ ________
___________ _____ ___ ______ _______________
___ ___ _________________ _____ __ _________ _______ __ _______ ______ _______ __ ________ ____________ __ ___________ _____ ______ ______ _______ _________ __ __________ __________
___________ _____ _________ _____ ___ _________ ________
-
_________________ __________ _ ______ _______ _______ __ _________ ___________ -
_____________________ _______ _ ___ ______ ___ _________ __ ___ ___________ _____ -
_______________ _______ _____ ______ __ ___ __ ___ __ _____ ___ _________ ______ ______ -
_____________ _______ _ ___ ______ __ _ ____ __ ________ -
_____________ _______ _ ___ _____ ______ ___ _ _________ _________ ____ -
___________ ______ _ ________ _______ _____ __ _ _____ _______ -
________________ _____ __________ ___ _________ ________ __ _________ -
_____________ _____ ___ _______ ____ _ _____ _____ -
_______________ ______ _ ________ _____ _____ __ _ _____ _____ _______ -
_____________ ______ _ ________ ___ _____ __ _ _____ ___ _______ -
______________________ _______ __________ ___ _________ ________ __ _________ -
_______________ ________ _ _____ ______ ____ ____ _________ ____ -
_____________ ______ _ _____ ______ ____ ________ ___ ____ ___ _ _________ __________
デフォルトの変換ルールと生成されたメトリクス
SignalFx エクスポータは、デフォルトで translation/constants.go で定義された変換ルールを使用します。
デフォルトのルールは、Infrastructure Monitoring に直接レポートされるメトリクスを作成します。その属性または値を変更する場合は、変換ルールまたはその構成要素であるホストのメトリクスを変更する必要があります。
デフォルトでは、SignalFx エクスポータは、ホストメトリクスレシーバーから以下の集約メトリクスを作成します。
-
cpu.idle -
cpu.interrupt -
cpu.nice -
cpu.num_processors -
cpu.softirq -
cpu.steal -
cpu.system -
cpu.user -
cpu.utilization -
cpu.utilization_per_core -
cpu.wait -
disk.summary_utilization -
disk.utilization -
disk_ops.pending -
disk_ops.total -
memory.total -
memory.utilization -
network.total -
process.cpu_time_seconds -
system.disk.io.total -
system.disk.operations.total -
system.network.io.total -
system.network.packets.total -
vmpage_io.memory.in -
vmpage_io.memory.out -
vmpage_io.swap.in -
vmpage_io.swap.out
集約されたメトリクスに加えて、デフォルトのルールでは、以下の「コアごとの」カスタムホストメトリクスが利用可能です。CPU 番号はディメンション cpu に割り当てられます。
-
cpu.interrupt -
cpu.nice -
cpu.softirq -
cpu.steal -
cpu.system -
cpu.user -
cpu.wait
____ _________ _______
__ ____ __ ____ ___________ ________ ________ _________ _______ _____ __ _______ __ ____ _________ ________ ___ ______________________ __ _____
____ ______________________ __ __________ _________ _______ ___ _______ _______ __ _____ __________ __ __________ ____ ___ _______ _______ ____ __________ ____ _____ _______ _____ ___ ____ ___ ____ _______ ___ _________
________
___ _________ _____ _____ ___ _____________ _______ ___ ___ ________ _________
________________________ _______ __ ______ _____ _ ________ ________ ____ ___ ____ ________ ____ ___ ___ ________ ________ ____ ___ ________ ________ ____ __________ ____ ________
_______________
If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.
Available to Splunk Observability Cloud customers
-
Submit a case in the Splunk Support Portal.
-
Contact Splunk Support.
Available to prospective customers and free trial users
-
Ask a question and get answers through community support at Splunk Answers.
-
Join the Splunk community #observability Slack channel to communicate with customers, partners, and Splunk employees worldwide.