error: unsupported character in float while parsing

[wademorris]

I am receiving the following error on my prometheus scrape logs:
err="unsupported character in float while parsing: "SourceName;SourceId;SourceInstance;State;Type;Number""

It seems like it is trying to read in the first line as a metric and it does not like it, as it is not a float. I dont know if there is a way to ignore the first line or turn that header off? Any help would be much appreciated.

[czanik]

Odd. Which version of syslog-ng do you use? As I connected now to the syslog-ng from the command line, executed the same commands as this python script does, and it works fine:

czplaptop:/run # ncat -U syslog-ng.ctl 
STATS PROMETHEUS WITH_LEGACY
syslogng_input_events_total{driver="journal",id="src#0"} 124034
syslogng_internal_events_total{result="dropped"} 0
syslogng_internal_events_total{result="processed"} 35
syslogng_internal_events_total{result="queued"} 0
syslogng_last_config_reload_timestamp_seconds 1743055842
syslogng_destination_processed{id="xconsole"} 92
syslogng_global_msg_clones_processed 0
syslogng_scratch_buffers_bytes 512
syslogng_global_sdata_updates_processed 0
syslogng_destination_processed{id="acpid"} 0
syslogng_last_config_file_modification_timestamp_seconds 1715622109
syslogng_destination_processed{id="messages"} 123763
syslogng_scratch_buffers_count 10
syslogng_destination_processed{id="console"} 92
syslogng_destination_processed{id="mailwarn"} 0
syslogng_destination_processed{id="mail"} 2
syslogng_destination_processed{id="netmgm"} 304
syslogng_center_processed{stat_instance="queued"} 125138
syslogng_destination_processed{id="warn"} 446
syslogng_input_events_total{id="src#1"} 35
syslogng_last_successful_config_reload_timestamp_seconds 1743055842
syslogng_destination_processed{id="localmessages"} 437
syslogng_destination_processed{id="firewall"} 0
syslogng_center_processed{stat_instance="received"} 124069
syslogng_global_payload_reallocs_processed 369439
syslogng_internal_events_queue_capacity 10000
syslogng_source_processed{id="src"} 124069
syslogng_destination_processed{id="mailinfo"} 2
syslogng_destination_processed{id="mailerr"} 0
.
STATS PROMETHEUS            
syslogng_input_events_total{driver="journal",id="src#0"} 124048
syslogng_internal_events_total{result="dropped"} 0
syslogng_internal_events_total{result="processed"} 35
syslogng_internal_events_total{result="queued"} 0
syslogng_last_config_reload_timestamp_seconds 1743055842
syslogng_scratch_buffers_bytes 0
syslogng_last_config_file_modification_timestamp_seconds 1715622109
syslogng_scratch_buffers_count 8
syslogng_input_events_total{id="src#1"} 35
syslogng_last_successful_config_reload_timestamp_seconds 1743055842
syslogng_internal_events_queue_capacity 10000
.

I use 4.6.0 on my laptop.

[wademorris]

syslog-ng-premium-edition 7 (7.0.32)

It doesnt seem to take the PROMETHEUS switch...

[root@myserver run]# ncat -U syslog-ng.ctl
STATS PROMETHEUS
SourceName;SourceId;SourceInstance;State;Type;Number
filter;f_valid_sd_logtype;;a;matched;0
filter;f_valid_sd_logtype;;a;not_matched;0
source;s_rfc5424_1356;;a;processed;0
global;payload_reallocs;;a;processed;650

[czanik]

I only tested with 7.0.34, that works fine. It seems that PE 4.0.32 is based on an older syslog-ng open source release than I expected. I'll fix the README.

Note that even if it works on 7.0.34, it is not an officially supported feature on syslog-ng PE (yet).