fartsampler v0.1.6

config the library - configure via yml/constractor/env-vars

config must be including 
   reporter  
    - report to console 
    - report to log 
    - report to csv (?)
   metric
    - skip idel metrics : it means that when vaule of metric is unchanged , there will not be a report
    - define app name
    - meter fields (count 1m_rate 5m ,15m)
    - timer fiedls (count,min,max,p99,p98,1m_rate 5m ,15m)
    - resethistogram
    - verbosity ? 

   db config 
    - host V
    - port V
    - db (name) V
    - protocol  V
    - connection time out ?
    - read time out ?
    
    print actual config  - not my problem

#define and use metrics registry - 

b2b Api (library to influxdb comunication )

in order to set the Api clear, we must make a convention for future metrics 

1. TAGS - map<String, String> #key will be the db key such as hostname ,pid ,app name and those will be a filters in future use #Value will be applied accordingly @ will be set later in section 3

2. meter and timer fields

   • create sets from user input (in metrics)

3. create and start influx reporter

   • idbreporter with :
     • metrics
     • tages
     • timer fields
     • meter fields
     • duration
     • rate
     • skip idel metrics

4. create other reporters

b2c Api (library to developer)

basic 
1- start/get timer (metric name)
2- start/get counter
3- increase/decrease/update counter 
4- update histogram 
5- register JUST once 
6- get parts by name - join string with "." between every part with keys 
adve

1- getorAddtimer /histogram - private method
2-  

Edit a file, create a new file, and clone from Bitbucket in under 2 minutes

When you're done, you can delete the content in this README and update the file with details for others getting started with your repository.

We recommend that you open this README in another tab as you perform the tasks below. You can watch our video for a full demo of all the steps in this tutorial. Open the video in a new tab to avoid leaving Bitbucket.

Edit a file

You’ll start by editing this README file to learn how to edit a file in Bitbucket.

1. Click Source on the left side.
2. Click the README.md link from the list of files.
3. Click the Edit button.
4. Delete the following text: Delete this line to make a change to the README from Bitbucket.
5. After making your change, click Commit and then Commit again in the dialog. The commit page will open and you’ll see the change you just made.
6. Go back to the Source page.

Create a file

Next, you’ll add a new file to this repository.

1. Click the New file button at the top of the Source page.
2. Give the file a filename of contributors.txt.
3. Enter your name in the empty file space.
4. Click Commit and then Commit again in the dialog.
5. Go back to the Source page.

Before you move on, go ahead and explore the repository. You've already seen the Source page, but check out the Commits, Branches, and Settings pages.

Clone a repository

Use these steps to clone from SourceTree, our client for using the repository command-line free. Cloning allows you to work on your files locally. If you don't yet have SourceTree, download and install first. If you prefer to clone from the command line, see Clone a repository.

1. You’ll see the clone button under the Source heading. Click that button.
2. Now click Check out in SourceTree. You may need to create a SourceTree account or log in.
3. When you see the Clone New dialog in SourceTree, update the destination path and name if you’d like to and then click Clone.
4. Open the directory you just created to see your repository’s files.

Now that you're more familiar with your Bitbucket repository, go ahead and add a new file locally. You can push your change back to Bitbucket with SourceTree, or you can add, commit, and push from the command line.