Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

metrics, cmd/geth: informational metrics (prometheus, influxdb, opentsb) #24877

Merged
merged 3 commits into from
Aug 31, 2023

Conversation

jorgeacortes
Copy link
Contributor

  • Created GaugeInfo metrics type for registering informational metrics.
  • Updated all related metrics modules to support the new GaugeInfo type.
  • Registered chain/info GaugeInfo with the chain_id value.
  • Registered geth/info GaugeInfo with system and build parameters.

Implements #21783

@timqian
Copy link

timqian commented Feb 16, 2023

The PR looks good to me. It works as expected and all the related tests passed

Screenshots for the added prometheus info

Screen Shot 2023-02-16 at 09 32 39

Screen Shot 2023-02-16 at 09 33 08

metrics/exp/exp.go Outdated Show resolved Hide resolved
Comment on lines 165 to 173
lastIdx := len(g) - 1
v := "{"
for idx, entry := range g {
v += "\"" + entry.Key + "\":\"" + entry.Val + "\""
if idx != lastIdx {
v += ","
}
}
v += "}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fragile, something like this would be more robust:

entries := make([]string, 0, len(g))
for k, v := range g {
        entries = append(entries, fmt.Sprintf("%s=%q", k, v))
}
return fmt.Sprintf("{%s}",strings.Join(entries,","))

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This method shouldn't be needed, just use json.Marshal(..) and pass the entries as a key/value map?
In fact, wouldn't it be a better model to have the g be a key/value map instead of a list of entries with key and a value ?

So instead of

type GaugeInfoValue []GaugeInfoEntry

You would have

type GaugeInfoValue map[string]string

Then just do json.Marshal(g) and that's it

Comment on lines 108 to 119
c.buff.WriteString(fmt.Sprintf("%s {", name))
for idx, entry := range value {
c.buff.WriteString(fmt.Sprintf("%s=\"%s\"", entry.Key, entry.Val))
if idx != len(value)-1 {
c.buff.WriteString(", ")
}
}
c.buff.WriteString("} 1 \n\n")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fragile again:

c.buff.WriteString(fmt.Sprintf("%s {", name))
entries := make([]string, 0, len(value))
for _, entry := range value {
        entries = append(entries, fmt.Sprintf("%s=%q", entry.Key, entry.Val))
}
c.buff.WriteString(fmt.Sprintf("{%s}",strings.Join(entries,",")))
c.buff.WriteString("} 1 \n\n")

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's just avoid writing json manually, we use the json package for that

Copy link
Contributor

@holiman holiman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm, made this comment weeks ago, but never actually submitted it :)

Comment on lines 165 to 173
lastIdx := len(g) - 1
v := "{"
for idx, entry := range g {
v += "\"" + entry.Key + "\":\"" + entry.Val + "\""
if idx != lastIdx {
v += ","
}
}
v += "}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This method shouldn't be needed, just use json.Marshal(..) and pass the entries as a key/value map?
In fact, wouldn't it be a better model to have the g be a key/value map instead of a list of entries with key and a value ?

So instead of

type GaugeInfoValue []GaugeInfoEntry

You would have

type GaugeInfoValue map[string]string

Then just do json.Marshal(g) and that's it

…onal metrics

- Created GaugeInfo metrics type for registering informational metrics.
- Updated all related metrics modules to support the new GaugeInfo type.
- Registered chain/info GaugeInfo with the chain_id value.
- Registered geth/info GaugeInfo with system and build parameters.

Implements ethereum#21783
@holiman holiman force-pushed the informational_metrics branch 2 times, most recently from 8eb3c7a to 00367d0 Compare August 28, 2023 10:03
@holiman holiman changed the title metrics/*,cmd/geth,core/blockchain: Implemented informational metrics metrics, cmd/geth: informational metrics (prometheus, opentsb) Aug 28, 2023
@holiman holiman changed the title metrics, cmd/geth: informational metrics (prometheus, opentsb) metrics, cmd/geth: informational metrics (prometheus, influxdb, opentsb) Aug 28, 2023
@holiman holiman force-pushed the informational_metrics branch 2 times, most recently from 9373869 to e2a9b98 Compare August 28, 2023 11:49
@holiman
Copy link
Contributor

holiman commented Aug 28, 2023

I have now refactored this quite a bit, and it should we ok for influx, prometheus and opentsb. It is defined for several other endpoints, but most of those seem deprecated and they do not even have the most basic tests.

For influx/prometheus, I have now added proper output-tests, to ensure correctnes now and in the future. What I have so far not done yet, however, is to actually hook them up and watch the numbers on actual stats-servers. Or, rather, I've tried to, but my grafana skills are a bit lacking....

Copy link
Contributor

@holiman holiman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM now (but needs to be tested with actual influx/prometheus backends)

@holiman holiman added this to the 1.13.0 milestone Aug 28, 2023
@holiman
Copy link
Contributor

holiman commented Aug 28, 2023

Ok, proof of concept:ish for influxdb/grafana ✔️ :

Screenshot 2023-08-28 at 14-48-14 Single Geth - Grafana

This change moves the initialization of an ordered registry to a shared
subpackage in 'internal', and makes it so both influx and prometheus
use the same testdata.
@holiman holiman merged commit 53f3c2a into ethereum:master Aug 31, 2023
2 checks passed
devopsbo3 pushed a commit to HorizenOfficial/go-ethereum that referenced this pull request Nov 10, 2023
…sb) (ethereum#24877)

This chang creates a GaugeInfo metrics type for registering informational (textual) metrics, e.g. geth version number. It also improves the testing for backend-exporters, and uses a shared subpackage in 'internal' to provide sample datasets and ordered registry. 

Implements ethereum#21783

---------

Co-authored-by: Martin Holst Swende <martin@swende.se>
devopsbo3 added a commit to HorizenOfficial/go-ethereum that referenced this pull request Nov 10, 2023
devopsbo3 added a commit to HorizenOfficial/go-ethereum that referenced this pull request Nov 10, 2023
devopsbo3 added a commit to HorizenOfficial/go-ethereum that referenced this pull request Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants