Skip to content

Updated documentation for OshiSysMonitor#14799

Closed
hardikbajaj wants to merge 0 commit intoapache:masterfrom
hardikbajaj:master
Closed

Updated documentation for OshiSysMonitor#14799
hardikbajaj wants to merge 0 commit intoapache:masterfrom
hardikbajaj:master

Conversation

@hardikbajaj
Copy link
Copy Markdown
Contributor

@hardikbajaj hardikbajaj commented Aug 11, 2023

Fixes #14359

Description

Updates documentation for OshiSysMontior

Fixed the bug ...

Renamed the class ...

Added a forbidden-apis entry ...

Release note


Key changed/added classes in this PR

This PR has:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • a release note entry in the PR description.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

@hardikbajaj
Copy link
Copy Markdown
Contributor Author

I didn't noticed wrong formatter formatted this file on my local :( . I'll get back with updated documentation

The `taskIngestionMode` dimension includes the following modes:
* `APPEND`: a native ingestion job appending to existing segments
The `taskIngestionMode` dimension includes the following modes:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you revert this formatting change?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This blank line is coming again with auto formatting. Do you want me to remove this ?



You can configure Druid to [emit metrics](../configuration/index.md#enabling-metrics) that are essential for monitoring query execution, ingestion, coordination, and so on.
You can configure Druid to [emit metrics](../configuration/index.md#enabling-metrics) that are essential for monitoring
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
You can configure Druid to [emit metrics](../configuration/index.md#enabling-metrics) that are essential for monitoring
You can configure Druid to [emit metrics](../configuration/index.md#enabling-metrics) that are essential for monitoring query execution, ingestion, coordination, and so on.


You can configure Druid to [emit metrics](../configuration/index.md#enabling-metrics) that are essential for monitoring query execution, ingestion, coordination, and so on.
You can configure Druid to [emit metrics](../configuration/index.md#enabling-metrics) that are essential for monitoring
query execution, ingestion, coordination, and so on.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove line 27.

### Router
|Metric|Description|Dimensions|Normal value|

|Metric|Description|Dimensions|Normal Value|
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
|Metric|Description|Dimensions|Normal Value|
|Metric|Description|Dimensions|Normal value|

#### Memcached only metrics

Memcached client metrics are reported as per the following. These metrics come directly from the client as opposed to from the cache retrieval layer.
Memcached client metrics are reported as per the following. These metrics come directly from the client as opposed to
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Memcached client metrics are reported as per the following. These metrics come directly from the client as opposed to
Memcached client metrics are reported as per the following. These metrics come directly from the client.


Memcached client metrics are reported as per the following. These metrics come directly from the client as opposed to from the cache retrieval layer.
Memcached client metrics are reported as per the following. These metrics come directly from the client as opposed to
from the cache retrieval layer.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove line 141.

|`true`|`true `|Invalid combination, exception thrown.|
|`false`|`false`|`REPLACE_LEGACY`. The default for JSON-based batch ingestion. |
|`false`|`true`|`REPLACE`|
| `isAppendToExisting` | `isDropExisting` | mode |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `isAppendToExisting` | `isDropExisting` | mode |
|`isAppendToExisting`|`isDropExisting`|mode|

|`false`|`false`|`REPLACE_LEGACY`. The default for JSON-based batch ingestion. |
|`false`|`true`|`REPLACE`|
| `isAppendToExisting` | `isDropExisting` | mode |
|----------------------|-------------------|------|
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
|----------------------|-------------------|------|
|--------------------|----------------|----|

|`false`|`true`|`REPLACE`|
| `isAppendToExisting` | `isDropExisting` | mode |
|----------------------|-------------------|------|
| `true` | `false` | `APPEND`|
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `true` | `false` | `APPEND`|
|`true`|`false`|`APPEND`|

| `isAppendToExisting` | `isDropExisting` | mode |
|----------------------|-------------------|------|
| `true` | `false` | `APPEND`|
| `true` | `true ` | Invalid combination, exception thrown. |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `true` | `true ` | Invalid combination, exception thrown. |
|`true`|`true`|Invalid combination, exception thrown.|

|----------------------|-------------------|------|
| `true` | `false` | `APPEND`|
| `true` | `true ` | Invalid combination, exception thrown. |
| `false` | `false` | `REPLACE_LEGACY` (this is the default for native batch ingestion). |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `false` | `false` | `REPLACE_LEGACY` (this is the default for native batch ingestion). |
|`false`|`false`|`REPLACE_LEGACY` (This is the default for native batch ingestion.)|

| `true` | `false` | `APPEND`|
| `true` | `true ` | Invalid combination, exception thrown. |
| `false` | `false` | `REPLACE_LEGACY` (this is the default for native batch ingestion). |
| `false` | `true` | `REPLACE`|
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `false` | `true` | `REPLACE`|
|`false`|`true`|`REPLACE`|

|`ingest/handoff/time`|Total number of milliseconds taken to handoff a set of segments.|`dataSource`, `taskId`, `taskType`, `groupId`, `tags`|Depends on the coordinator cycle time.|
|`ingest/handoff/time`|Total number of milliseconds taken to handoff a set of segments.|`dataSource`, `taskId`, `taskType`, `groupId`, `tags`|Depends on the coordinator cycle time.|
If the JVM does not support CPU time measurement for the current thread, `ingest/merge/cpu` and `ingest/persists/cpu` will be 0.
|`ingest/handoff/time`|Total number of milliseconds taken to handoff a set of segments.|`dataSource`, `taskId`, `taskType`, `groupId`, `tags`|Depends on coordinator cycle time.|
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
|`ingest/handoff/time`|Total number of milliseconds taken to handoff a set of segments.|`dataSource`, `taskId`, `taskType`, `groupId`, `tags`|Depends on coordinator cycle time.|
|`ingest/handoff/time`|Total number of milliseconds taken to handoff a set of segments.|`dataSource`, `taskId`, `taskType`, `groupId`, `tags`|Depends on the coordinator cycle time.|


The shuffle metrics can be enabled by adding `org.apache.druid.indexing.worker.shuffle.ShuffleMonitor` in `druid.monitoring.monitors`
The shuffle metrics can be enabled by adding `org.apache.druid.indexing.worker.shuffle.ShuffleMonitor`
in `druid.monitoring.monitors`
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
in `druid.monitoring.monitors`
in `druid.monitoring.monitors`.

The shuffle metrics can be enabled by adding `org.apache.druid.indexing.worker.shuffle.ShuffleMonitor` in `druid.monitoring.monitors`
The shuffle metrics can be enabled by adding `org.apache.druid.indexing.worker.shuffle.ShuffleMonitor`
in `druid.monitoring.monitors`
See [Enabling Metrics](../configuration/index.md#enabling-metrics) for more details.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
See [Enabling Metrics](../configuration/index.md#enabling-metrics) for more details.
See [Enabling metrics](../configuration/index.md#enabling-metrics) for more details.

## Sys
## Sys [Deprecated]

> SysMonitor will be deprecated due to its reliance on the sigar library, which is no longer maintained.
Copy link
Copy Markdown
Contributor

@ektravel ektravel Aug 21, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> SysMonitor will be deprecated due to its reliance on the sigar library, which is no longer maintained.
> SysMonitor is now deprecated and will be removed in future releases.

## Sys [Deprecated]

> SysMonitor will be deprecated due to its reliance on the sigar library, which is no longer maintained.
> A new Monitor called [OshiSysMonitor](#oshisysmonitor), which provides similar functionality but is based on the oshi
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> A new Monitor called [OshiSysMonitor](#oshisysmonitor), which provides similar functionality but is based on the oshi
> Instead, use the new OSHI monitor called [OshiSysMonitor](#oshisysmonitor). The new monitor has a wider support for different machine architectures including ARM instances.


> SysMonitor will be deprecated due to its reliance on the sigar library, which is no longer maintained.
> A new Monitor called [OshiSysMonitor](#oshisysmonitor), which provides similar functionality but is based on the oshi
> library. We encourage all users to switch to OshiSysMonitor as soon as possible.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove line 415.

|`sys/mem/max`|Memory max||Varies|
|`sys/storage/used`|Disk space used|`fsDirName`|Varies|
|`sys/cpu`|CPU used|`cpuName`, `cpuTime`|Varies|
| Metric | Description |Dimensions|Normal Value|
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If SysMonitor is deprecated, should these metrics be removed?

Also, please fix the table formatting. Do not add whitespace to make columns longer. Trim excessive white space between columns.


These metrics are only available if the `OshiSysMonitor` module is included.

| Metric | Description | Dimensions | Normal Value |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix the table formatting.

Do not add whitespace to make columns longer. Trim excessive white space between columns.

org.apache.druid.jetty.RequestLog
org.apache.hadoop
overlord.html
oshi
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
oshi
OSHI

sql
sqlQuery
successfulSending
sigar
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
sigar
[S]igar

Copy link
Copy Markdown
Contributor

@ektravel ektravel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed documentation portion of the PR.

@hardikbajaj
Copy link
Copy Markdown
Contributor Author

@ektravel @abhishekagarwal87 , This PR got closed accidentally, I have moved it to a new PR now #14912 and addressed all the comments there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants