Property reference

`sn.occ.log_ingestion.max_datainputs_per_mid`

The sn.occ.log_ingestion.max_datainputs_per_mid property sets the maximum number of data inputs that can stream logs to a single MID Server. Admins should adjust this value if they need to increase the number of integrations beyond the default limit of 10.

Default: Not stated
Type: Not stated
Application: Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do?	This property configures the maximum number of log streaming integrations allowed per MID Server, enabling better management of log ingestion.
What area does it affect?	MID Server configuration
What does the default mean?	No default value is stated in the ServiceNow documentation.
When should you review it?	Review this property when planning to increase log ingestion capacity or when configuring new integrations.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name	`sn.occ.log_ingestion.max_datainputs_per_mid`
Type	Not stated
Application	Not stated
Default value	Not stated
Description	Not stated

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs View supporting context

Context preview Snippet 1

... log ingestion. • No more than the default maximum of 10 integrations will stream logs to a single MID Server. You can modify the maximum number by adding the property sn.occ.log_ingestion.max_datainputs_per_mid to the MID Server and then changing the default value. To find out how many data inputs are streaming logs to the same MID Server, navigate to the Streaming Sources ...

More in `sn`

Other properties in the same namespace.

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.adm.ip_expansion_limit This property limits the expansion of global addresses into individual IPs, with options for no expansion, ful sn.adm.skip_k8s_nodes This property, when enabled, prevents ADM and ADME from reporting on processes and TCP connections for Kuberne sn.code.coverage.enabled This property enables or disables code coverage tracking, impacting how performance metrics are collected and

All 8 properties in sn →