diff options
Diffstat (limited to '')
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/4d_server.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/4d_server.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/8430ft_modem.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/8430ft_modem.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/a10_acos_network_devices.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/a10_acos_network_devices.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/airthings_waveplus_air_sensor.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/airthings_waveplus_air_sensor.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/akamai_edge_dns_traffic.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_edge_dns_traffic.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/akamai_global_traffic_management.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_global_traffic_management.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/akami_cloudmonitor.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/akami_cloudmonitor.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/alamos_fe2_server.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/alamos_fe2_server.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/alibaba_cloud.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/alibaba_cloud.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/altaro_backup.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/altaro_backup.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/amd_cpu_&_gpu.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/amd_cpu_&_gpu.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/andrews_&_arnold_line_status.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/andrews_&_arnold_line_status.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/apache_airflow.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_airflow.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/apache_flink.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_flink.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/apicast.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/apicast.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/apple_time_machine.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/apple_time_machine.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/arm_hwcpipe.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/arm_hwcpipe.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/aruba_devices.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/aruba_devices.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/arvancloud_cdn.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/arvancloud_cdn.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/audisto.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/audisto.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/authlog.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/authlog.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/aws_ec2_compute_instances.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_compute_instances.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/aws_ec2_spot_instance.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_spot_instance.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/aws_ecs.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ecs.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/aws_health_events.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_health_events.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/aws_instance_health.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_instance_health.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/aws_quota.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_quota.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/aws_rds.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_rds.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/aws_s3_buckets.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_s3_buckets.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/aws_sqs.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_sqs.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/azure_ad_app_passwords.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_ad_app_passwords.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/azure_application.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_application.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/azure_elastic_pool_sql.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_elastic_pool_sql.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/azure_resources.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_resources.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/azure_service_bus.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_service_bus.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/azure_sql.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_sql.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/bigquery.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/bigquery.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/bird_routing_daemon.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/bird_routing_daemon.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/blackbox.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/blackbox.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/bobcat_miner_300.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/bobcat_miner_300.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/borg_backup.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/borg_backup.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/bosh.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/bosh.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/bpftrace_variables.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/bpftrace_variables.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/bungeecord.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/bungeecord.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cadvisor.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cadvisor.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/celery.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/celery.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/certificate_transparency.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/certificate_transparency.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/checkpoint_device.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/checkpoint_device.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/chia.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/chia.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cilium_agent.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_agent.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cilium_operator.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_operator.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cilium_proxy.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_proxy.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cisco_aci.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cisco_aci.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/citrix_netscaler.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/citrix_netscaler.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/clamav_daemon.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamav_daemon.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/clamscan_results.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamscan_results.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/clash.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/clash.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cloud_foundry.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cloud_foundry_firehose.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry_firehose.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cloudflare_pcap.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudflare_pcap.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cloudwatch.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudwatch.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/clustercontrol_cmon.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/clustercontrol_cmon.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/collectd.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/collectd.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/concourse.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/concourse.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/craftbeerpi.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/craftbeerpi.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/crowdsec.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/crowdsec.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/crypto_exchanges.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/crypto_exchanges.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cryptowatch.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cryptowatch.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/custom_exporter.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/custom_exporter.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/cvmfs_clients.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/cvmfs_clients.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ddwrt_routers.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ddwrt_routers.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_ecs_cluster.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_ecs_cluster.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_isilon_cluster.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_isilon_cluster.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_xtremio_cluster.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_xtremio_cluster.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/dell_powermax.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_powermax.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/dependency-track.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/dependency-track.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/digitalocean.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/digitalocean.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/discourse.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/discourse.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/dmarc.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/dmarc.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/dnsbl.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/dnsbl.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/dutch_electricity_smart_meter.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/dutch_electricity_smart_meter.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/dynatrace.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/dynatrace.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/eaton_ups.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/eaton_ups.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/elgato_key_light_devices..md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/elgato_key_light_devices..md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/energomera_smart_power_meters.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/energomera_smart_power_meters.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/eos.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/eos.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/etcd.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/etcd.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/excel_spreadsheet.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/excel_spreadsheet.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/fastd.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/fastd.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/fortigate_firewall.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/fortigate_firewall.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/freebsd_nfs.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_nfs.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/freebsd_rctl-racct.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_rctl-racct.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/freifunk_network.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/freifunk_network.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/fritzbox_network_devices.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/fritzbox_network_devices.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/frrouting.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/frrouting.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/gcp_gce.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_gce.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/gcp_quota.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_quota.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/generic_command_line_output.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_command_line_output.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/generic_storage_enclosure_tool.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_storage_enclosure_tool.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/github_api_rate_limit.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_api_rate_limit.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/github_repository.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_repository.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/gitlab_runner.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/gitlab_runner.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/gobetween.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/gobetween.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/google_cloud_platform.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_cloud_platform.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/google_pagespeed.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_pagespeed.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/google_stackdriver.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_stackdriver.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/gpsd.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/gpsd.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/grafana.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/grafana.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/graylog_server.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/graylog_server.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/gtp.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/gtp.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/halon.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/halon.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/hana.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/hana.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/hashicorp_vault_secrets.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/hashicorp_vault_secrets.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/hasura_graphql_server.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/hasura_graphql_server.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/hdsentinel.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/hdsentinel.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/helium_hotspot.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_hotspot.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/helium_miner_validator.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_miner_validator.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/hhvm.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/hhvm.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/hitron_cgn_series_cpe.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_cgn_series_cpe.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/hitron_coda_cable_modem.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_coda_cable_modem.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/homebridge.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/homebridge.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/homey.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/homey.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/honeypot.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/honeypot.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/hp_ilo.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/hp_ilo.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/huawei_devices.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/huawei_devices.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/hubble.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/hubble.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ibm_aix_systems_njmon.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_aix_systems_njmon.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ibm_mq.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_mq.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ibm_spectrum.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ibm_spectrum_virtualize.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum_virtualize.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ibm_z_hardware_management_console.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_z_hardware_management_console.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/influxdb.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/influxdb.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/iota_full_node.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/iota_full_node.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ipmi_by_soundcloud.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ipmi_by_soundcloud.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/jarvis_standing_desk.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/jarvis_standing_desk.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/jenkins.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/jenkins.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/jetbrains_floating_license_server.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/jetbrains_floating_license_server.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/jmx.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/jmx.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/jolokia.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/jolokia.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/journald.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/journald.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/kafka.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/kafka_connect.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_connect.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/kafka_consumer_lag.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_consumer_lag.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/kafka_zookeeper.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_zookeeper.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/kannel.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/kannel.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/keepalived.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/keepalived.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/lagerist_disk_latency.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/lagerist_disk_latency.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ldap.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ldap.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/linode.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/linode.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/loki.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/loki.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/lustre_metadata.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/lustre_metadata.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/lynis_audit_reports.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/lynis_audit_reports.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/machbase.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/machbase.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/maildir.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/maildir.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/meilisearch.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/meilisearch.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/memcached_community.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/memcached_community.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/meraki_dashboard.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/meraki_dashboard.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/mesos.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/mesos.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/mikrotik_devices.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_devices.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/mikrotik_routeros_devices.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_routeros_devices.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/minecraft.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/minecraft.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/modbus_protocol.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/modbus_protocol.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/mogilefs.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/mogilefs.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/monnit_sensors_mqtt.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/monnit_sensors_mqtt.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/mosquitto.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/mosquitto.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/mp707_usb_thermometer.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/mp707_usb_thermometer.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/mqtt_blackbox.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/mqtt_blackbox.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/mtail.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/mtail.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/naemon.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/naemon.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/nagios.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/nagios.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/nature_remo_e_lite_devices.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/nature_remo_e_lite_devices.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/netapp_ontap_api.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_ontap_api.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/netapp_solidfire.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_solidfire.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/netatmo_sensors.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/netatmo_sensors.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/netflow.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/netflow.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/netmeter.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/netmeter.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/new_relic.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/new_relic.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/nextcloud_servers.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextcloud_servers.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/nextdns.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextdns.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/nftables.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/nftables.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/nrpe_daemon.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/nrpe_daemon.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/nsx-t.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/nsx-t.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/nvml.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/nvml.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/obs_studio.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/obs_studio.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/odbc.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/odbc.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/open_vswitch.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/open_vswitch.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/openhab.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/openhab.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/openldap_community.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/openldap_community.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/openrc.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrc.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/openrct2.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrct2.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/openroadm_devices.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/openroadm_devices.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/openstack.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/openstack.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/openvas.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/openvas.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/openweathermap.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/openweathermap.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/oracle_db_community.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/oracle_db_community.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/otrs.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/otrs.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/patroni.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/patroni.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/personal_weather_station.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/personal_weather_station.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/pgbackrest.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgbackrest.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/pgpool-ii.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgpool-ii.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/philips_hue.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/philips_hue.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/pimoroni_enviro+.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/pimoroni_enviro+.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/pingdom.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/pingdom.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/podman.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/podman.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/powerpal_devices.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/powerpal_devices.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/proftpd.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/proftpd.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/prometheus_endpoint.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/prometheus_endpoint.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/proxmox_ve.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/proxmox_ve.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/radio_thermostat.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/radio_thermostat.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/radius.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/radius.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/rancher.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/rancher.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/raritan_pdu.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/raritan_pdu.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/redis_queue.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/redis_queue.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ripe_atlas.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ripe_atlas.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/sabnzbd.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/sabnzbd.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/salicru_eqx_inverter.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/salicru_eqx_inverter.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/sense_energy.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/sense_energy.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/sentry.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/sentry.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/servertech.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/servertech.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/shell_command.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/shell_command.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/shelly_humidity_sensor.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/shelly_humidity_sensor.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/sia.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/sia.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/siemens_s7_plc.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/siemens_s7_plc.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/site_24x7.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/site_24x7.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/slurm.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/slurm.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/sma_inverters.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/sma_inverters.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/smart_meters_sml.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/smart_meters_sml.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/smartrg_808ac_cable_modem.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/smartrg_808ac_cable_modem.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/softether_vpn_server.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/softether_vpn_server.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/solar_logging_stick.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/solar_logging_stick.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/solaredge_inverters.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/solaredge_inverters.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/solis_ginlong_5g_inverters.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/solis_ginlong_5g_inverters.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/sonic_nos.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/sonic_nos.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/spacelift.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/spacelift.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/speedify_cli.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/speedify_cli.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/sphinx.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/sphinx.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/sql_database_agnostic.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/sql_database_agnostic.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ssh.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssh.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ssl_certificate.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssl_certificate.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/starlink_spacex.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/starlink_spacex.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/statuspage.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/statuspage.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/steam.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/steam.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/storidge.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/storidge.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/stream.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/stream.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/strongswan.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/strongswan.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/sunspec_solar_energy.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/sunspec_solar_energy.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/suricata.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/suricata.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/synology_activebackup.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/synology_activebackup.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/sysload.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/sysload.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/tacacs.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/tacacs.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/tado_smart_heating_solution.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/tado_smart_heating_solution.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/tankerkoenig_api.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/tankerkoenig_api.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/tesla_powerwall.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_powerwall.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/tesla_vehicle.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_vehicle.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/tesla_wall_connector.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_wall_connector.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/tp-link_p110.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/tp-link_p110.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/traceroute.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/traceroute.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/twincat_ads_web_service.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/twincat_ads_web_service.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/twitch.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/twitch.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/ubiquiti_ufiber_olt.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/ubiquiti_ufiber_olt.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/uptimerobot.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/uptimerobot.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/vault_pki.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/vault_pki.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/vertica.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/vertica.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/vscode.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/vscode.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/warp10.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/warp10.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/xiaomi_mi_flora.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/xiaomi_mi_flora.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/xmpp_server.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/xmpp_server.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/yourls_url_shortener.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/yourls_url_shortener.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/zerto.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/zerto.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/zulip.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/zulip.md) | 42 | ||||
-rw-r--r-- | src/go/plugin/go.d/modules/prometheus/integrations/zyxel_gs1200-8.md (renamed from src/go/collectors/go.d.plugin/modules/prometheus/integrations/zyxel_gs1200-8.md) | 42 |
277 files changed, 10526 insertions, 1108 deletions
diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/4d_server.md b/src/go/plugin/go.d/modules/prometheus/integrations/4d_server.md index ce9241546..479fbe132 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/4d_server.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/4d_server.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/4d_server.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/4d_server.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "4D Server" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/8430ft_modem.md b/src/go/plugin/go.d/modules/prometheus/integrations/8430ft_modem.md index 9e419e180..d5087d8c1 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/8430ft_modem.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/8430ft_modem.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/8430ft_modem.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/8430ft_modem.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "8430FT modem" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/a10_acos_network_devices.md b/src/go/plugin/go.d/modules/prometheus/integrations/a10_acos_network_devices.md index e08fffa28..886572d83 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/a10_acos_network_devices.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/a10_acos_network_devices.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/a10_acos_network_devices.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/a10_acos_network_devices.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "A10 ACOS network devices" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/airthings_waveplus_air_sensor.md b/src/go/plugin/go.d/modules/prometheus/integrations/airthings_waveplus_air_sensor.md index 275b8ccaf..d6353d5c4 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/airthings_waveplus_air_sensor.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/airthings_waveplus_air_sensor.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/airthings_waveplus_air_sensor.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/airthings_waveplus_air_sensor.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Airthings Waveplus air sensor" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_edge_dns_traffic.md b/src/go/plugin/go.d/modules/prometheus/integrations/akamai_edge_dns_traffic.md index e8e8c8aba..d61275eb6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_edge_dns_traffic.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/akamai_edge_dns_traffic.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_edge_dns_traffic.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/akamai_edge_dns_traffic.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Akamai Edge DNS Traffic" learn_status: "Published" learn_rel_path: "Collecting Metrics/DNS and DHCP Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_global_traffic_management.md b/src/go/plugin/go.d/modules/prometheus/integrations/akamai_global_traffic_management.md index 1fbd6bf23..6c1dbbf3a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_global_traffic_management.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/akamai_global_traffic_management.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akamai_global_traffic_management.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/akamai_global_traffic_management.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Akamai Global Traffic Management" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akami_cloudmonitor.md b/src/go/plugin/go.d/modules/prometheus/integrations/akami_cloudmonitor.md index 736cf25fa..480892401 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akami_cloudmonitor.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/akami_cloudmonitor.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/akami_cloudmonitor.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/akami_cloudmonitor.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Akami Cloudmonitor" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/alamos_fe2_server.md b/src/go/plugin/go.d/modules/prometheus/integrations/alamos_fe2_server.md index b29363d15..1f5552ac6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/alamos_fe2_server.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/alamos_fe2_server.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/alamos_fe2_server.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/alamos_fe2_server.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Alamos FE2 server" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/alibaba_cloud.md b/src/go/plugin/go.d/modules/prometheus/integrations/alibaba_cloud.md index ec11ff2fe..51a5203fe 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/alibaba_cloud.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/alibaba_cloud.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/alibaba_cloud.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/alibaba_cloud.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Alibaba Cloud" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/altaro_backup.md b/src/go/plugin/go.d/modules/prometheus/integrations/altaro_backup.md index 8f2509ffd..c5200c889 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/altaro_backup.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/altaro_backup.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/altaro_backup.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/altaro_backup.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Altaro Backup" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/amd_cpu_&_gpu.md b/src/go/plugin/go.d/modules/prometheus/integrations/amd_cpu_&_gpu.md index 5e9b84488..0eb582743 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/amd_cpu_&_gpu.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/amd_cpu_&_gpu.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/amd_cpu_&_gpu.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/amd_cpu_&_gpu.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AMD CPU & GPU" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/andrews_&_arnold_line_status.md b/src/go/plugin/go.d/modules/prometheus/integrations/andrews_&_arnold_line_status.md index 85c1cc1de..52d282bab 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/andrews_&_arnold_line_status.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/andrews_&_arnold_line_status.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/andrews_&_arnold_line_status.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/andrews_&_arnold_line_status.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Andrews & Arnold line status" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_airflow.md b/src/go/plugin/go.d/modules/prometheus/integrations/apache_airflow.md index 139d0f6e5..5a5d15074 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_airflow.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/apache_airflow.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_airflow.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/apache_airflow.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Apache Airflow" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_flink.md b/src/go/plugin/go.d/modules/prometheus/integrations/apache_flink.md index 90560fa80..325b15d67 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_flink.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/apache_flink.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apache_flink.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/apache_flink.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Apache Flink" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apicast.md b/src/go/plugin/go.d/modules/prometheus/integrations/apicast.md index ed4b089df..7c36df053 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apicast.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/apicast.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apicast.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/apicast.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "APIcast" learn_status: "Published" learn_rel_path: "Collecting Metrics/Web Servers and Web Proxies" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apple_time_machine.md b/src/go/plugin/go.d/modules/prometheus/integrations/apple_time_machine.md index e42d25a2e..e3a916ebc 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apple_time_machine.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/apple_time_machine.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/apple_time_machine.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/apple_time_machine.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Apple Time Machine" learn_status: "Published" learn_rel_path: "Collecting Metrics/macOS Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/arm_hwcpipe.md b/src/go/plugin/go.d/modules/prometheus/integrations/arm_hwcpipe.md index 9cbb3b505..14a4386f4 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/arm_hwcpipe.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/arm_hwcpipe.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/arm_hwcpipe.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/arm_hwcpipe.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "ARM HWCPipe" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aruba_devices.md b/src/go/plugin/go.d/modules/prometheus/integrations/aruba_devices.md index d11a520ea..c848873b2 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aruba_devices.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/aruba_devices.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aruba_devices.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/aruba_devices.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Aruba devices" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/arvancloud_cdn.md b/src/go/plugin/go.d/modules/prometheus/integrations/arvancloud_cdn.md index e8c31e4ff..81bcbd70a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/arvancloud_cdn.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/arvancloud_cdn.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/arvancloud_cdn.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/arvancloud_cdn.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "ArvanCloud CDN" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/audisto.md b/src/go/plugin/go.d/modules/prometheus/integrations/audisto.md index 51e27fa2e..81c450889 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/audisto.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/audisto.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/audisto.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/audisto.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Audisto" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/authlog.md b/src/go/plugin/go.d/modules/prometheus/integrations/authlog.md index 4c3e86e78..86f20e30b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/authlog.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/authlog.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/authlog.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/authlog.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AuthLog" learn_status: "Published" learn_rel_path: "Collecting Metrics/Logs Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_compute_instances.md b/src/go/plugin/go.d/modules/prometheus/integrations/aws_ec2_compute_instances.md index 11f1bea81..c31b72dc1 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_compute_instances.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/aws_ec2_compute_instances.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_compute_instances.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/aws_ec2_compute_instances.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AWS EC2 Compute instances" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_spot_instance.md b/src/go/plugin/go.d/modules/prometheus/integrations/aws_ec2_spot_instance.md index ad8b625eb..908624b4c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_spot_instance.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/aws_ec2_spot_instance.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ec2_spot_instance.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/aws_ec2_spot_instance.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AWS EC2 Spot Instance" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ecs.md b/src/go/plugin/go.d/modules/prometheus/integrations/aws_ecs.md index 8192a4f19..aed1877b8 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ecs.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/aws_ecs.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_ecs.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/aws_ecs.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AWS ECS" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_health_events.md b/src/go/plugin/go.d/modules/prometheus/integrations/aws_health_events.md index 531159d0c..dd1d4bc6a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_health_events.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/aws_health_events.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_health_events.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/aws_health_events.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AWS Health events" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_instance_health.md b/src/go/plugin/go.d/modules/prometheus/integrations/aws_instance_health.md index 39d44f056..82da72d23 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_instance_health.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/aws_instance_health.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_instance_health.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/aws_instance_health.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AWS instance health" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_quota.md b/src/go/plugin/go.d/modules/prometheus/integrations/aws_quota.md index 45f8e46c2..67970fdf8 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_quota.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/aws_quota.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_quota.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/aws_quota.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AWS Quota" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_rds.md b/src/go/plugin/go.d/modules/prometheus/integrations/aws_rds.md index aa41d233b..acd1e7101 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_rds.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/aws_rds.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_rds.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/aws_rds.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AWS RDS" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_s3_buckets.md b/src/go/plugin/go.d/modules/prometheus/integrations/aws_s3_buckets.md index e60ccc95f..e4628d718 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_s3_buckets.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/aws_s3_buckets.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_s3_buckets.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/aws_s3_buckets.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AWS S3 buckets" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_sqs.md b/src/go/plugin/go.d/modules/prometheus/integrations/aws_sqs.md index c47c9ab5d..b2760e205 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_sqs.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/aws_sqs.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/aws_sqs.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/aws_sqs.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "AWS SQS" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_ad_app_passwords.md b/src/go/plugin/go.d/modules/prometheus/integrations/azure_ad_app_passwords.md index 7cc470b5f..1f1ce0a85 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_ad_app_passwords.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/azure_ad_app_passwords.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_ad_app_passwords.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/azure_ad_app_passwords.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Azure AD App passwords" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_application.md b/src/go/plugin/go.d/modules/prometheus/integrations/azure_application.md index 0506121dd..55f124658 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_application.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/azure_application.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_application.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/azure_application.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Azure application" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_elastic_pool_sql.md b/src/go/plugin/go.d/modules/prometheus/integrations/azure_elastic_pool_sql.md index 9b4fa439f..0fa89bff2 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_elastic_pool_sql.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/azure_elastic_pool_sql.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_elastic_pool_sql.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/azure_elastic_pool_sql.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Azure Elastic Pool SQL" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_resources.md b/src/go/plugin/go.d/modules/prometheus/integrations/azure_resources.md index f4bf49a24..c63e0ad1d 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_resources.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/azure_resources.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_resources.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/azure_resources.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Azure Resources" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_service_bus.md b/src/go/plugin/go.d/modules/prometheus/integrations/azure_service_bus.md index 98ea56cd1..c1a641aaa 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_service_bus.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/azure_service_bus.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_service_bus.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/azure_service_bus.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Azure Service Bus" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_sql.md b/src/go/plugin/go.d/modules/prometheus/integrations/azure_sql.md index 84519f1f6..98a933eb6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_sql.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/azure_sql.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/azure_sql.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/azure_sql.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Azure SQL" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bigquery.md b/src/go/plugin/go.d/modules/prometheus/integrations/bigquery.md index dd3803557..a76ff8fb3 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bigquery.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/bigquery.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bigquery.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/bigquery.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "BigQuery" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bird_routing_daemon.md b/src/go/plugin/go.d/modules/prometheus/integrations/bird_routing_daemon.md index 5b54fe191..43318c4c5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bird_routing_daemon.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/bird_routing_daemon.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bird_routing_daemon.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/bird_routing_daemon.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Bird Routing Daemon" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/blackbox.md b/src/go/plugin/go.d/modules/prometheus/integrations/blackbox.md index d46e0f72e..d37019b6d 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/blackbox.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/blackbox.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/blackbox.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/blackbox.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Blackbox" learn_status: "Published" learn_rel_path: "Collecting Metrics/Synthetic Checks" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bobcat_miner_300.md b/src/go/plugin/go.d/modules/prometheus/integrations/bobcat_miner_300.md index 66038390f..c00ccaa7d 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bobcat_miner_300.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/bobcat_miner_300.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bobcat_miner_300.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/bobcat_miner_300.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Bobcat Miner 300" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/borg_backup.md b/src/go/plugin/go.d/modules/prometheus/integrations/borg_backup.md index 073178281..67a175340 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/borg_backup.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/borg_backup.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/borg_backup.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/borg_backup.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Borg backup" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bosh.md b/src/go/plugin/go.d/modules/prometheus/integrations/bosh.md index b7a170278..c8fc354f3 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bosh.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/bosh.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bosh.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/bosh.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "BOSH" learn_status: "Published" learn_rel_path: "Collecting Metrics/Provisioning Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bpftrace_variables.md b/src/go/plugin/go.d/modules/prometheus/integrations/bpftrace_variables.md index fc29c2451..76ed9a2f0 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bpftrace_variables.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/bpftrace_variables.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bpftrace_variables.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/bpftrace_variables.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "bpftrace variables" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bungeecord.md b/src/go/plugin/go.d/modules/prometheus/integrations/bungeecord.md index 5412b4314..cebba3d2f 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bungeecord.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/bungeecord.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/bungeecord.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/bungeecord.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "BungeeCord" learn_status: "Published" learn_rel_path: "Collecting Metrics/Gaming" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cadvisor.md b/src/go/plugin/go.d/modules/prometheus/integrations/cadvisor.md index 549311c3d..a40221af5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cadvisor.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cadvisor.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cadvisor.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cadvisor.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "cAdvisor" learn_status: "Published" learn_rel_path: "Collecting Metrics/Containers and VMs" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/celery.md b/src/go/plugin/go.d/modules/prometheus/integrations/celery.md index b8d72eaa4..2cb4e8219 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/celery.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/celery.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/celery.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/celery.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Celery" learn_status: "Published" learn_rel_path: "Collecting Metrics/Task Queues" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/certificate_transparency.md b/src/go/plugin/go.d/modules/prometheus/integrations/certificate_transparency.md index 9f541e8e5..b741f95ff 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/certificate_transparency.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/certificate_transparency.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/certificate_transparency.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/certificate_transparency.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Certificate Transparency" learn_status: "Published" learn_rel_path: "Collecting Metrics/Security Systems" @@ -38,7 +38,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -139,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -267,6 +266,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -289,4 +290,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/checkpoint_device.md b/src/go/plugin/go.d/modules/prometheus/integrations/checkpoint_device.md index a84fae415..4d63f806e 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/checkpoint_device.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/checkpoint_device.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/checkpoint_device.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/checkpoint_device.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Checkpoint device" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/chia.md b/src/go/plugin/go.d/modules/prometheus/integrations/chia.md index 45755773e..158b6990e 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/chia.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/chia.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/chia.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/chia.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Chia" learn_status: "Published" learn_rel_path: "Collecting Metrics/Blockchain Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md b/src/go/plugin/go.d/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md index d315fbe4b..71f6460f3 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/christ_elektronik_clm5ip_power_panel.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Christ Elektronik CLM5IP power panel" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_agent.md b/src/go/plugin/go.d/modules/prometheus/integrations/cilium_agent.md index d2285aa32..77369adaa 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_agent.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cilium_agent.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_agent.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cilium_agent.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Cilium Agent" learn_status: "Published" learn_rel_path: "Collecting Metrics/Kubernetes" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_operator.md b/src/go/plugin/go.d/modules/prometheus/integrations/cilium_operator.md index b1bb16cfa..4083f7b0b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_operator.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cilium_operator.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_operator.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cilium_operator.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Cilium Operator" learn_status: "Published" learn_rel_path: "Collecting Metrics/Kubernetes" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_proxy.md b/src/go/plugin/go.d/modules/prometheus/integrations/cilium_proxy.md index 685c32291..cfffa6299 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_proxy.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cilium_proxy.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cilium_proxy.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cilium_proxy.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Cilium Proxy" learn_status: "Published" learn_rel_path: "Collecting Metrics/Kubernetes" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cisco_aci.md b/src/go/plugin/go.d/modules/prometheus/integrations/cisco_aci.md index b452a6ccc..9766e88d1 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cisco_aci.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cisco_aci.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cisco_aci.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cisco_aci.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Cisco ACI" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/citrix_netscaler.md b/src/go/plugin/go.d/modules/prometheus/integrations/citrix_netscaler.md index 5a1d47cca..e6b704031 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/citrix_netscaler.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/citrix_netscaler.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/citrix_netscaler.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/citrix_netscaler.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Citrix NetScaler" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamav_daemon.md b/src/go/plugin/go.d/modules/prometheus/integrations/clamav_daemon.md index abe4e2058..ea0398be5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamav_daemon.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/clamav_daemon.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamav_daemon.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/clamav_daemon.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "ClamAV daemon" learn_status: "Published" learn_rel_path: "Collecting Metrics/Security Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamscan_results.md b/src/go/plugin/go.d/modules/prometheus/integrations/clamscan_results.md index 48910ea66..4cc488b1c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamscan_results.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/clamscan_results.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clamscan_results.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/clamscan_results.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Clamscan results" learn_status: "Published" learn_rel_path: "Collecting Metrics/Security Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clash.md b/src/go/plugin/go.d/modules/prometheus/integrations/clash.md index 76d092e1f..23b80bd30 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clash.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/clash.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clash.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/clash.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Clash" learn_status: "Published" learn_rel_path: "Collecting Metrics/Web Servers and Web Proxies" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry.md b/src/go/plugin/go.d/modules/prometheus/integrations/cloud_foundry.md index ea3136e9c..2d1b36c25 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cloud_foundry.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cloud_foundry.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Cloud Foundry" learn_status: "Published" learn_rel_path: "Collecting Metrics/Provisioning Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry_firehose.md b/src/go/plugin/go.d/modules/prometheus/integrations/cloud_foundry_firehose.md index 704613da5..d6405b416 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry_firehose.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cloud_foundry_firehose.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloud_foundry_firehose.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cloud_foundry_firehose.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Cloud Foundry Firehose" learn_status: "Published" learn_rel_path: "Collecting Metrics/Provisioning Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudflare_pcap.md b/src/go/plugin/go.d/modules/prometheus/integrations/cloudflare_pcap.md index fd2606685..2c1c479a4 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudflare_pcap.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cloudflare_pcap.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudflare_pcap.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cloudflare_pcap.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Cloudflare PCAP" learn_status: "Published" learn_rel_path: "Collecting Metrics/Web Servers and Web Proxies" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudwatch.md b/src/go/plugin/go.d/modules/prometheus/integrations/cloudwatch.md index 32a5eee3e..816c0450e 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudwatch.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cloudwatch.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cloudwatch.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cloudwatch.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "CloudWatch" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clustercontrol_cmon.md b/src/go/plugin/go.d/modules/prometheus/integrations/clustercontrol_cmon.md index 82f853b8e..c69cb434c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clustercontrol_cmon.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/clustercontrol_cmon.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/clustercontrol_cmon.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/clustercontrol_cmon.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "ClusterControl CMON" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/collectd.md b/src/go/plugin/go.d/modules/prometheus/integrations/collectd.md index 9f2def2b9..972146881 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/collectd.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/collectd.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/collectd.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/collectd.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Collectd" learn_status: "Published" learn_rel_path: "Collecting Metrics/Observability" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/concourse.md b/src/go/plugin/go.d/modules/prometheus/integrations/concourse.md index d6c04ab3d..ce7baff4b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/concourse.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/concourse.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/concourse.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/concourse.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Concourse" learn_status: "Published" learn_rel_path: "Collecting Metrics/CICD Platforms" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/craftbeerpi.md b/src/go/plugin/go.d/modules/prometheus/integrations/craftbeerpi.md index 809750202..f4dae54c5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/craftbeerpi.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/craftbeerpi.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/craftbeerpi.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/craftbeerpi.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "CraftBeerPi" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/crowdsec.md b/src/go/plugin/go.d/modules/prometheus/integrations/crowdsec.md index d7aebeb88..a59069dd3 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/crowdsec.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/crowdsec.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/crowdsec.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/crowdsec.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Crowdsec" learn_status: "Published" learn_rel_path: "Collecting Metrics/Security Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/crypto_exchanges.md b/src/go/plugin/go.d/modules/prometheus/integrations/crypto_exchanges.md index c6b4a9c87..a56ed0db5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/crypto_exchanges.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/crypto_exchanges.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/crypto_exchanges.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/crypto_exchanges.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Crypto exchanges" learn_status: "Published" learn_rel_path: "Collecting Metrics/Blockchain Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cryptowatch.md b/src/go/plugin/go.d/modules/prometheus/integrations/cryptowatch.md index 599c83b16..554910783 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cryptowatch.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cryptowatch.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cryptowatch.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cryptowatch.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Cryptowatch" learn_status: "Published" learn_rel_path: "Collecting Metrics/Blockchain Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/custom_exporter.md b/src/go/plugin/go.d/modules/prometheus/integrations/custom_exporter.md index 950baef8a..9d309e624 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/custom_exporter.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/custom_exporter.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/custom_exporter.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/custom_exporter.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Custom Exporter" learn_status: "Published" learn_rel_path: "Collecting Metrics/Generic Collecting Metrics" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cvmfs_clients.md b/src/go/plugin/go.d/modules/prometheus/integrations/cvmfs_clients.md index 6015b27e0..b283f220c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cvmfs_clients.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/cvmfs_clients.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/cvmfs_clients.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/cvmfs_clients.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "CVMFS clients" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ddwrt_routers.md b/src/go/plugin/go.d/modules/prometheus/integrations/ddwrt_routers.md index efff8ee21..e0b898fbf 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ddwrt_routers.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ddwrt_routers.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ddwrt_routers.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ddwrt_routers.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "DDWRT Routers" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_ecs_cluster.md b/src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_ecs_cluster.md index ea1954dff..6d268ca64 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_ecs_cluster.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_ecs_cluster.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_ecs_cluster.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_ecs_cluster.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Dell EMC ECS cluster" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_isilon_cluster.md b/src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_isilon_cluster.md index 96be281d6..5f29528ad 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_isilon_cluster.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_isilon_cluster.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_isilon_cluster.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_isilon_cluster.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Dell EMC Isilon cluster" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_xtremio_cluster.md b/src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_xtremio_cluster.md index cc658d4a9..fe7285234 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_xtremio_cluster.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_xtremio_cluster.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_emc_xtremio_cluster.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/dell_emc_xtremio_cluster.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Dell EMC XtremIO cluster" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_powermax.md b/src/go/plugin/go.d/modules/prometheus/integrations/dell_powermax.md index 87657569e..200e2f049 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_powermax.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/dell_powermax.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dell_powermax.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/dell_powermax.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Dell PowerMax" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dependency-track.md b/src/go/plugin/go.d/modules/prometheus/integrations/dependency-track.md index 854d67a81..22d41e643 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dependency-track.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/dependency-track.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dependency-track.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/dependency-track.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Dependency-Track" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/digitalocean.md b/src/go/plugin/go.d/modules/prometheus/integrations/digitalocean.md index 04ab3e766..8978434c2 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/digitalocean.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/digitalocean.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/digitalocean.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/digitalocean.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "DigitalOcean" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/discourse.md b/src/go/plugin/go.d/modules/prometheus/integrations/discourse.md index 68db69083..adffe3fc3 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/discourse.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/discourse.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/discourse.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/discourse.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Discourse" learn_status: "Published" learn_rel_path: "Collecting Metrics/Media Services" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dmarc.md b/src/go/plugin/go.d/modules/prometheus/integrations/dmarc.md index 6dc0bbedf..2d02e75a9 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dmarc.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/dmarc.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dmarc.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/dmarc.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "DMARC" learn_status: "Published" learn_rel_path: "Collecting Metrics/Mail Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dnsbl.md b/src/go/plugin/go.d/modules/prometheus/integrations/dnsbl.md index 05cdb983c..e79517968 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dnsbl.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/dnsbl.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dnsbl.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/dnsbl.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "DNSBL" learn_status: "Published" learn_rel_path: "Collecting Metrics/DNS and DHCP Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dutch_electricity_smart_meter.md b/src/go/plugin/go.d/modules/prometheus/integrations/dutch_electricity_smart_meter.md index d169be7d2..cf2dabd7b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dutch_electricity_smart_meter.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/dutch_electricity_smart_meter.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dutch_electricity_smart_meter.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/dutch_electricity_smart_meter.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Dutch Electricity Smart Meter" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dynatrace.md b/src/go/plugin/go.d/modules/prometheus/integrations/dynatrace.md index ad8b25ad9..96e3969d6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dynatrace.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/dynatrace.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/dynatrace.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/dynatrace.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Dynatrace" learn_status: "Published" learn_rel_path: "Collecting Metrics/Observability" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/eaton_ups.md b/src/go/plugin/go.d/modules/prometheus/integrations/eaton_ups.md index 0c161ec90..c6c1823c8 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/eaton_ups.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/eaton_ups.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/eaton_ups.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/eaton_ups.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Eaton UPS" learn_status: "Published" learn_rel_path: "Collecting Metrics/UPS" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/elgato_key_light_devices..md b/src/go/plugin/go.d/modules/prometheus/integrations/elgato_key_light_devices..md index 1b374c1e7..b4bc8d5d6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/elgato_key_light_devices..md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/elgato_key_light_devices..md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/elgato_key_light_devices..md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/elgato_key_light_devices..md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Elgato Key Light devices." learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/energomera_smart_power_meters.md b/src/go/plugin/go.d/modules/prometheus/integrations/energomera_smart_power_meters.md index 20d661765..74764ae52 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/energomera_smart_power_meters.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/energomera_smart_power_meters.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/energomera_smart_power_meters.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/energomera_smart_power_meters.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Energomera smart power meters" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/eos.md b/src/go/plugin/go.d/modules/prometheus/integrations/eos.md index c60e269c9..b2e3d590a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/eos.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/eos.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/eos.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/eos.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "EOS" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/etcd.md b/src/go/plugin/go.d/modules/prometheus/integrations/etcd.md index acd763b37..b24d6b241 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/etcd.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/etcd.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/etcd.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/etcd.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "etcd" learn_status: "Published" learn_rel_path: "Collecting Metrics/Service Discovery / Registry" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -134,7 +133,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -262,6 +261,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -284,4 +285,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/excel_spreadsheet.md b/src/go/plugin/go.d/modules/prometheus/integrations/excel_spreadsheet.md index 8e4c88dff..6039ee832 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/excel_spreadsheet.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/excel_spreadsheet.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/excel_spreadsheet.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/excel_spreadsheet.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Excel spreadsheet" learn_status: "Published" learn_rel_path: "Collecting Metrics/Generic Collecting Metrics" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fastd.md b/src/go/plugin/go.d/modules/prometheus/integrations/fastd.md index bb4eeeded..2442dff82 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fastd.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/fastd.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fastd.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/fastd.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Fastd" learn_status: "Published" learn_rel_path: "Collecting Metrics/VPNs" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fortigate_firewall.md b/src/go/plugin/go.d/modules/prometheus/integrations/fortigate_firewall.md index 6c22c8b31..b89853a99 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fortigate_firewall.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/fortigate_firewall.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fortigate_firewall.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/fortigate_firewall.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Fortigate firewall" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_nfs.md b/src/go/plugin/go.d/modules/prometheus/integrations/freebsd_nfs.md index f2105ab2f..cf60803ad 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_nfs.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/freebsd_nfs.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_nfs.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/freebsd_nfs.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "FreeBSD NFS" learn_status: "Published" learn_rel_path: "Collecting Metrics/FreeBSD" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_rctl-racct.md b/src/go/plugin/go.d/modules/prometheus/integrations/freebsd_rctl-racct.md index db61bd9c5..bfe6e9e93 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_rctl-racct.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/freebsd_rctl-racct.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freebsd_rctl-racct.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/freebsd_rctl-racct.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "FreeBSD RCTL-RACCT" learn_status: "Published" learn_rel_path: "Collecting Metrics/FreeBSD" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freifunk_network.md b/src/go/plugin/go.d/modules/prometheus/integrations/freifunk_network.md index b716bfa2f..847e305d1 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freifunk_network.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/freifunk_network.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/freifunk_network.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/freifunk_network.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Freifunk network" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fritzbox_network_devices.md b/src/go/plugin/go.d/modules/prometheus/integrations/fritzbox_network_devices.md index 7410803fc..0158b0ba6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fritzbox_network_devices.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/fritzbox_network_devices.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/fritzbox_network_devices.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/fritzbox_network_devices.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Fritzbox network devices" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/frrouting.md b/src/go/plugin/go.d/modules/prometheus/integrations/frrouting.md index 651a028ea..5f492a475 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/frrouting.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/frrouting.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/frrouting.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/frrouting.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "FRRouting" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_gce.md b/src/go/plugin/go.d/modules/prometheus/integrations/gcp_gce.md index 87c3f2947..34c6d7673 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_gce.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/gcp_gce.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_gce.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/gcp_gce.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "GCP GCE" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_quota.md b/src/go/plugin/go.d/modules/prometheus/integrations/gcp_quota.md index 1fcc61ed0..85959b677 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_quota.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/gcp_quota.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gcp_quota.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/gcp_quota.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "GCP Quota" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_command_line_output.md b/src/go/plugin/go.d/modules/prometheus/integrations/generic_command_line_output.md index 49d4f716e..27f1cb647 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_command_line_output.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/generic_command_line_output.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_command_line_output.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/generic_command_line_output.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Generic Command Line Output" learn_status: "Published" learn_rel_path: "Collecting Metrics/Generic Collecting Metrics" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_storage_enclosure_tool.md b/src/go/plugin/go.d/modules/prometheus/integrations/generic_storage_enclosure_tool.md index 1ba08a424..ac8f74a43 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_storage_enclosure_tool.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/generic_storage_enclosure_tool.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/generic_storage_enclosure_tool.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/generic_storage_enclosure_tool.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Generic storage enclosure tool" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_api_rate_limit.md b/src/go/plugin/go.d/modules/prometheus/integrations/github_api_rate_limit.md index 6e9abc583..548430349 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_api_rate_limit.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/github_api_rate_limit.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_api_rate_limit.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/github_api_rate_limit.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "GitHub API rate limit" learn_status: "Published" learn_rel_path: "Collecting Metrics/Other" @@ -38,7 +38,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -139,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -267,6 +266,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -289,4 +290,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_repository.md b/src/go/plugin/go.d/modules/prometheus/integrations/github_repository.md index f01cbf61c..f96fc527a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_repository.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/github_repository.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/github_repository.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/github_repository.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "GitHub repository" learn_status: "Published" learn_rel_path: "Collecting Metrics/Other" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gitlab_runner.md b/src/go/plugin/go.d/modules/prometheus/integrations/gitlab_runner.md index 528543038..6982b7a59 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gitlab_runner.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/gitlab_runner.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gitlab_runner.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/gitlab_runner.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "GitLab Runner" learn_status: "Published" learn_rel_path: "Collecting Metrics/CICD Platforms" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gobetween.md b/src/go/plugin/go.d/modules/prometheus/integrations/gobetween.md index 39b74b786..7ea5ec62c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gobetween.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/gobetween.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gobetween.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/gobetween.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Gobetween" learn_status: "Published" learn_rel_path: "Collecting Metrics/Web Servers and Web Proxies" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -134,7 +133,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -262,6 +261,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -284,4 +285,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_cloud_platform.md b/src/go/plugin/go.d/modules/prometheus/integrations/google_cloud_platform.md index 4575a9edb..50fad9263 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_cloud_platform.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/google_cloud_platform.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_cloud_platform.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/google_cloud_platform.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Google Cloud Platform" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_pagespeed.md b/src/go/plugin/go.d/modules/prometheus/integrations/google_pagespeed.md index a76cf48f4..a3a3ecefe 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_pagespeed.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/google_pagespeed.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_pagespeed.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/google_pagespeed.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Google Pagespeed" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_stackdriver.md b/src/go/plugin/go.d/modules/prometheus/integrations/google_stackdriver.md index b54979932..ef8fc5734 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_stackdriver.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/google_stackdriver.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/google_stackdriver.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/google_stackdriver.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Google Stackdriver" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gpsd.md b/src/go/plugin/go.d/modules/prometheus/integrations/gpsd.md index 48716d99f..68a588515 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gpsd.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/gpsd.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gpsd.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/gpsd.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "gpsd" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/grafana.md b/src/go/plugin/go.d/modules/prometheus/integrations/grafana.md index c099fa869..2c0baa395 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/grafana.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/grafana.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/grafana.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/grafana.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Grafana" learn_status: "Published" learn_rel_path: "Collecting Metrics/Observability" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -134,7 +133,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -262,6 +261,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -284,4 +285,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/graylog_server.md b/src/go/plugin/go.d/modules/prometheus/integrations/graylog_server.md index c62c03f8d..8888ae210 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/graylog_server.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/graylog_server.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/graylog_server.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/graylog_server.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Graylog Server" learn_status: "Published" learn_rel_path: "Collecting Metrics/Logs Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gtp.md b/src/go/plugin/go.d/modules/prometheus/integrations/gtp.md index f0ad36c02..edd3b3a56 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gtp.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/gtp.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/gtp.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/gtp.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "GTP" learn_status: "Published" learn_rel_path: "Collecting Metrics/Telephony Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/halon.md b/src/go/plugin/go.d/modules/prometheus/integrations/halon.md index 41b611579..3a288e53b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/halon.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/halon.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/halon.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/halon.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Halon" learn_status: "Published" learn_rel_path: "Collecting Metrics/Mail Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hana.md b/src/go/plugin/go.d/modules/prometheus/integrations/hana.md index eb421d9ee..75d84fef6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hana.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/hana.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hana.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/hana.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "HANA" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hashicorp_vault_secrets.md b/src/go/plugin/go.d/modules/prometheus/integrations/hashicorp_vault_secrets.md index 9eb74f791..c619344d4 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hashicorp_vault_secrets.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/hashicorp_vault_secrets.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hashicorp_vault_secrets.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/hashicorp_vault_secrets.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "HashiCorp Vault secrets" learn_status: "Published" learn_rel_path: "Collecting Metrics/Authentication and Authorization" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hasura_graphql_server.md b/src/go/plugin/go.d/modules/prometheus/integrations/hasura_graphql_server.md index 0597a033c..d95a9199b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hasura_graphql_server.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/hasura_graphql_server.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hasura_graphql_server.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/hasura_graphql_server.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Hasura GraphQL Server" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -38,7 +38,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -139,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -267,6 +266,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -289,4 +290,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hdsentinel.md b/src/go/plugin/go.d/modules/prometheus/integrations/hdsentinel.md index 49cce578d..1daad64a5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hdsentinel.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/hdsentinel.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hdsentinel.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/hdsentinel.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "HDSentinel" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_hotspot.md b/src/go/plugin/go.d/modules/prometheus/integrations/helium_hotspot.md index adf9a4cf0..6ce0d3348 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_hotspot.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/helium_hotspot.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_hotspot.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/helium_hotspot.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Helium hotspot" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_miner_validator.md b/src/go/plugin/go.d/modules/prometheus/integrations/helium_miner_validator.md index 6f38b8e8b..a8fdb2814 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_miner_validator.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/helium_miner_validator.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/helium_miner_validator.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/helium_miner_validator.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Helium miner (validator)" learn_status: "Published" learn_rel_path: "Collecting Metrics/Blockchain Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hhvm.md b/src/go/plugin/go.d/modules/prometheus/integrations/hhvm.md index 20511dc13..4201947be 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hhvm.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/hhvm.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hhvm.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/hhvm.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "HHVM" learn_status: "Published" learn_rel_path: "Collecting Metrics/Web Servers and Web Proxies" @@ -38,7 +38,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -139,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -267,6 +266,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -289,4 +290,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_cgn_series_cpe.md b/src/go/plugin/go.d/modules/prometheus/integrations/hitron_cgn_series_cpe.md index 519e76261..069062f61 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_cgn_series_cpe.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/hitron_cgn_series_cpe.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_cgn_series_cpe.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/hitron_cgn_series_cpe.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Hitron CGN series CPE" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_coda_cable_modem.md b/src/go/plugin/go.d/modules/prometheus/integrations/hitron_coda_cable_modem.md index 17119f3af..c62b7b24a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_coda_cable_modem.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/hitron_coda_cable_modem.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hitron_coda_cable_modem.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/hitron_coda_cable_modem.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Hitron CODA Cable Modem" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/homebridge.md b/src/go/plugin/go.d/modules/prometheus/integrations/homebridge.md index e7dba4735..ca56a7647 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/homebridge.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/homebridge.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/homebridge.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/homebridge.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Homebridge" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/homey.md b/src/go/plugin/go.d/modules/prometheus/integrations/homey.md index cad04c0d6..b17aae574 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/homey.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/homey.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/homey.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/homey.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Homey" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/honeypot.md b/src/go/plugin/go.d/modules/prometheus/integrations/honeypot.md index 70ab53506..28fdf70b2 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/honeypot.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/honeypot.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/honeypot.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/honeypot.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Honeypot" learn_status: "Published" learn_rel_path: "Collecting Metrics/Security Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hp_ilo.md b/src/go/plugin/go.d/modules/prometheus/integrations/hp_ilo.md index 47a18b3da..54de557cb 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hp_ilo.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/hp_ilo.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hp_ilo.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/hp_ilo.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "HP iLO" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/huawei_devices.md b/src/go/plugin/go.d/modules/prometheus/integrations/huawei_devices.md index 1e4e207ed..2f1e95733 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/huawei_devices.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/huawei_devices.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/huawei_devices.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/huawei_devices.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Huawei devices" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hubble.md b/src/go/plugin/go.d/modules/prometheus/integrations/hubble.md index ebfb34698..36bd86d69 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hubble.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/hubble.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/hubble.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/hubble.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Hubble" learn_status: "Published" learn_rel_path: "Collecting Metrics/Observability" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_aix_systems_njmon.md b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_aix_systems_njmon.md index 0b9a60271..5a4499e6a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_aix_systems_njmon.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_aix_systems_njmon.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_aix_systems_njmon.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ibm_aix_systems_njmon.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "IBM AIX systems Njmon" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md index e745b88ca..f32cdd0c4 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ibm_cryptoexpress_cex_cards.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "IBM CryptoExpress (CEX) cards" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_mq.md b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_mq.md index a07219227..d41219bbb 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_mq.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_mq.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_mq.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ibm_mq.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "IBM MQ" learn_status: "Published" learn_rel_path: "Collecting Metrics/Message Brokers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum.md b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_spectrum.md index f1bff1f6d..edffab950 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_spectrum.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ibm_spectrum.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "IBM Spectrum" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum_virtualize.md b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_spectrum_virtualize.md index de55933d5..5d3dab9e7 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum_virtualize.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_spectrum_virtualize.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_spectrum_virtualize.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ibm_spectrum_virtualize.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "IBM Spectrum Virtualize" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_z_hardware_management_console.md b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_z_hardware_management_console.md index 715c6a4e0..5cca9c2ae 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_z_hardware_management_console.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ibm_z_hardware_management_console.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ibm_z_hardware_management_console.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ibm_z_hardware_management_console.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "IBM Z Hardware Management Console" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/influxdb.md b/src/go/plugin/go.d/modules/prometheus/integrations/influxdb.md index 11b340d33..817144efb 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/influxdb.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/influxdb.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/influxdb.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/influxdb.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "InfluxDB" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/iota_full_node.md b/src/go/plugin/go.d/modules/prometheus/integrations/iota_full_node.md index b81e4eacb..74ba5a3ef 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/iota_full_node.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/iota_full_node.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/iota_full_node.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/iota_full_node.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "IOTA full node" learn_status: "Published" learn_rel_path: "Collecting Metrics/Blockchain Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ipmi_by_soundcloud.md b/src/go/plugin/go.d/modules/prometheus/integrations/ipmi_by_soundcloud.md index 089c68c08..52966c728 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ipmi_by_soundcloud.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ipmi_by_soundcloud.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ipmi_by_soundcloud.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ipmi_by_soundcloud.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "IPMI (By SoundCloud)" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md b/src/go/plugin/go.d/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md index 336639604..9e2ed89a5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/iqair_airvisual_air_quality_monitors.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "iqAir AirVisual air quality monitors" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jarvis_standing_desk.md b/src/go/plugin/go.d/modules/prometheus/integrations/jarvis_standing_desk.md index 3ba765fef..cd392a297 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jarvis_standing_desk.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/jarvis_standing_desk.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jarvis_standing_desk.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/jarvis_standing_desk.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Jarvis Standing Desk" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jenkins.md b/src/go/plugin/go.d/modules/prometheus/integrations/jenkins.md index aeaf8bc23..203ae3d69 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jenkins.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/jenkins.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jenkins.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/jenkins.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Jenkins" learn_status: "Published" learn_rel_path: "Collecting Metrics/CICD Platforms" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jetbrains_floating_license_server.md b/src/go/plugin/go.d/modules/prometheus/integrations/jetbrains_floating_license_server.md index 88eae33c8..cde4e22a6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jetbrains_floating_license_server.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/jetbrains_floating_license_server.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jetbrains_floating_license_server.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/jetbrains_floating_license_server.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "JetBrains Floating License Server" learn_status: "Published" learn_rel_path: "Collecting Metrics/Generic Collecting Metrics" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jmx.md b/src/go/plugin/go.d/modules/prometheus/integrations/jmx.md index 4473dd624..6813a8087 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jmx.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/jmx.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jmx.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/jmx.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "JMX" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jolokia.md b/src/go/plugin/go.d/modules/prometheus/integrations/jolokia.md index c4c5f26af..187b40be1 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jolokia.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/jolokia.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/jolokia.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/jolokia.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "jolokia" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/journald.md b/src/go/plugin/go.d/modules/prometheus/integrations/journald.md index 36a9eeafd..0d016ad21 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/journald.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/journald.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/journald.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/journald.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "journald" learn_status: "Published" learn_rel_path: "Collecting Metrics/Logs Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka.md b/src/go/plugin/go.d/modules/prometheus/integrations/kafka.md index 83e94397f..fb328f740 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/kafka.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/kafka.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Kafka" learn_status: "Published" learn_rel_path: "Collecting Metrics/Message Brokers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_connect.md b/src/go/plugin/go.d/modules/prometheus/integrations/kafka_connect.md index 6709ce172..c28c90f49 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_connect.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/kafka_connect.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_connect.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/kafka_connect.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Kafka Connect" learn_status: "Published" learn_rel_path: "Collecting Metrics/Message Brokers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_consumer_lag.md b/src/go/plugin/go.d/modules/prometheus/integrations/kafka_consumer_lag.md index 95d5fc566..6003d3af9 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_consumer_lag.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/kafka_consumer_lag.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_consumer_lag.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/kafka_consumer_lag.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Kafka Consumer Lag" learn_status: "Published" learn_rel_path: "Collecting Metrics/Service Discovery / Registry" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_zookeeper.md b/src/go/plugin/go.d/modules/prometheus/integrations/kafka_zookeeper.md index 907aeaf4d..cbf799ca3 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_zookeeper.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/kafka_zookeeper.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kafka_zookeeper.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/kafka_zookeeper.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Kafka ZooKeeper" learn_status: "Published" learn_rel_path: "Collecting Metrics/Message Brokers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kannel.md b/src/go/plugin/go.d/modules/prometheus/integrations/kannel.md index 98fe1466e..a2264e9d9 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kannel.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/kannel.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kannel.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/kannel.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Kannel" learn_status: "Published" learn_rel_path: "Collecting Metrics/Telephony Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/keepalived.md b/src/go/plugin/go.d/modules/prometheus/integrations/keepalived.md index c82813cbc..aeb0d99b0 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/keepalived.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/keepalived.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/keepalived.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/keepalived.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Keepalived" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md b/src/go/plugin/go.d/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md index 01d0fc60c..759ce0cbe 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/kubernetes_cluster_cloud_cost.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Kubernetes Cluster Cloud Cost" learn_status: "Published" learn_rel_path: "Collecting Metrics/Kubernetes" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lagerist_disk_latency.md b/src/go/plugin/go.d/modules/prometheus/integrations/lagerist_disk_latency.md index e878d16ce..73019995c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lagerist_disk_latency.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/lagerist_disk_latency.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lagerist_disk_latency.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/lagerist_disk_latency.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Lagerist Disk latency" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ldap.md b/src/go/plugin/go.d/modules/prometheus/integrations/ldap.md index 2c4bd0ba7..705d1e198 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ldap.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ldap.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ldap.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ldap.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "LDAP" learn_status: "Published" learn_rel_path: "Collecting Metrics/Authentication and Authorization" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/linode.md b/src/go/plugin/go.d/modules/prometheus/integrations/linode.md index 046a57e3d..eff67ae75 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/linode.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/linode.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/linode.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/linode.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Linode" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/loki.md b/src/go/plugin/go.d/modules/prometheus/integrations/loki.md index bd607a23e..002634a10 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/loki.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/loki.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/loki.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/loki.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "loki" learn_status: "Published" learn_rel_path: "Collecting Metrics/Logs Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lustre_metadata.md b/src/go/plugin/go.d/modules/prometheus/integrations/lustre_metadata.md index a13c2502d..2fe27331e 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lustre_metadata.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/lustre_metadata.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lustre_metadata.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/lustre_metadata.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Lustre metadata" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lynis_audit_reports.md b/src/go/plugin/go.d/modules/prometheus/integrations/lynis_audit_reports.md index 13b2ef300..47b87c2d3 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lynis_audit_reports.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/lynis_audit_reports.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/lynis_audit_reports.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/lynis_audit_reports.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Lynis audit reports" learn_status: "Published" learn_rel_path: "Collecting Metrics/Security Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/machbase.md b/src/go/plugin/go.d/modules/prometheus/integrations/machbase.md index 48dd9aee0..23e928296 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/machbase.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/machbase.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/machbase.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/machbase.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Machbase" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/maildir.md b/src/go/plugin/go.d/modules/prometheus/integrations/maildir.md index 69c8003eb..a7c106e83 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/maildir.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/maildir.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/maildir.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/maildir.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Maildir" learn_status: "Published" learn_rel_path: "Collecting Metrics/Mail Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/meilisearch.md b/src/go/plugin/go.d/modules/prometheus/integrations/meilisearch.md index 3b22f13c6..60cad4a91 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/meilisearch.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/meilisearch.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/meilisearch.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/meilisearch.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Meilisearch" learn_status: "Published" learn_rel_path: "Collecting Metrics/Search Engines" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/memcached_community.md b/src/go/plugin/go.d/modules/prometheus/integrations/memcached_community.md index 83b53f8cd..45acae167 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/memcached_community.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/memcached_community.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/memcached_community.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/memcached_community.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Memcached (community)" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/meraki_dashboard.md b/src/go/plugin/go.d/modules/prometheus/integrations/meraki_dashboard.md index 83bb309f4..28626195a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/meraki_dashboard.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/meraki_dashboard.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/meraki_dashboard.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/meraki_dashboard.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Meraki dashboard" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mesos.md b/src/go/plugin/go.d/modules/prometheus/integrations/mesos.md index 094d53b8a..c1f7cd0ee 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mesos.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/mesos.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mesos.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/mesos.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Mesos" learn_status: "Published" learn_rel_path: "Collecting Metrics/Task Queues" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_devices.md b/src/go/plugin/go.d/modules/prometheus/integrations/mikrotik_devices.md index cac9a8c64..8d846fd26 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_devices.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/mikrotik_devices.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_devices.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/mikrotik_devices.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "MikroTik devices" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_routeros_devices.md b/src/go/plugin/go.d/modules/prometheus/integrations/mikrotik_routeros_devices.md index 5060a2d25..e988add25 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_routeros_devices.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/mikrotik_routeros_devices.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mikrotik_routeros_devices.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/mikrotik_routeros_devices.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Mikrotik RouterOS devices" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/minecraft.md b/src/go/plugin/go.d/modules/prometheus/integrations/minecraft.md index 7926ef8aa..f8649bbcb 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/minecraft.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/minecraft.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/minecraft.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/minecraft.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Minecraft" learn_status: "Published" learn_rel_path: "Collecting Metrics/Gaming" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/modbus_protocol.md b/src/go/plugin/go.d/modules/prometheus/integrations/modbus_protocol.md index 8712f31cd..f6266cd43 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/modbus_protocol.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/modbus_protocol.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/modbus_protocol.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/modbus_protocol.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Modbus protocol" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mogilefs.md b/src/go/plugin/go.d/modules/prometheus/integrations/mogilefs.md index c1759ded7..becc6c194 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mogilefs.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/mogilefs.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mogilefs.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/mogilefs.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "MogileFS" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/monnit_sensors_mqtt.md b/src/go/plugin/go.d/modules/prometheus/integrations/monnit_sensors_mqtt.md index 0e854c1b2..05517f39f 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/monnit_sensors_mqtt.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/monnit_sensors_mqtt.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/monnit_sensors_mqtt.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/monnit_sensors_mqtt.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Monnit Sensors MQTT" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mosquitto.md b/src/go/plugin/go.d/modules/prometheus/integrations/mosquitto.md index 9f5606364..115dde093 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mosquitto.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/mosquitto.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mosquitto.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/mosquitto.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "mosquitto" learn_status: "Published" learn_rel_path: "Collecting Metrics/Message Brokers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mp707_usb_thermometer.md b/src/go/plugin/go.d/modules/prometheus/integrations/mp707_usb_thermometer.md index 7beeaa202..f032dcfb6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mp707_usb_thermometer.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/mp707_usb_thermometer.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mp707_usb_thermometer.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/mp707_usb_thermometer.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "MP707 USB thermometer" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mqtt_blackbox.md b/src/go/plugin/go.d/modules/prometheus/integrations/mqtt_blackbox.md index 79b295cf5..2f6e6ca57 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mqtt_blackbox.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/mqtt_blackbox.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mqtt_blackbox.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/mqtt_blackbox.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "MQTT Blackbox" learn_status: "Published" learn_rel_path: "Collecting Metrics/Message Brokers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mtail.md b/src/go/plugin/go.d/modules/prometheus/integrations/mtail.md index 35ddb22df..e44f88d4c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mtail.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/mtail.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/mtail.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/mtail.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "mtail" learn_status: "Published" learn_rel_path: "Collecting Metrics/Logs Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/naemon.md b/src/go/plugin/go.d/modules/prometheus/integrations/naemon.md index 061b4f723..208777b95 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/naemon.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/naemon.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/naemon.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/naemon.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Naemon" learn_status: "Published" learn_rel_path: "Collecting Metrics/Observability" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nagios.md b/src/go/plugin/go.d/modules/prometheus/integrations/nagios.md index 973749943..bdd669c76 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nagios.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/nagios.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nagios.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/nagios.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Nagios" learn_status: "Published" learn_rel_path: "Collecting Metrics/Observability" @@ -38,7 +38,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -139,7 +138,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -267,6 +266,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -289,4 +290,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nature_remo_e_lite_devices.md b/src/go/plugin/go.d/modules/prometheus/integrations/nature_remo_e_lite_devices.md index da5030d6a..c102e4a7c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nature_remo_e_lite_devices.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/nature_remo_e_lite_devices.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nature_remo_e_lite_devices.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/nature_remo_e_lite_devices.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Nature Remo E lite devices" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_ontap_api.md b/src/go/plugin/go.d/modules/prometheus/integrations/netapp_ontap_api.md index 6a5025463..80e4dce3b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_ontap_api.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/netapp_ontap_api.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_ontap_api.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/netapp_ontap_api.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Netapp ONTAP API" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_solidfire.md b/src/go/plugin/go.d/modules/prometheus/integrations/netapp_solidfire.md index eab756cf4..a15aef5fb 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_solidfire.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/netapp_solidfire.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netapp_solidfire.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/netapp_solidfire.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "NetApp Solidfire" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netatmo_sensors.md b/src/go/plugin/go.d/modules/prometheus/integrations/netatmo_sensors.md index 08d17d59e..8420a5fe0 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netatmo_sensors.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/netatmo_sensors.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netatmo_sensors.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/netatmo_sensors.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Netatmo sensors" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netflow.md b/src/go/plugin/go.d/modules/prometheus/integrations/netflow.md index a5023d7b1..0b23e39b0 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netflow.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/netflow.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netflow.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/netflow.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "NetFlow" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netmeter.md b/src/go/plugin/go.d/modules/prometheus/integrations/netmeter.md index 6311eeac5..97c9893d3 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netmeter.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/netmeter.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/netmeter.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/netmeter.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "NetMeter" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/new_relic.md b/src/go/plugin/go.d/modules/prometheus/integrations/new_relic.md index fb237679d..9ca6b4c8a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/new_relic.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/new_relic.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/new_relic.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/new_relic.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "New Relic" learn_status: "Published" learn_rel_path: "Collecting Metrics/Observability" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextcloud_servers.md b/src/go/plugin/go.d/modules/prometheus/integrations/nextcloud_servers.md index 134a73520..9e61c6be8 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextcloud_servers.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/nextcloud_servers.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextcloud_servers.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/nextcloud_servers.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Nextcloud servers" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextdns.md b/src/go/plugin/go.d/modules/prometheus/integrations/nextdns.md index 9989c80ed..3d5bc0a6d 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextdns.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/nextdns.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nextdns.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/nextdns.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "NextDNS" learn_status: "Published" learn_rel_path: "Collecting Metrics/DNS and DHCP Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nftables.md b/src/go/plugin/go.d/modules/prometheus/integrations/nftables.md index 30b04d5b4..acce8b8af 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nftables.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/nftables.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nftables.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/nftables.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "nftables" learn_status: "Published" learn_rel_path: "Collecting Metrics/Linux Systems/Firewall" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nrpe_daemon.md b/src/go/plugin/go.d/modules/prometheus/integrations/nrpe_daemon.md index f6378aaac..e3a03e356 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nrpe_daemon.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/nrpe_daemon.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nrpe_daemon.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/nrpe_daemon.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "NRPE daemon" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nsx-t.md b/src/go/plugin/go.d/modules/prometheus/integrations/nsx-t.md index ec1581207..4e670ba56 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nsx-t.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/nsx-t.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nsx-t.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/nsx-t.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "NSX-T" learn_status: "Published" learn_rel_path: "Collecting Metrics/Containers and VMs" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nvml.md b/src/go/plugin/go.d/modules/prometheus/integrations/nvml.md index a6d863dc9..54bb3f1fb 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nvml.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/nvml.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/nvml.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/nvml.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "NVML" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/obs_studio.md b/src/go/plugin/go.d/modules/prometheus/integrations/obs_studio.md index eb97ee513..254833af5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/obs_studio.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/obs_studio.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/obs_studio.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/obs_studio.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "OBS Studio" learn_status: "Published" learn_rel_path: "Collecting Metrics/Media Services" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/odbc.md b/src/go/plugin/go.d/modules/prometheus/integrations/odbc.md index 553571c86..d128b647b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/odbc.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/odbc.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/odbc.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/odbc.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "ODBC" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/open_vswitch.md b/src/go/plugin/go.d/modules/prometheus/integrations/open_vswitch.md index b317cb9f1..c8d24a876 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/open_vswitch.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/open_vswitch.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/open_vswitch.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/open_vswitch.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Open vSwitch" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openhab.md b/src/go/plugin/go.d/modules/prometheus/integrations/openhab.md index 1e0d9fa07..52a2ac94d 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openhab.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/openhab.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openhab.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/openhab.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "OpenHAB" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openldap_community.md b/src/go/plugin/go.d/modules/prometheus/integrations/openldap_community.md index 29ab99e86..c1a547211 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openldap_community.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/openldap_community.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openldap_community.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/openldap_community.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "OpenLDAP (community)" learn_status: "Published" learn_rel_path: "Collecting Metrics/Authentication and Authorization" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrc.md b/src/go/plugin/go.d/modules/prometheus/integrations/openrc.md index 112f95ff8..bc5dfa902 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrc.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/openrc.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrc.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/openrc.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "OpenRC" learn_status: "Published" learn_rel_path: "Collecting Metrics/Linux Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrct2.md b/src/go/plugin/go.d/modules/prometheus/integrations/openrct2.md index a6b6b422d..7995839b1 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrct2.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/openrct2.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openrct2.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/openrct2.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "OpenRCT2" learn_status: "Published" learn_rel_path: "Collecting Metrics/Gaming" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openroadm_devices.md b/src/go/plugin/go.d/modules/prometheus/integrations/openroadm_devices.md index b6c30bd8a..d1e23dc3c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openroadm_devices.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/openroadm_devices.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openroadm_devices.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/openroadm_devices.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "OpenROADM devices" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openstack.md b/src/go/plugin/go.d/modules/prometheus/integrations/openstack.md index babb27210..874cf5ce7 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openstack.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/openstack.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openstack.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/openstack.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "OpenStack" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openvas.md b/src/go/plugin/go.d/modules/prometheus/integrations/openvas.md index fcafa2e21..09681ae7e 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openvas.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/openvas.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openvas.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/openvas.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "OpenVAS" learn_status: "Published" learn_rel_path: "Collecting Metrics/Security Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openweathermap.md b/src/go/plugin/go.d/modules/prometheus/integrations/openweathermap.md index 63ea81b82..624478e2b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openweathermap.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/openweathermap.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/openweathermap.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/openweathermap.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "OpenWeatherMap" learn_status: "Published" learn_rel_path: "Collecting Metrics/Generic Collecting Metrics" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/oracle_db_community.md b/src/go/plugin/go.d/modules/prometheus/integrations/oracle_db_community.md index 18efb8d58..ab59c3181 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/oracle_db_community.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/oracle_db_community.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/oracle_db_community.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/oracle_db_community.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Oracle DB (community)" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/otrs.md b/src/go/plugin/go.d/modules/prometheus/integrations/otrs.md index 6bb6adabd..8eadb3410 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/otrs.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/otrs.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/otrs.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/otrs.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "OTRS" learn_status: "Published" learn_rel_path: "Collecting Metrics/Incident Management" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/patroni.md b/src/go/plugin/go.d/modules/prometheus/integrations/patroni.md index a3ac52cb9..e4fe20123 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/patroni.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/patroni.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/patroni.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/patroni.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Patroni" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/personal_weather_station.md b/src/go/plugin/go.d/modules/prometheus/integrations/personal_weather_station.md index 97e6bf5b9..af1482067 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/personal_weather_station.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/personal_weather_station.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/personal_weather_station.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/personal_weather_station.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Personal Weather Station" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgbackrest.md b/src/go/plugin/go.d/modules/prometheus/integrations/pgbackrest.md index e61b9e0a7..19c60d95a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgbackrest.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/pgbackrest.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgbackrest.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/pgbackrest.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "pgBackRest" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgpool-ii.md b/src/go/plugin/go.d/modules/prometheus/integrations/pgpool-ii.md index 153304e5b..a7cfd941f 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgpool-ii.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/pgpool-ii.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pgpool-ii.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/pgpool-ii.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Pgpool-II" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/philips_hue.md b/src/go/plugin/go.d/modules/prometheus/integrations/philips_hue.md index 0ee879030..47dd77b0e 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/philips_hue.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/philips_hue.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/philips_hue.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/philips_hue.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Philips Hue" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pimoroni_enviro+.md b/src/go/plugin/go.d/modules/prometheus/integrations/pimoroni_enviro+.md index 8c93b99bf..12b5719c5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pimoroni_enviro+.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/pimoroni_enviro+.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pimoroni_enviro+.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/pimoroni_enviro+.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Pimoroni Enviro+" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pingdom.md b/src/go/plugin/go.d/modules/prometheus/integrations/pingdom.md index b28271a4b..758b80eff 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pingdom.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/pingdom.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/pingdom.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/pingdom.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Pingdom" learn_status: "Published" learn_rel_path: "Collecting Metrics/Synthetic Checks" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/podman.md b/src/go/plugin/go.d/modules/prometheus/integrations/podman.md index fe7fd0cdb..346e765cf 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/podman.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/podman.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/podman.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/podman.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Podman" learn_status: "Published" learn_rel_path: "Collecting Metrics/Containers and VMs" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/powerpal_devices.md b/src/go/plugin/go.d/modules/prometheus/integrations/powerpal_devices.md index eacd9b916..cc7b681ee 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/powerpal_devices.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/powerpal_devices.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/powerpal_devices.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/powerpal_devices.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Powerpal devices" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/proftpd.md b/src/go/plugin/go.d/modules/prometheus/integrations/proftpd.md index 9853deac1..f92612383 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/proftpd.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/proftpd.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/proftpd.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/proftpd.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "ProFTPD" learn_status: "Published" learn_rel_path: "Collecting Metrics/FTP Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/prometheus_endpoint.md b/src/go/plugin/go.d/modules/prometheus/integrations/prometheus_endpoint.md index fb24711a0..18bbd9d0a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/prometheus_endpoint.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/prometheus_endpoint.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/prometheus_endpoint.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/prometheus_endpoint.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Prometheus endpoint" learn_status: "Published" learn_rel_path: "Collecting Metrics/Generic Collecting Metrics" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -134,7 +133,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -262,6 +261,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -284,4 +285,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/proxmox_ve.md b/src/go/plugin/go.d/modules/prometheus/integrations/proxmox_ve.md index 9ac69820c..ad4bdfe63 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/proxmox_ve.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/proxmox_ve.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/proxmox_ve.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/proxmox_ve.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Proxmox VE" learn_status: "Published" learn_rel_path: "Collecting Metrics/Containers and VMs" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/radio_thermostat.md b/src/go/plugin/go.d/modules/prometheus/integrations/radio_thermostat.md index 3418c68cf..8004e7ff1 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/radio_thermostat.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/radio_thermostat.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/radio_thermostat.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/radio_thermostat.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Radio Thermostat" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/radius.md b/src/go/plugin/go.d/modules/prometheus/integrations/radius.md index 11a4625e8..22e2567e6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/radius.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/radius.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/radius.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/radius.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "RADIUS" learn_status: "Published" learn_rel_path: "Collecting Metrics/Authentication and Authorization" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/rancher.md b/src/go/plugin/go.d/modules/prometheus/integrations/rancher.md index 8a00fcf5b..945813b1d 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/rancher.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/rancher.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/rancher.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/rancher.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Rancher" learn_status: "Published" learn_rel_path: "Collecting Metrics/Kubernetes" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/raritan_pdu.md b/src/go/plugin/go.d/modules/prometheus/integrations/raritan_pdu.md index f7b1720e1..2781c3af8 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/raritan_pdu.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/raritan_pdu.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/raritan_pdu.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/raritan_pdu.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Raritan PDU" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/redis_queue.md b/src/go/plugin/go.d/modules/prometheus/integrations/redis_queue.md index 5dc630057..d3fb16d4d 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/redis_queue.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/redis_queue.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/redis_queue.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/redis_queue.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Redis Queue" learn_status: "Published" learn_rel_path: "Collecting Metrics/Message Brokers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ripe_atlas.md b/src/go/plugin/go.d/modules/prometheus/integrations/ripe_atlas.md index 4c666ffd7..7aa35e8d5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ripe_atlas.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ripe_atlas.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ripe_atlas.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ripe_atlas.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "RIPE Atlas" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sabnzbd.md b/src/go/plugin/go.d/modules/prometheus/integrations/sabnzbd.md index f1e46ab98..3c98fa9e1 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sabnzbd.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/sabnzbd.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sabnzbd.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/sabnzbd.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "SABnzbd" learn_status: "Published" learn_rel_path: "Collecting Metrics/Media Services" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/salicru_eqx_inverter.md b/src/go/plugin/go.d/modules/prometheus/integrations/salicru_eqx_inverter.md index 4863484b1..b7c5b46c3 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/salicru_eqx_inverter.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/salicru_eqx_inverter.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/salicru_eqx_inverter.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/salicru_eqx_inverter.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Salicru EQX inverter" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sense_energy.md b/src/go/plugin/go.d/modules/prometheus/integrations/sense_energy.md index d65773ac0..837d30ceb 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sense_energy.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/sense_energy.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sense_energy.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/sense_energy.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Sense Energy" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sentry.md b/src/go/plugin/go.d/modules/prometheus/integrations/sentry.md index 0837ad0af..ae878cedf 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sentry.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/sentry.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sentry.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/sentry.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Sentry" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/servertech.md b/src/go/plugin/go.d/modules/prometheus/integrations/servertech.md index f1846b348..d287fb65b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/servertech.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/servertech.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/servertech.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/servertech.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "ServerTech" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/shell_command.md b/src/go/plugin/go.d/modules/prometheus/integrations/shell_command.md index 91f4449b2..dec29a66c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/shell_command.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/shell_command.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/shell_command.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/shell_command.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Shell command" learn_status: "Published" learn_rel_path: "Collecting Metrics/Generic Collecting Metrics" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/shelly_humidity_sensor.md b/src/go/plugin/go.d/modules/prometheus/integrations/shelly_humidity_sensor.md index 256b9a94b..baf6fa58f 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/shelly_humidity_sensor.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/shelly_humidity_sensor.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/shelly_humidity_sensor.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/shelly_humidity_sensor.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Shelly humidity sensor" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sia.md b/src/go/plugin/go.d/modules/prometheus/integrations/sia.md index 41f80e7c3..6fe4a3684 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sia.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/sia.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sia.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/sia.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Sia" learn_status: "Published" learn_rel_path: "Collecting Metrics/Blockchain Servers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/siemens_s7_plc.md b/src/go/plugin/go.d/modules/prometheus/integrations/siemens_s7_plc.md index 33483d799..c6aec71e2 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/siemens_s7_plc.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/siemens_s7_plc.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/siemens_s7_plc.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/siemens_s7_plc.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Siemens S7 PLC" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/site_24x7.md b/src/go/plugin/go.d/modules/prometheus/integrations/site_24x7.md index 50a47c896..8faefa53e 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/site_24x7.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/site_24x7.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/site_24x7.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/site_24x7.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Site 24x7" learn_status: "Published" learn_rel_path: "Collecting Metrics/Synthetic Checks" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/slurm.md b/src/go/plugin/go.d/modules/prometheus/integrations/slurm.md index 003b975c0..00d27ca19 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/slurm.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/slurm.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/slurm.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/slurm.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Slurm" learn_status: "Published" learn_rel_path: "Collecting Metrics/Task Queues" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sma_inverters.md b/src/go/plugin/go.d/modules/prometheus/integrations/sma_inverters.md index 08072b85b..f739362eb 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sma_inverters.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/sma_inverters.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sma_inverters.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/sma_inverters.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "SMA Inverters" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/smart_meters_sml.md b/src/go/plugin/go.d/modules/prometheus/integrations/smart_meters_sml.md index 30578d06c..1201475a5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/smart_meters_sml.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/smart_meters_sml.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/smart_meters_sml.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/smart_meters_sml.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Smart meters SML" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/smartrg_808ac_cable_modem.md b/src/go/plugin/go.d/modules/prometheus/integrations/smartrg_808ac_cable_modem.md index 06cb9975d..1dadc3d85 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/smartrg_808ac_cable_modem.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/smartrg_808ac_cable_modem.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/smartrg_808ac_cable_modem.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/smartrg_808ac_cable_modem.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "SmartRG 808AC Cable Modem" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/softether_vpn_server.md b/src/go/plugin/go.d/modules/prometheus/integrations/softether_vpn_server.md index 5188707fc..30fd7cb64 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/softether_vpn_server.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/softether_vpn_server.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/softether_vpn_server.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/softether_vpn_server.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "SoftEther VPN Server" learn_status: "Published" learn_rel_path: "Collecting Metrics/VPNs" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solar_logging_stick.md b/src/go/plugin/go.d/modules/prometheus/integrations/solar_logging_stick.md index caee6ce8d..35c78085e 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solar_logging_stick.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/solar_logging_stick.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solar_logging_stick.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/solar_logging_stick.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Solar logging stick" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solaredge_inverters.md b/src/go/plugin/go.d/modules/prometheus/integrations/solaredge_inverters.md index ad9a67021..266f2d05c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solaredge_inverters.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/solaredge_inverters.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solaredge_inverters.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/solaredge_inverters.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "SolarEdge inverters" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solis_ginlong_5g_inverters.md b/src/go/plugin/go.d/modules/prometheus/integrations/solis_ginlong_5g_inverters.md index 46c2b5218..d0d0658f5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solis_ginlong_5g_inverters.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/solis_ginlong_5g_inverters.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/solis_ginlong_5g_inverters.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/solis_ginlong_5g_inverters.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Solis Ginlong 5G inverters" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sonic_nos.md b/src/go/plugin/go.d/modules/prometheus/integrations/sonic_nos.md index 109f8fde6..455f14fbf 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sonic_nos.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/sonic_nos.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sonic_nos.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/sonic_nos.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "SONiC NOS" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/spacelift.md b/src/go/plugin/go.d/modules/prometheus/integrations/spacelift.md index fec5255ca..ab83110bb 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/spacelift.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/spacelift.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/spacelift.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/spacelift.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Spacelift" learn_status: "Published" learn_rel_path: "Collecting Metrics/Provisioning Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/speedify_cli.md b/src/go/plugin/go.d/modules/prometheus/integrations/speedify_cli.md index 98551c620..beed0bd1a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/speedify_cli.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/speedify_cli.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/speedify_cli.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/speedify_cli.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Speedify CLI" learn_status: "Published" learn_rel_path: "Collecting Metrics/VPNs" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sphinx.md b/src/go/plugin/go.d/modules/prometheus/integrations/sphinx.md index d52f6b978..1116f91e0 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sphinx.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/sphinx.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sphinx.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/sphinx.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Sphinx" learn_status: "Published" learn_rel_path: "Collecting Metrics/Search Engines" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sql_database_agnostic.md b/src/go/plugin/go.d/modules/prometheus/integrations/sql_database_agnostic.md index 2716b751e..6a0a523c6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sql_database_agnostic.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/sql_database_agnostic.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sql_database_agnostic.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/sql_database_agnostic.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "SQL Database agnostic" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssh.md b/src/go/plugin/go.d/modules/prometheus/integrations/ssh.md index 55090280e..7ffe9b203 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssh.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ssh.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssh.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ssh.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "SSH" learn_status: "Published" learn_rel_path: "Collecting Metrics/Authentication and Authorization" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssl_certificate.md b/src/go/plugin/go.d/modules/prometheus/integrations/ssl_certificate.md index 577cc19db..2c1d519a8 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssl_certificate.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ssl_certificate.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ssl_certificate.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ssl_certificate.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "SSL Certificate" learn_status: "Published" learn_rel_path: "Collecting Metrics/Security Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/starlink_spacex.md b/src/go/plugin/go.d/modules/prometheus/integrations/starlink_spacex.md index 838d817db..b48f32c9a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/starlink_spacex.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/starlink_spacex.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/starlink_spacex.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/starlink_spacex.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Starlink (SpaceX)" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md b/src/go/plugin/go.d/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md index 5cc7847da..9b7409b83 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/starwind_vsan_vsphere_edition.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Starwind VSAN VSphere Edition" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/statuspage.md b/src/go/plugin/go.d/modules/prometheus/integrations/statuspage.md index 06fd21b99..6038729dc 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/statuspage.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/statuspage.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/statuspage.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/statuspage.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "StatusPage" learn_status: "Published" learn_rel_path: "Collecting Metrics/Incident Management" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/steam.md b/src/go/plugin/go.d/modules/prometheus/integrations/steam.md index deceacc5c..44b346593 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/steam.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/steam.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/steam.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/steam.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Steam" learn_status: "Published" learn_rel_path: "Collecting Metrics/Gaming" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/storidge.md b/src/go/plugin/go.d/modules/prometheus/integrations/storidge.md index c3115de31..48a320ce6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/storidge.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/storidge.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/storidge.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/storidge.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Storidge" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/stream.md b/src/go/plugin/go.d/modules/prometheus/integrations/stream.md index d1902ab8a..fb21cb4da 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/stream.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/stream.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/stream.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/stream.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Stream" learn_status: "Published" learn_rel_path: "Collecting Metrics/Media Services" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/strongswan.md b/src/go/plugin/go.d/modules/prometheus/integrations/strongswan.md index 234fe4507..ffddfb022 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/strongswan.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/strongswan.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/strongswan.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/strongswan.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "strongSwan" learn_status: "Published" learn_rel_path: "Collecting Metrics/VPNs" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sunspec_solar_energy.md b/src/go/plugin/go.d/modules/prometheus/integrations/sunspec_solar_energy.md index fad103072..552c5583b 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sunspec_solar_energy.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/sunspec_solar_energy.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sunspec_solar_energy.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/sunspec_solar_energy.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Sunspec Solar Energy" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/suricata.md b/src/go/plugin/go.d/modules/prometheus/integrations/suricata.md index 0f6fbd1e6..d5bdd01b5 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/suricata.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/suricata.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/suricata.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/suricata.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Suricata" learn_status: "Published" learn_rel_path: "Collecting Metrics/Security Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/synology_activebackup.md b/src/go/plugin/go.d/modules/prometheus/integrations/synology_activebackup.md index 530f7b911..b558bbf92 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/synology_activebackup.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/synology_activebackup.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/synology_activebackup.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/synology_activebackup.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Synology ActiveBackup" learn_status: "Published" learn_rel_path: "Collecting Metrics/Storage, Mount Points and Filesystems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sysload.md b/src/go/plugin/go.d/modules/prometheus/integrations/sysload.md index f697caa32..369a43020 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sysload.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/sysload.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/sysload.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/sysload.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Sysload" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md b/src/go/plugin/go.d/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md index 79a23a669..55b26bf9c 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/t-rex_nvidia_gpu_miner.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "T-Rex NVIDIA GPU Miner" learn_status: "Published" learn_rel_path: "Collecting Metrics/Hardware Devices and Sensors" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tacacs.md b/src/go/plugin/go.d/modules/prometheus/integrations/tacacs.md index 3443b6ab6..5d3534393 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tacacs.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/tacacs.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tacacs.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/tacacs.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "TACACS" learn_status: "Published" learn_rel_path: "Collecting Metrics/Authentication and Authorization" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tado_smart_heating_solution.md b/src/go/plugin/go.d/modules/prometheus/integrations/tado_smart_heating_solution.md index f04344451..ece7fb677 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tado_smart_heating_solution.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/tado_smart_heating_solution.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tado_smart_heating_solution.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/tado_smart_heating_solution.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Tado smart heating solution" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tankerkoenig_api.md b/src/go/plugin/go.d/modules/prometheus/integrations/tankerkoenig_api.md index 5911debe6..01eb6557a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tankerkoenig_api.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/tankerkoenig_api.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tankerkoenig_api.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/tankerkoenig_api.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Tankerkoenig API" learn_status: "Published" learn_rel_path: "Collecting Metrics/Generic Collecting Metrics" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_powerwall.md b/src/go/plugin/go.d/modules/prometheus/integrations/tesla_powerwall.md index f1424add3..c24163111 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_powerwall.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/tesla_powerwall.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_powerwall.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/tesla_powerwall.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Tesla Powerwall" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_vehicle.md b/src/go/plugin/go.d/modules/prometheus/integrations/tesla_vehicle.md index 10f22fbb3..56617affd 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_vehicle.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/tesla_vehicle.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_vehicle.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/tesla_vehicle.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Tesla vehicle" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_wall_connector.md b/src/go/plugin/go.d/modules/prometheus/integrations/tesla_wall_connector.md index d2a12b295..8e3c0e901 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_wall_connector.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/tesla_wall_connector.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tesla_wall_connector.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/tesla_wall_connector.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Tesla Wall Connector" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tp-link_p110.md b/src/go/plugin/go.d/modules/prometheus/integrations/tp-link_p110.md index 1d835bde6..5dd150413 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tp-link_p110.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/tp-link_p110.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/tp-link_p110.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/tp-link_p110.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "TP-Link P110" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/traceroute.md b/src/go/plugin/go.d/modules/prometheus/integrations/traceroute.md index d2f8d5c41..0896fd9ca 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/traceroute.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/traceroute.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/traceroute.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/traceroute.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Traceroute" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/twincat_ads_web_service.md b/src/go/plugin/go.d/modules/prometheus/integrations/twincat_ads_web_service.md index 9f8878c65..e276e598d 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/twincat_ads_web_service.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/twincat_ads_web_service.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/twincat_ads_web_service.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/twincat_ads_web_service.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "TwinCAT ADS Web Service" learn_status: "Published" learn_rel_path: "Collecting Metrics/Generic Collecting Metrics" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/twitch.md b/src/go/plugin/go.d/modules/prometheus/integrations/twitch.md index 9cf82aaaf..f08f81bd9 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/twitch.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/twitch.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/twitch.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/twitch.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Twitch" learn_status: "Published" learn_rel_path: "Collecting Metrics/Media Services" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ubiquiti_ufiber_olt.md b/src/go/plugin/go.d/modules/prometheus/integrations/ubiquiti_ufiber_olt.md index d5d978ee2..810ebbea3 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ubiquiti_ufiber_olt.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/ubiquiti_ufiber_olt.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/ubiquiti_ufiber_olt.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/ubiquiti_ufiber_olt.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Ubiquiti UFiber OLT" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/uptimerobot.md b/src/go/plugin/go.d/modules/prometheus/integrations/uptimerobot.md index fda2004c5..9c6b5395a 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/uptimerobot.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/uptimerobot.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/uptimerobot.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/uptimerobot.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Uptimerobot" learn_status: "Published" learn_rel_path: "Collecting Metrics/Synthetic Checks" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vault_pki.md b/src/go/plugin/go.d/modules/prometheus/integrations/vault_pki.md index 0954f0849..a7d11cd16 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vault_pki.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/vault_pki.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vault_pki.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/vault_pki.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Vault PKI" learn_status: "Published" learn_rel_path: "Collecting Metrics/Security Systems" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vertica.md b/src/go/plugin/go.d/modules/prometheus/integrations/vertica.md index 666123c8e..8463d713f 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vertica.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/vertica.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vertica.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/vertica.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Vertica" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vscode.md b/src/go/plugin/go.d/modules/prometheus/integrations/vscode.md index d72a5bf27..5fcffca01 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vscode.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/vscode.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/vscode.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/vscode.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "VSCode" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/warp10.md b/src/go/plugin/go.d/modules/prometheus/integrations/warp10.md index 5fd9e7c26..e9e60dea6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/warp10.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/warp10.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/warp10.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/warp10.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Warp10" learn_status: "Published" learn_rel_path: "Collecting Metrics/Databases" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/xiaomi_mi_flora.md b/src/go/plugin/go.d/modules/prometheus/integrations/xiaomi_mi_flora.md index 882c1022f..51314b8b2 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/xiaomi_mi_flora.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/xiaomi_mi_flora.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/xiaomi_mi_flora.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/xiaomi_mi_flora.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Xiaomi Mi Flora" learn_status: "Published" learn_rel_path: "Collecting Metrics/IoT Devices" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/xmpp_server.md b/src/go/plugin/go.d/modules/prometheus/integrations/xmpp_server.md index 336282e27..eacae8393 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/xmpp_server.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/xmpp_server.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/xmpp_server.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/xmpp_server.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "XMPP Server" learn_status: "Published" learn_rel_path: "Collecting Metrics/Message Brokers" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/yourls_url_shortener.md b/src/go/plugin/go.d/modules/prometheus/integrations/yourls_url_shortener.md index 015622617..6b84c5ee6 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/yourls_url_shortener.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/yourls_url_shortener.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/yourls_url_shortener.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/yourls_url_shortener.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "YOURLS URL Shortener" learn_status: "Published" learn_rel_path: "Collecting Metrics/APM" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zerto.md b/src/go/plugin/go.d/modules/prometheus/integrations/zerto.md index 612c6ec15..3d316461f 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zerto.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/zerto.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zerto.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/zerto.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Zerto" learn_status: "Published" learn_rel_path: "Collecting Metrics/Cloud Provider Managed" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zulip.md b/src/go/plugin/go.d/modules/prometheus/integrations/zulip.md index eb931759a..91e652c47 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zulip.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/zulip.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zulip.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/zulip.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Zulip" learn_status: "Published" learn_rel_path: "Collecting Metrics/Media Services" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + diff --git a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zyxel_gs1200-8.md b/src/go/plugin/go.d/modules/prometheus/integrations/zyxel_gs1200-8.md index d4917f635..4f0b43431 100644 --- a/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zyxel_gs1200-8.md +++ b/src/go/plugin/go.d/modules/prometheus/integrations/zyxel_gs1200-8.md @@ -1,6 +1,6 @@ <!--startmeta -custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/integrations/zyxel_gs1200-8.md" -meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/prometheus/metadata.yaml" +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/integrations/zyxel_gs1200-8.md" +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/prometheus/metadata.yaml" sidebar_label: "Zyxel GS1200-8" learn_status: "Published" learn_rel_path: "Collecting Metrics/Networking Stack and Network Interfaces" @@ -37,7 +37,6 @@ This collector supports collecting metrics from multiple instances of this integ #### Auto-Detection By default, it detects instances running on the local host by trying to connect to known ports that are [allocated to exporters](https://github.com/prometheus/prometheus/wiki/Default-port-allocations). -The full list of endpoints is available in the collector's [configuration file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/prometheus.conf). #### Limits @@ -138,7 +137,7 @@ The following options can be defined globally: update_every, autodetection_retry This option allows you to filter out unwanted time series. Only metrics matching the selector will be collected. - Logic: (pattern1 OR pattern2) AND !(pattern3 or pattern4) -- Pattern syntax: [selector](/src/go/collectors/go.d.plugin/pkg/prometheus/selector/README.md). +- Pattern syntax: [selector](/src/go/plugin/go.d/pkg/prometheus/selector/README.md). - Option syntax: ```yaml @@ -266,6 +265,8 @@ jobs: ### Debug Mode +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + To troubleshoot issues with the `prometheus` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. @@ -288,4 +289,37 @@ should give you clues as to why the collector isn't working. ./go.d.plugin -d -m prometheus ``` +### Getting Logs + +If you're encountering problems with the `prometheus` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem. + +#### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep prometheus +``` + +#### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep prometheus /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +#### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep prometheus +``` + |