You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
I noticed errors in the container log and decided to take a look, as a result I came across a problem with the paths, but i dont fix my problem.
1. caller=collector.go:346 level=error msg="Error scraping metric" Context=activity MetricsDesc="map[value:Generic counter metric from v$sysstat view in Oracle.]" time=44.085579ms error="**driver: bad connection**"
2. caller=collector.go:346 level=error msg="Error scraping metric" Context=db_platform MetricsDesc="map[value:Database platform]" time=48.104538ms error="driver: bad connection"
3. caller=collector.go:346 level=error msg="Error scraping metric" Context=db_system MetricsDesc="map[value:Database system resources metric]" time=1.375944ms error="driver: bad connection"
Hi @AOzhogin
Thanks for reporting this issue.
I am pretty sure this is just becuase of the difference between the arm and amd versions of instant client - they put the .so files in different directories, so we added both paths so it would work on either architecture.
I will double check on this to make sure everything is working as expected and update this issue.
Thanks!
Hi,
Image: amd64 container-registry.oracle.com/database/observability-exporter:1.5.0 id: 7a38e0ddd3e6
Registry: container-registry.oracle.com
DB: Oracle 19.0.0.0.0
Problem:
I noticed errors in the container log and decided to take a look, as a result I came across a problem with the paths, but i dont fix my problem.
Other database queries are working.
The text was updated successfully, but these errors were encountered: