[BUG] <TextParser parse promethues data error>

[Ceilzcx]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

when parser value like 6.6917e-05, double parse while throw exception

  ```
          # HELP go_gc_duration_seconds A summary of the pause duration of garbage collection cycles.
                # TYPE go_gc_duration_seconds summary 
                go_gc_duration_seconds {  quantile="0"} 2.0209e-05 1733750089
                go_gc_duration_seconds{  quantile = "0.25"  }   6.6917e-05
                go_gc_duration_seconds{quantile="0.5"} -Inf
                go_gc_duration_seconds{ quantile = "0.75"} +Inf
                go_gc_duration_seconds{quantile="1"} NaN
                go_gc_duration_seconds_sum 0.001134793 321314
                go_gc_duration_seconds_count 5 43
                # HELP go_goroutines Number of goroutines that currently exist.
                # TYPE go_goroutines gauge
                go_goroutines 32
                # HELP go_info Information about the Go environment.
                # TYPE go_info gauge
                go_info{version="go1.21.6"} 1
                # HELP go_memstats_alloc_bytes Number of bytes allocated and still in use.
                # TYPE go_memstats_alloc_bytes gauge
                go_memstats_alloc_bytes 1.5716224e+07
                # HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
                # TYPE go_memstats_alloc_bytes_total counter
                go_memstats_alloc_bytes_total 2.0707544e+07
                # HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table.
                # TYPE go_memstats_buck_hash_sys_bytes gauge
                go_memstats_buck_hash_sys_bytes 1.457881e+06
                # HELP go_memstats_frees_total Total number of frees.
                # TYPE go_memstats_frees_total counter
                go_memstats_frees_total 50438
                # HELP go_memstats_gc_sys_bytes Number of bytes used for garbage collection system metadata.
                # TYPE go_memstats_gc_sys_bytes gauge
                go_memstats_gc_sys_bytes 4.614808e+06

### Expected Behavior

_No response_

### Steps To Reproduce

_No response_

### Environment

```markdown
HertzBeat version(s):

Debug logs

No response

Anything else?

No response

[Ceilzcx]

their are two prometheus parse implement, maybe can unify into a common class

[JuJinPark]

I believe there is definitely a bug in TextParser.
Can I work on this issue? 😄

By the way, I have a question. I noticed that OnlineParser is not used anywhere in the code. However, it seems to work well and has already been tested with some test cases.
What is OnlineParser for? Was it just forgotten to be used in place of TextParser? 🤔

[tomsun28]

I believe there is definitely a bug in TextParser.
Can I work on this issue? 😄

hi, welcome.

By the way, I have a question. I noticed that OnlineParser is not used anywhere in the code. However, it seems to work well and has already been tested with some test cases.
What is OnlineParser for? Was it just forgotten to be used in place of TextParser? 🤔

we haven't replaced it yet now. We plan to replace all of them in the future.

[JuJinPark]

@tomsun28 then Can I fix this issue by replacing TextParser with OnlineParser in PrometheusAutoCollectImpl?

[tomsun28]

@tomsun28 then Can I fix this issue by replacing TextParser with OnlineParser in PrometheusAutoCollectImpl?

hi @leo-934 how about this?