Giter Site home page Giter Site logo

influxdata / docs.influxdata.com-archive Goto Github PK

View Code? Open in Web Editor NEW
253.0 61.0 295.0 138.81 MB

ARCHIVE - 1.x docs for InfluxData

Home Page: https://archive.docs.influxdata.com/

License: MIT License

HTML 28.62% Shell 0.88% CSS 2.12% JavaScript 10.20% Less 58.18%

docs.influxdata.com-archive's Introduction

Note: This repository is for the InfluxData documentation archive and is not actively maintained. For the most recent InfluxData documentation repository, visit github.com/influxdata/docs-v2/.

InfluxData Documentation Archive

This repository powers archive.docs.influxdata.com, which includes archived documentation for the following InfluxData projects and versions:

  • Telegraf v0.10 - v1.8
  • InfluxDB v0.10 - v1.2
  • InfluxDB Enterprise v1.0 - v1.3
  • Chronograf v0.10 - v1.5
  • Kapacitor v0.10 - v1.3
  • Kapacitor Enterprise v1.3 - v1.5

docs.influxdata.com-archive's People

Contributors

121watts avatar alexpaxton avatar beckettsean avatar benschweizer avatar dandv avatar danielnelson avatar dependabot[bot] avatar desa avatar dragoshenron avatar gunnaraasen avatar jackzampolin avatar jaredscheib avatar joe-influx avatar jstirnaman avatar karel-rehor avatar kelseiv avatar mark-rushakoff avatar nathanielc avatar noramullen1 avatar paulinalei avatar pierwill avatar rkuchan avatar rossmcdonald avatar russorat avatar sanderson avatar stevebang avatar thergbway avatar timhallinflux avatar timraymond avatar toddboom avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docs.influxdata.com-archive's Issues

show tag values throwing ERR

Originally: https://github.com/influxdb/influxdb.com/issues/547

Is there some way I can send a trace or dump file for my database?
I'm using Influx 0.9.5.1.

See the problem:
[ksengal@csdev-ksengal influxdb]$ influx
Visit https://enterprise.influxdata.com to register for updates, InfluxDB server management, and monitoring.
Connected to http://localhost:8086 version 0.9.5.1
InfluxDB shell 0.9.5.1
% show databases

name: databases

name
_internal
cs

% use cs
Using database cs
% help
Usage:
connect host:port connect to another node
auth prompt for username and password
pretty toggle pretty print
use set current databases
format set the output format: json, csv, or column
precision set the timestamp format: h,m,s,ms,u,ns
consistency set write consistency level: any, one, quorum, or all
settings output the current settings for the shell
exit quit the influx shell

show databases        show database names
show series           show series information
show measurements     show measurement information
show tag keys         show tag key information
show tag values       show tag value information

a full list of influxql commands can be found at:
https://influxdb.com/docs/v0.9/query_language/spec.html

% show series

name: fakeMeasurementName

_key fakeTagLabel1 fakeTagLabel2
fakeMeasurementName,fakeTagLabel1=fakeTagValue1,fakeTagLabel2=fakeTagValue2 fakeTagValue1 fakeTagValue2

% show tag keys

name: fakeMeasurementName

tagKey
fakeTagLabel1
fakeTagLabel2

% show tag values

ERR: error parsing query: found EOF, expected WITH at line 1, char 17 <~~ Error?
% SELECT * from fakeMeasurementName
% <~~~~ Also, this should return something :(

What are the debugging commands available to help here?
Note, the data was inserted using golang code using v2 version of golang client api (pasting it here probably would not make sense).

Here I try to grab the entire series:

[ksengal@csdev-ksengal influxdb]$ curl -G 'http://localhost:8086/query?pretty=true' --data-urlencode "db=cs" --data-urlencode "q=SELECT value FROM fakeMeasurementName"
{
"results": [
{}
]
}

EMPTY, yet...

[ksengal@csdev-ksengal influxdb]$ influx
Visit https://enterprise.influxdata.com to register for updates, InfluxDB server management, and monitoring.
Connected to http://localhost:8086 version 0.9.5.1
InfluxDB shell 0.9.5.1
% use cs
Using database cs
% show series

name: fakeMeasurementName

_key fakeTagLabel1 fakeTagLabel2
fakeMeasurementName,fakeTagLabel1=fakeTagValue1,fakeTagLabel2=fakeTagValue2 fakeTagValue1 fakeTagValue2

%

[new page] instructions on setting up HTTPS #284

Originally: https://github.com/influxdb/influxdb.com/issues/

@toddboom
I'm not sure we have this documented anywhere yet, but some quick instructions on how to set up a PEM file to work with InfluxDB for the HTTP API and the admin interface would be helpful. I'll add some notes here on how it should be laid out.

@victorhooi
For reference, this was the question I posted on the InfluxDB group about this issue:

https://groups.google.com/d/topic/influxdb/onlhVW9WJ-A/discussion

and it also contains the steps I followed.

It would be awesome if the proper way could be captured in the docs though.

I've managed to get the InfluxDb server-side working, now I'm hitting issue with the Influx CLI seemingly not liking the self-signed certs. Hopefully will be able to nut those out on the Google Group =).

