diff options
Diffstat (limited to 'health/guides/exporting')
| -rw-r--r-- | health/guides/exporting/exporting_last_buffering.md | 29 | ||||
| -rw-r--r-- | health/guides/exporting/exporting_metrics_sent.md | 46 |
2 files changed, 0 insertions, 75 deletions
diff --git a/health/guides/exporting/exporting_last_buffering.md b/health/guides/exporting/exporting_last_buffering.md deleted file mode 100644 index 4b13fe761..000000000 --- a/health/guides/exporting/exporting_last_buffering.md +++ /dev/null @@ -1,29 +0,0 @@ -### Understand the alert - -This alert is related to the Netdata Exporting engine, which calculates the number of seconds since the last successful buffering of exporting data. If you receive this alert, it means the exporting engine failed to buffer metrics for a while, and some metrics were lost during exporting. There might be issues with the exporting destination being down or unreachable. - -### Troubleshoot the alert - -1. Check the exporting destination status and accessibility: If the exporting destination (e.g. a remote server or database) is down or unreachable, your priority should be to fix the connection issue or bring the destination back up. - -2. Investigate short-term network availability problems: Short-term network connectivity issues might cause temporary errors in the exporting process. You may want to check and monitor your network to confirm this is the case and fix any issues. - -3. Increase the `buffer on failures` value in `exporting.conf`: You can try to prevent short-term problems from causing alert issues by increasing the `buffer on failures` value in the `exporting.conf` file. To do this, edit the configuration file, find the parameter `buffer on failures`, and increase its value. - - ``` - [exporting:global] - buffer on failures = new_value - ``` - Replace `new_value` with the desired number that matches your system requirements. - -4. Restart the Netdata Agent: After modifying the `exporting.conf` file, don't forget to restart the Netdata Agent for changes to take effect. Use the following command to restart the agent: - - ``` - sudo systemctl restart netdata - ``` - -5. Monitor the `exporting_last_buffering` alert: After applying the changes, keep monitoring the `exporting_last_buffering` alert to check if the issue is resolved. If the alert continues, further investigate possible issues with the exporting engine or destination. - -### Useful resources - -1. [Netdata Exporting Engine](https://learn.netdata.cloud/docs/exporting-data-to-other-systems/exporting-reference) diff --git a/health/guides/exporting/exporting_metrics_sent.md b/health/guides/exporting/exporting_metrics_sent.md deleted file mode 100644 index f17f593c4..000000000 --- a/health/guides/exporting/exporting_metrics_sent.md +++ /dev/null @@ -1,46 +0,0 @@ -### Understand the alert - -The `exporting_metrics_sent` alert is triggered when the Netdata Agent fails to send all metrics to the configured external database server. This could be due to the exporting destination being down, unreachable, or short-term network availability problems. - -### Troubleshoot the alert - -To troubleshoot this alert, follow these steps: - -1. Verify the exporting destination status: - - - Make sure the external database server is up and running. - - Check if there are any issues with the server, such as high CPU usage, low memory, or a full disk. - -2. Check the network connection between the Netdata Agent and the external database server: - - - Use tools like `ping` or `traceroute` to test the connection. - - Check for any firewall rules that may be blocking the connection. - -3. Increase the `buffer on failures` in `exporting.conf`: - - - Open the `exporting.conf` file, which is typically located at `/etc/netdata/exporting.conf`. - - - Increase the value of the `buffer on failures` setting to allow for more metrics to be stored when network/connectivity issues occur. For example, if the current setting is `10000`, try increasing it to `20000` or higher, depending on your server's available memory. - - ``` - [exporting:global] - buffer on failures = 20000 - ``` - - - Save and exit the file. - - - Restart the Netdata Agent to apply the changes. - -4. Review the Netdata Agent logs: - - - Check for any error messages or warnings related to the exporting engine in the Netdata Agent logs (`/var/log/netdata/error.log`). - - - Use the information from the logs to troubleshoot any issues you find. - -5. Ensure your configuration settings are correct: - - - Double-check your exporting configuration settings (located in `/etc/netdata/exporting.conf`) to ensure they match the requirements of your external database server. - -### Useful resources - -1. [Netdata Exporting Engine documentation](https://learn.netdata.cloud/docs/exporting-data-to-other-systems/exporting-reference) |