sn.adm.skip_k8s_nodes The sn.adm.skip_k8s_nodes property determines whether process and TCP connection reporting is skipped on Kubernetes nodes. When set to true, this property enhances performance by reducing reporting overhead, which may be important for environments heavily utilizing Kubernetes.
trueThe answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This property, when enabled, prevents ADM and ADME from reporting on processes and TCP connections for Kubernetes nodes, optimizing resource usage. |
|---|---|
| What area does it affect? | Kubernetes monitoring |
| What does the default mean? | The default value is "true", which means this behavior is enabled by default. |
| When should you review it? | Review this property when adjusting monitoring settings for Kubernetes environments or troubleshooting performance issues. |
Raw metadata from the property record.
| Property name | sn.adm.skip_k8s_nodes |
|---|---|
| Sys ID | d7b7cbf63b610b10cbf3bb9c24e45afe |
| Type | boolean |
| Application | Global |
| Default value | true |
| Description | When true, ADM and ADME skips process and TCP connection reporting on Kubernetes nodes (hosts running kubelet). Set to false to restore legacy behavior. |
| Updated | 2026-06-22 06:23:17 |
Official references and nearby text excerpts where this property appears.
snOther properties in the same namespace.
sn.adm.ip_expansion_limit
This property limits the expansion of global addresses into individual IPs, with options for no expansion, ful
sn.code.coverage.enabled
This property enables or disables code coverage tracking, impacting how performance metrics are collected and
sn.dt.activity_stream.allow_list
This property defines a comma-separated list of tables that allow translation of comments and work notes in ac
sn.dt.activity_stream.block_list
This property defines a comma-separated list of tables that will not have their comments and work notes transl
sn.metadata.tracing.enabled
This property determines whether metadata tracing is active, impacting how changes are logged and monitored in
sn.metadata.tracing.table.records.expiration.days
It sets the retention period for traced metadata records to a specified number of days, with a default of 90 d
sn.occ.log_ingestion.max_datainputs_per_mid
This property configures the maximum number of log streaming integrations allowed per MID Server, enabling bet