Revisit redis receiver metrics #6942
Description
The following issues found with the redis receiver metrics:
- Many metrics miss unit field.
- Some metrics can be combined with an additional attribute, e.g. different metrics for memory -> one metrics + "state" attribute.
- Start timestamp is inconsistent between sum and gauge metrics.
- CPU metrics reported inconsistently, only 3 of 8 redis metrics reported:
- used_cpu_sys -> redis.cpu.time{state=sys}
- used_cpu_user -> redis.cpu.time{state=user}
- used_cpu_sys_children -> redis.cpu.time{state=children}
- used_cpu_user_children is skipped
- used_cpu_sys_main_thread is skipped
- used_cpu_user_main_thread is skipped
- More than half of the redis metrics are not collected at all, they can be added as optional (disabled by default) metrics once [receiver/redis] Apply new mdatagen metrics builder #6938 is merged.