CLM documentation (public beta) #4893
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
leoncx
reviewed
Dec 8, 2025
|
|
||
| 1. I notice an incident in Centreon Infra Monitoring, but I can't find enough information to determine the cause. | ||
| 2. In CLM, I investigate the relevant logs and explore their context to identify the root cause of the problem. | ||
| 3. Once the cause is understood, I can create an alert in Centreon Infra Monitoring to detect the issue automatically in the future. |
|
|
||
| Here is an example of a raw log entry in OpenTelemetry format sent by the Windows Event Viewer: | ||
|
|
||
| ```json |
There was a problem hiding this comment.
It's the format stored in Quickwit but it's not the OpenTelemetry format.
fvallon-centreon
left a comment
fvallon-centreon
left a comment
There was a problem hiding this comment.
CLM only collect OTEL log through OTEL protocol
OTEL-Collector transform non OTEL log (such as raw log from syslog for ex.) in OTEL log format
|
|
||
| ## Server or infrastructure issues | ||
|
|
||
| * **Full or failing disks**: System logs may indicate errors related to insufficient disk space or failing disks, which can cause system failure. |
There was a problem hiding this comment.
Data space is more a metrics use case (CIM) than a log use case
|
|
||
| * **Full or failing disks**: System logs may indicate errors related to insufficient disk space or failing disks, which can cause system failure. | ||
|
|
||
| * **Missing or insufficient system resources**: A lack of memory, network bandwidth, or CPU capacity may be revealed by logs indicating resource failures or "out of memory" errors. |
There was a problem hiding this comment.
CPU capacity , memory ... are more metrics use cases
|
|
||
| ## Performance anomalies | ||
|
|
||
| * **Abnormally long response times**: If an API or application starts responding much more slowly than usual, logs can reveal the underlying causes (e.g., request overload, insufficient server resources). |
There was a problem hiding this comment.
More APM / traces than ( even if you probably can detect it into apache log for example)
|
|
||
| * **Abnormally long response times**: If an API or application starts responding much more slowly than usual, logs can reveal the underlying causes (e.g., request overload, insufficient server resources). | ||
|
|
||
| * **Memory leaks**: Logs of excessive memory consumption or abnormal growth in memory usage can be detected. |
There was a problem hiding this comment.
memory usage is more metrics than log
|
|
||
| * **Memory leaks**: Logs of excessive memory consumption or abnormal growth in memory usage can be detected. | ||
|
|
||
| * **Excessive CPU or system resource consumption**: Spikes in CPU or system resource usage can be identified, helping to pinpoint bottlenecks. |
There was a problem hiding this comment.
CPU is more metrics than log use case
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Please include a short summary of the changes and what is the purpose of the PR. Any relevant information should be added to help reviewers.
Target version (i.e. version that this PR changes)