brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <...@git.apache.org>
Subject [GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...
Date Tue, 21 Jun 2016 08:34:10 GMT
Github user aledsage commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/79#discussion_r67827766
  
    --- Diff: guide/ops/requirements.md ---
    @@ -19,6 +19,43 @@ at least 8GB RAM and 100GB disk. The disk is just for logs, a small
amount of pe
     any binaries for custom blueprints/integrations.
     
     
    +### Disk Space
    +
    +There are three main consumers of disk space:
    +
    +* **Static files**: these are the Apache Brooklyn files themselves, plus
    +  binaries for custom blueprints and integrations added to the `lib` directory.
    +* **Persisted state**: when using [Persistence](persistence/index.html) -- which
    +  is a prerequisite for [High Availability](high-availability.html) -- Brooklyn
    +  will save data to a store location. Items in the persisted state include
    +  metadata about the Brooklyn servers, catalog items, and metadata about all
    +  running applications and entities.
    +* **Log files**: Brooklyn writes detailed log files by default to its own
    +  installation directory. This can be reconfigured to change the destination
    --- End diff --
    
    Agreed. Perhaps we don't need to say here where it's written to - you've already linked
to the logging section. Instead just say:
    
         **Log files**: Brooklyn writes info and debug log files. By default, these are 
        written to the local filesystem. This can be reconfigured to set the destination
        and to increase or decrease the detail in the logs. See the
        [Logging](logging.html) section for more details.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message