-
Notifications
You must be signed in to change notification settings - Fork 77
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
Exporter service failing with "slice index out of range" error #42
Comments
Seems like a problem with scraping the alertlog. So far i never used the exporter for Oracle 18/19. I've only used it in 11g/12g. Can you please post your configfile and a snippet of the alertlog? |
hi, the alert log seems to be swamped with TNS messages, i'm going to investigate those. The config file is monitoring 20 databases so it's difficult to pin down if one of the messages is the alert logs corresponds to the error message in the messages file. I'm going to limit the config to just monitor a couple of databases and see if that make things easier to piece together what could be causing the problem. will post again when things are a bit simpler thanks for you help |
Hi, I've cleaned up the TNS messages from the alerts logs, and also excluded the particular error (TNS-12535) from being recorded by the exporter. The configfile is attached, from that you can see it is monitoring 3 databases, there is nothing in the alert log anywhere near the time of the failure in the exporter service. this is the message displayed by the systemctl status for the service Dec 02 11:04:55 cs-tc3-oracle-dev2.apak-dmz.local systemd[1]: Started Oracle Database Exporter for Prometheus. |
connections:
|
Hi
The oracle prometheus exporter service is failing after a few days on several of our servers. The error in the messages file is below...
the service file looks like this...
any ideas what the problem would be ??
The text was updated successfully, but these errors were encountered: