Skip to content

Commit 0b86673

Browse files
Merge pull request #280792 from guywi-ms/patch-119
Update diagnostics-linux-v3.md
2 parents 1016267 + ef68145 commit 0b86673

File tree

2 files changed

+2
-16
lines changed

2 files changed

+2
-16
lines changed

articles/virtual-machines/extensions/diagnostics-linux-v3.md

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -463,14 +463,7 @@ sinks | A comma-separated list of names of sinks to which individual log events
463463
facilityName | A syslog facility name, such as `"LOG_USER"` or `"LOG\LOCAL0"`. For more information, see the "Facility" section of the [syslog man page](http://man7.org/linux/man-pages/man3/syslog.3.html).
464464
minSeverity | A syslog severity level, such as `"LOG_ERR"` or `"LOG_INFO"`. For more information, see the "Level" section of the [syslog man page](http://man7.org/linux/man-pages/man3/syslog.3.html). The extension captures events sent to the facility at or above the specified level.
465465
466-
When you specify `syslogEvents`, LAD always writes data to a table in Azure Storage. The same data can be written to JSON blobs or Event Hubs or both. But you can't disable storing data to a table.
467-
468-
The partitioning behavior for the table is the same as described for `performanceCounters`. The table name is the concatenation of these strings:
469-
470-
* `LinuxSyslog`
471-
* A date, in the form "YYYYMMDD", which changes every 10 days
472-
473-
Examples include `LinuxSyslog20170410` and `LinuxSyslog20170609`.
466+
When you specify `syslogEvents`, LAD always writes data to a table named LinuxSyslogVer2v0 in Azure Storage. The same data can be written to JSON blobs or Event Hubs or both. But you can't disable storing data to a table.
474467
475468
### perfCfg
476469

articles/virtual-machines/extensions/diagnostics-linux.md

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -570,14 +570,7 @@ sinks | A comma-separated list of names of sinks to which individual log events
570570
facilityName | A syslog facility name, such as `"LOG_USER"` or `"LOG_LOCAL0"`. For more information, see *Values for facility* in the [syslog manual page](http://man7.org/linux/man-pages/man3/syslog.3.html).
571571
minSeverity | A syslog severity level, such as `"LOG_ERR"` or `"LOG_INFO"`. For more information, see *Values for level* in the [syslog manual page](http://man7.org/linux/man-pages/man3/syslog.3.html). The extension captures events sent to the facility at or above the specified level.
572572

573-
When you specify `syslogEvents`, LAD always writes data to a table in Azure Storage. The same data can be written to JSON blobs or Event Hubs or both. You can't disable storing data to a table.
574-
575-
The partitioning behavior for this table is the same as described for `performanceCounters`. The table name is the concatenation of these strings:
576-
577-
- `LinuxSyslog`
578-
- A date, in the form *YYYYMMDD*, which changes every 10 days
579-
580-
Examples include `LinuxSyslog20170410` and `LinuxSyslog20170609`.
573+
When you specify `syslogEvents`, LAD always writes data to a table named LinuxSyslogVer2v0 in Azure Storage. The same data can be written to JSON blobs or Event Hubs or both. You can't disable storing data to a table.
581574

582575
### sinksConfig
583576

0 commit comments

Comments
 (0)