Document INTO keyword

Originally: https://github.com/influxdb/influxdb.com/issues/520

Starting from version 0.9.5 INTO keyword can be used outside of continuous queries: influxdata/influxdb#4409.

But it's still unclear how to use this feature.

I was able to make two-step filtering with queries like these:

SELECT last(size) INTO temp FROM vm GROUP BY hostname
SELECT sum(last) FROM temp
But here are two questions:

  1. how to join them into a single query? Semicolon does not work by some reason.
  2. I'm using temp, but what does this syntax mean? It is some kind of a local variable? Is it performant and safe to use on a large number of queries in Grafana?

Thanks.

"GROUP BY time intervals" example doesn't explain time interval offsets

Originally: https://github.com/influxdb/influxdb.com/issues/462

Related to influxdata/influxdb#1837

In the "GROUP BY time intervals" example in this section of the documentation, there is a lower time bound of 2015-08-18T00:00:00Z and a GROUP BY time(2d) in the query. The first timestamp returned is 2015-08-17T00:00:00Z.

A couple observations:

  1. It is surprising that a timestamp is returned that lies outside the range specified in the WHERE clause.
  2. It is not discussed why this particular timestamp was the first returned.

I infer from the issue linked above that this occurs because 2015-08-17T00:00:00Z is zero seconds modulo (2*24*60*60), but this is not obvious from reading the example. I could have just as easily concluded (falsely) that GROUP BY time(2d) assumes my time lower bound refers to the midpoint of the GROUP BY interval.

This example should be updated to indicate what exactly is going on by default, and perhaps link to the issue.

[new page] open feature requests

Originally: https://github.com/influxdb/influxdb.com/issues/234

Let's put up a page of the larger feature requests (timezone support, month/year support, custom functions, multiple mount points, etc) so that they are discoverable, and so that we can make some comments about them all in one place. It will help the community understand what's on the eventual roadmap, what's open for debate, and what's not going to be considered until 2.x or later.

[new page] Shards and Shard Management

Originally: https://github.com/influxdb/influxdb.com/issues/491

Under Concepts:

  • how data are organized into shards
    • by time (If the RP has a duration less than 2 days, all shards are 1h shards. If the RP has a duration of 2 days to 6 months, all shards are 1d shards. For durations greater than 6 months, all shards are 7d shards.)
    • by series (modulo assignment)
    • how replicated
    • what duration and expiration means
  • SHOW SHARDS
  • SHOW SHARD GROUPS, see influxdata/influxdb#4792

Probably link to the FEI about data not being dropped after altering a retention policy: https://docs.influxdata.com/influxdb/v0.9/troubleshooting/frequently_encountered_issues/#data-aren-t-dropped-after-altering-a-retention-policy.

update write pages to reflect new partial batch success writes

Originally: https://github.com/influxdb/influxdb.com/issues/436

From influxdata/influxdb#4587:

"HTTP line protocol handler will now write all successfully parsed points instead of failing the entire batch if one failed. When some points fail to parse and the remaining are written successfully, the endpoint returns a partial write error with the failed lines in the response. This makes the behavior more consistent with the other inputs."

create new docs structure

Originally: https://github.com/influxdb/influxdb.com/issues/329

In advance of the new website and docs support for the new products, let's build the skeleton organization.

Each product will have the following sections:

  • Intro
    • Overview
    • Installation
    • Getting Started
  • Learning (replaces Guides)
  • Reference (can be multiple sections here)
    • Configuration
    • Plugins (if appropriate)
    • Libraries (if appropriate)
    • DSL (if appropriate)
  • About
    • Contributing
    • License
    • Getting Help

add FAQ entry about apparent loss of data when making a new default RP

Originally: https://github.com/influxdb/influxdb.com/issues/395

When a user creates a new RP and makes it the default, all queries go to the new RP by default. That can make it look like data has gone missing, since queries that used to work no longer return values.

E.g.

SELECT count(value) FROM foo returns 10000.
CREATE RETENTION POLICY bar ON mydb DURATION INF REPLICATION 1 DEFAULT
SELECT count(value) FROM foo returns 0. (because it's actually querying bar.foo, and the existing points are in default.foo.
SELECT count(value) FROM default.foo returns 10000.

Another instance of this confusion: influxdata/influxdb#4832 (comment).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.