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
Docs are missing max-series-per-database setting #710
Labels
Comments
Set Please read the docs about schema design to make sure you are using series responsibly. |
beckettsean
changed the title
Influx DB stopped writing DATA into a DB with Error Max Series per Database exceeds.
document new configuration settings
Sep 25, 2016
need to add
to http://docs.influxdata.com/influxdb/v1.0/administration/config/ |
beckettsean
changed the title
document new configuration settings
Docs are missing max-series-per-database setting
Sep 27, 2016
rkuchan
added a commit
that referenced
this issue
Sep 28, 2016
Thank you for pointing that out, @reshujain4u. Fixed by #734. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{"error":"max series per database exceeded: Metrics,App=Saks,MetricName=average_dom_content_load_time,Metric_Type=EndUser/RB/UserAgent/Mobile/Browser"}
This is what I'm getting, I am pretty new to influx db and Time series database, requirnment is to have mutiple tags like App,Metrics_Type to be feeded into influx db, with Metrics (in case content load time) with value.
It is currnetly auto generating Timeseries, I tried to take configuration using influxd config > /etc/influxdb/influxdb.conf.generated
then updated Max-Series DB filed and saved the file, then passon command
influxd -config /etc/influxdb.conf.generated
restarted Influx as port 8086 was used by gafana to query influx db.
Still nothing happens.. Please provide a clear command to disable max series and let infux make unlimited entry... Because this is going to used for atleast 2 years.
URL for relevant page?
What products and version are you using?
Where did you look before opening the issue?
The text was updated successfully, but these errors were encountered: